Hi Nico,

> That's correct, but the problem is, we maintain 1 updatescript for
> all customers. So, if we use TIMESTAMP in the script, it won't work
> for IB customers, and if we use DATE then the TIME part of the data
> is gone in FB. That's our main problem for now :-)

Aha, so that's the problem. Sorry, I didn't get that from the original
question.

You could do a search/replace before running the script :-)

Anyway, if you have a datatype that's not supported in
dialect 1/IB 5.6 - you will run into problems, as you have
found out.

With regards,

Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL
Server.
Upscene Productions
http://www.upscene.com

> Thanks ! Nico
>
>
> --- In firebird-support@yahoogroups.com, "Martijn Tonies"
> <m.tonies@u...> wrote:
> > Hi Nico,
> >
> > > Thanks for the response. Are you sure about Timestamp in IB 5.6,
> > > dialect 1 ? Because most of our customers are running under
> dialect
> > > 1 still.
> >
> > In IB < 6, it's called DATE, in IB 6, dialect 3, it's called
> TIMESTAMP.
> >
> > In dialect 3, DATE holds date only while TIME holds time only.
> > TIMESTAMP holds both.
> >
> > With regards,
> >
> > Martijn Tonies
> > Database Workbench - developer tool for InterBase, Firebird, MySQL
> & MS SQL
> > Server.
> > Upscene Productions
> > http://www.upscene.com
> >
> >
> > > Best regards, Nico
> > >
> > >
> > > --- In firebird-support@yahoogroups.com, "Martijn Tonies"
> > > <m.tonies@u...> wrote:
> > > > Hi Nico,
> > > >
> > > > > After migrating from IB 5.6 to FB 1.5, we changed the dialect
> to
> > > 3.
> > > > > Because there is no common datatype in IB and FB to hold Date
> and
> > > > > Time in 1 field,
> > > >
> > > > Yes there is - its called TIMESTAMP.
> > > >
> > > > >we want to switch back to dialect 1, so we can use
> > > > > DATE datatype again. Is this possible, because after
> changing
> > > with
> > > > > GFIX, we get BIGINT errors.