From: ilMes mes (il_meshotmail.com)
Date: Wed Jan 21 2004 - 14:39:23 CST

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

MaxDB v.7.5.00.08 on Linux Red Hat 8.0
ODBC on Windows "SAP DB 7.05.00.00"
ADO 2.8 and Visual Basic 6.0 SP5

Compatibility problem ADO<->MaxDB with TIMESTAMP columns

I have a table like:
create table XX (
  ID INTEGER NOT NULL,
  MYDATE TIMESTAMP DEFAULT TIMESTAMP,
  PRIMARY KEY(ID)
)

ok, if i insert a record without explicit value for MYDATE column, the
database use the DEFAULT TIMESTAM value.

But, TIMESTAMP is in the format '2004-01-01 11:22:33.697500' with
microsecond!!

Now for exaple, I create an Microsoft Access database and Link (Attached
table) the table XX via ODBC.
If i with MAccess TRY to change the value of MYDATE column of may record, i
have the error like "Anhoder user have changed or delete the record"!! Is
Not TRUE!
The real True is that MAccess tryed to Update the record, but it do not
founded the record because it was searched a record with MYDATE =
'2004-01-01 11:22:33' without the MICROSECONDs!

I tryed to create the table in this mode:
create table XX (
  ID INTEGER NOT NULL,
  MYDATE TIMESTAMP DEFAULT TIMESTAMP(DATE,TIME),
  PRIMARY KEY(ID)
)
But it is not possible.

The only value possible for DEFAULT is TIMESTAMP, no Procedures, no internal
Funcions, no TIMESTAMP without microsecounds.

How can i do?
(i prefer no to use a triggers)

My opinion is that should to be necessary to can specify a DEFAULT value
more flexible, and to have a TIMESTAMP without microsecoud.
Can you implement in teh next versions?

Hi
Ettore,
il Mes

_________________________________________________________________
Nuovo MSN Messenger con sfondi e giochi! http://messenger.msn.it/ Provalo
subito!

--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]