Watch out for new reserved words in dialect 3. State, for instance, has
become a reserved word, as has Type.

Also, rules for dates and times have changed with the new data types.

At 08:17 AM 03/26/2001 -0700, you wrote:

>I did hear that for large numeric columns using the new int64 instead of the
>doubleprecision yielded much faster numeric processing.
>
>Jason Wharton
>CPS - Mesa AZ
>http://www.ibobjects.com
>
>
>----- Original Message -----
>From: "Geoff Worboys" <geoff@...>
>To: <IBObjects@yahoogroups.com>
>Sent: Sunday, March 25, 2001 7:31 PM
>Subject: Re: [IBO] Dialect 1 or 3?
>
>
> > > If we are creating a new Database, is there any preferred
> > > choice between Dialect 1 and 3. We are happy not to have spaces
> > > and capitalised field names (e.g. field names in Dialect 1 are
> > > fine.) Is there any other reason to choose Dialect 1 or 3,
> > > e.g. any performance differences?
> >
> > MHO - choose dialect 3, so that you can implement Dialect 3 features
> > in the future without conversion problems - such as keyword
> > differences and maths changes (int64 support). Also this way your
> > data types can explicitly state the date/time/timestamp requirement of
> > a field.
> >
> > I doubt if there is much in the way of performance difference either
> > way.
> >
> > Geoff Worboys
> > Telesis Computing
>
>
>
>
>
>
>Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>