Re: [mdb-dev] Possible bug: incorrectly returned Date/Time fields

[Sam M. <pa...@gm...>]

Considering this has only just hit the list afaik (well, my gmail
account just popped up with it), as a simple solution just add a
second on to the times when they come out. I can't personally see an
issue with your SQL.

Also, what version of mdb-tools are you using?


On Thu, 27 Jan 2005 09:48:41 +0200, Mindaugas Kirsanskas
<Min...@ha...> wrote:
> =20
> =20
>=20
> Hello,=20
>=20
>  =20
>=20
> I don't know if such situation was reported, but recently I noticed that
> data in mysql database differ from ms access, particulary Date/Time field=
s
> (format in access db - General Date). During replication process almost h=
alf
> of data was damaged (Date/Time was short by one second), and there is no
> rule which data damaged. This is really serious problem to me because whe=
n
> operating with huge databases it causes big differences in duration and s=
o
> on=E2=80=A6=20
>=20
>  =20
>=20
> Tried to select data via mdb-sql to make sure this is mdbtools problem an=
d
> this is what I got:=20
>=20
> 1 =3D> select * from IVR_Calls_NoDet where Start_Date < '01/02/04 00:00:0=
0';=20
>=20
> 2 =3D> go=20
>=20
> Calling mdb_test_sarg on unknown type.  Add code to mdb_test_sarg() for t=
ype
> 8=20
>=20
> ( my data =E2=80=A6. )=20
>=20
> Calling mdb_test_sarg on unknown type.  Add code to mdb_test_sarg() for t=
ype
> 8=20
>=20
> =E2=80=A6=20
>=20
> =E2=80=A6=20
>=20
>  =20
>=20
> Where clause was ignored, and data from Date/Time fields was shorter in 1
> second.=20
>=20
>  =20
>=20
> If it is not a bug so please explain what I am doing wrong. I tried vario=
us
> Date/Time formats, JET3 and JET4 engines but always get the same result.=
=20
>=20
>  =20
>=20
> It is really urgent to me, so please respond=20
>=20
>  =20
>=20
> Thanks in advance