From: Date: September 13 2005 8:58am
Subject: RE: Update problem
List-Archive: http://lists.mysql.com/myodbc/10348
Message-Id: <79F81D5F4790D344B05F489CE2AC8AB72418A0@dubexdc03.dubex.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Carlos Daniel Olivas Barba wrote:
> Hi, I turned on logging, what I got is this:
>
> UPDATE `sweet`.`traspasos` SET
> =
`FOLIO_TRASPASO`=3D1,`ORIGEN`=3D'VD',`DESTINO`=3D'JR',`FECHA`=3D'20050912=
',
> =
`HORA`=3D'10:39:43',`CODRESPON`=3D'CARLOS',`TERM`=3D'CARLOS',`STATUS`=3D'=
2',
> `OBSERVACIONES`=3D'ok. guardar para continuar despues'
> WHERE `FOLIO_TRASPASO`=3D1 AND `ORIGEN`=3D'VD' AND `DESTINO`=3D'JR' =
AND
> `FECHA`=3D'20050908' AND `HORA` IS NULL
> AND `CODRESPON`=3D'CARLOS' AND `TERM`=3D'CARLOS' AND `STATUS`=3D'2' =
AND
> `OBSERVACIONES`=3D'ok. guardar para continuar despues' AND
`CONSECUTIVO`=3D1
>
> I think the error is the column FECHA because the date format is
> "YYYY-MM-DD" and then column HORA in the selected recordset is not
null,
> it's "00:00:00".

Ok, so far so good.  Never seen that problem before.

The manual:
 http://dev.mysql.com/doc/mysql/en/date-and-time-types.html

states that:
 "Zero" date or time values used through MyODBC are converted
automatically
 to NULL in MyODBC 2.50.12 and above, because ODBC can't handle such
values.

which might be a clue.