ODBC: "Write conflict" from access. - MySQL ODBC

MySQLTalk.org
MYSQL discussions groups

Archives

FAQ

Memberlist

Usergroups

Profile

ODBC: "Write conflict" from access.

MySQLTalk.org Forum Index -> MySQL ODBC

View previous topic :: View next topic

Author

Message

Steve Webb
Guest

Posted: Fri Jun 25, 1999 9:29 pm Post subject: ODBC: "Write conflict" from access.

Hello.

I had odbc and access working great together until I upgraded mysql to
3.21.33b. Now, when I try to change something in the database from access, I
get a "Write Conflict" message. The dialog box makes it sound like the record
has been changed since I last read the data and doesn't allow me to change
the record.

I tried starting safe_mysqld with the "--old-protocol" option but it didn't
make any difference.

Any ideas?

I turned on tracing in the odbc driver and I get:

Quote:

do_query
mysql_real_query
| enter: handle: 15f3cc
| query: Query = "UPDATE Fixed_Assets SET login='test' WHERE ID = 9 AND
login = 'crook' AND system_name = 'alpha' AND type = 'cpu' AND description =

'PB46A-AA' AND location = 'FL2-2080' AND serial_number = 'KA513VUKN9' AND
nsf_number IS NULL AND ppe_number = 'PPE000000701' AND po_number = '52391' AND
vendor = 'DEC' AND date_installed = 19950413000000 AND status IS NULL AND
timestamp = 19961112000000 AND project = '170113' AND architecture = 'DEC' AND
operating_system IS NULL"

Quote:

| >free_old_query
| mysql_real_query
mysql_store_result
mysql_store_result
_myfree
| enter: ptr: 96c3a28
_myfree
do_query
SQLRowCount
exit: Affected rows: 0
SQLRowCount
SQLFreeStmt
enter: stmt: 15f278 option: 0
mysql_free_result
| enter: mysql_res: 0
mysql_free_result
SQLFreeStmt
SQLFreeStmt
enter: stmt: 15f278 option: 1
mysql_free_result
| enter: mysql_res: 0
mysql_free_result
_myfree
| enter: ptr: 96c2238
_myfree
my_free
| my: ptr: 96c3c30
my_free
SQLFreeStmt

- Steve

--
_ _ ____ _
____ __ _____| |__| |__ / __ _ _ __ __ _ _ _ ___ __| |_ _
(_-< V V / -_) '_ '_ / / _` | || / _/ _` | '_|/ -_) _` | || |
/__/_/_/___|_.__/_.__/ __,_|_,_____,_|_|(_)_____,_|_,_|
____/ http://www.rap.ucar.edu/~swebb

Michael Widenius
Guest

Posted: Tue Jun 29, 1999 4:01 am Post subject: ODBC: "Write conflict" from access.

Quote:

"Steve" == Steve Webb <swebb (AT) rap (DOT) ucar.edu> writes:

Steve> Hello.
Steve> I had odbc and access working great together until I upgraded mysql to
Steve> 3.21.33b. Now, when I try to change something in the database from access, I
Steve> get a "Write Conflict" message. The dialog box makes it sound like the record
Steve> has been changed since I last read the data and doesn't allow me to change
Steve> the record.

Steve> I tried starting safe_mysqld with the "--old-protocol" option but it didn't
Steve> make any difference.

Steve> Any ideas?

Steve> I turned on tracing in the odbc driver and I get:

Quote:

do_query
Steve> | >mysql_real_query

Steve> | | enter: handle: 15f3cc
Steve> | | query: Query = "UPDATE Fixed_Assets SET login='test' WHERE ID = 9 AND
Steve> login = 'crook' AND system_name = 'alpha' AND type = 'cpu' AND description =
Steve> 'PB46A-AA' AND location = 'FL2-2080' AND serial_number = 'KA513VUKN9' AND
Steve> nsf_number IS NULL AND ppe_number = 'PPE000000701' AND po_number = '52391' AND
Steve> vendor = 'DEC' AND date_installed = 19950413000000 AND status IS NULL AND
Steve> timestamp = 19961112000000 AND project = '170113' AND architecture = 'DEC' AND
Steve> operating_system IS NULL"
Steve> | | >free_old_query
Steve> | | <free_old_query
Steve> | <mysql_real_query
Steve> | >mysql_store_result
Steve> | <mysql_store_result
Steve> | >_myfree
Steve> | | enter: ptr: 96c3a28
Steve> | <_myfree
Steve> <do_query

Quote:

SQLRowCount
Steve> | exit: Affected rows: 0

Steve> <SQLRowCount

Quote:

SQLFreeStmt
Steve> | enter: stmt: 15f278 option: 0

Steve> | >mysql_free_result
Steve> | | enter: mysql_res: 0
Steve> | <mysql_free_result
Steve> <SQLFreeStmt

Quote:

SQLFreeStmt
Steve> | enter: stmt: 15f278 option: 1

Steve Webb
Guest

Posted: Tue Jun 29, 1999 3:21 pm Post subject: Re: ODBC: "Write conflict" from access.

Another good guess, but I have a "DATETIME" and a "TIMESTAMP" field. No
"DATE" fields. I sense, from the proposed solutions so-far, that there is no
ODBC problem and just a date issue. Could it be that the clocks on the server
and the client machine are just "enough" off to cause a problem?

- Steve

On Tue, 29 Jun 1999, Michael Widenius wrote:

Quote:

"Steve" == Steve Webb <swebb (AT) rap (DOT) ucar.edu> writes:

Steve> Hello.
Steve> I had odbc and access working great together until I upgraded mysql to
Steve> 3.21.33b. Now, when I try to change something in the database from access, I
Steve> get a "Write Conflict" message. The dialog box makes it sound like the record
Steve> has been changed since I last read the data and doesn't allow me to change
Steve> the record.

Steve> I tried starting safe_mysqld with the "--old-protocol" option but it didn't
Steve> make any difference.

Steve> Any ideas?

Steve> I turned on tracing in the odbc driver and I get:

do_query
Steve> | >mysql_real_query
Steve> | | enter: handle: 15f3cc
Steve> | | query: Query = "UPDATE Fixed_Assets SET login='test' WHERE ID = 9 AND
Steve> login = 'crook' AND system_name = 'alpha' AND type = 'cpu' AND description =
Steve> 'PB46A-AA' AND location = 'FL2-2080' AND serial_number = 'KA513VUKN9' AND
Steve> nsf_number IS NULL AND ppe_number = 'PPE000000701' AND po_number = '52391' AND
Steve> vendor = 'DEC' AND date_installed = 19950413000000 AND status IS NULL AND
Steve> timestamp = 19961112000000 AND project = '170113' AND architecture = 'DEC' AND
Steve> operating_system IS NULL"
Steve> | | >free_old_query
Steve> | | <free_old_query
Steve> | <mysql_real_query
Steve> | >mysql_store_result
Steve> | <mysql_store_result
Steve> | >_myfree
Steve> | | enter: ptr: 96c3a28
Steve> | <_myfree
Steve> <do_query
SQLRowCount
Steve> | exit: Affected rows: 0
Steve> <SQLRowCount
SQLFreeStmt
Steve> | enter: stmt: 15f278 option: 0
Steve> | >mysql_free_result
Steve> | | enter: mysql_res: 0
Steve> | <mysql_free_result
Steve> <SQLFreeStmt
SQLFreeStmt
Steve> | enter: stmt: 15f278 option: 1
Steve> | >mysql_free_result
Steve> | | enter: mysql_res: 0
Steve> | <mysql_free_result
Steve> | >_myfree
Steve> | | enter: ptr: 96c2238
Steve> | <_myfree
Steve> | >my_free
Steve> | | my: ptr: 96c3c30
Steve> | <my_free
Steve>
Hi!

If some of the above fields are DATE field and not DATETIME fields,
then the solution is to upgrade to MySQL 3.22.23b or change all DATE
fields to DATETIME fields!

Regards,
Monty

--
_ _ ____ _
____ __ _____| |__| |__ / __ _ _ __ __ _ _ _ ___ __| |_ _
(_-< V V / -_) '_ '_ / / _` | || / _/ _` | '_|/ -_) _` | || |
/__/_/_/___|_.__/_.__/ __,_|_,_____,_|_|(_)_____,_|_,_|
____/ http://www.rap.ucar.edu/~swebb

Michael Widenius
Guest

Posted: Tue Jun 29, 1999 6:29 pm Post subject: Re: ODBC: "Write conflict" from access.

Quote:

"Steve" == Steve Webb <swebb (AT) rap (DOT) ucar.edu> writes:

Steve> Another good guess, but I have a "DATETIME" and a "TIMESTAMP" field. No
Steve> "DATE" fields. I sense, from the proposed solutions so-far, that there is no
Steve> ODBC problem and just a date issue. Could it be that the clocks on the server
Steve> and the client machine are just "enough" off to cause a problem?

I don't think so.

Could you try to execute the query in the mysql client and try to find
out why it doesn't find any matching rows.

Steve> | | query: Query = "UPDATE Fixed_Assets SET login='test' WHERE ID = 9 AND
Steve> login = 'crook' AND system_name = 'alpha' AND type = 'cpu' AND description =
Steve> 'PB46A-AA' AND location = 'FL2-2080' AND serial_number = 'KA513VUKN9' AND
Steve> nsf_number IS NULL AND ppe_number = 'PPE000000701' AND po_number = '52391' AND
Steve> vendor = 'DEC' AND date_installed = 19950413000000 AND status IS NULL AND
Steve> timestamp = 19961112000000 AND project = '170113' AND architecture = 'DEC' AND
Steve> operating_system IS NULL"

Regards,
Monty

Steve Webb
Guest

Posted: Tue Jun 29, 1999 6:38 pm Post subject: Re: ODBC: "Write conflict" from access.

Quote:

1 row in set (0.00 sec)

mysql> UPDATE Fixed_Assets SET login='test' WHERE ID = 9 AND login = 'crook'
AND system_name = 'alpha' AND type = 'cpu' AND description = 'PB46A-AA' AND
location = 'FL2-2080' AND serial_number = 'KA513VUKN9' AND nsf_number IS NULL
AND ppe_number = 'PPE000000701' AND po_number = '52391' AND vendor = 'DEC' AND
date_installed = 19950413000000 AND status IS NULL AND timestamp =
19961112000000 AND project = '170113' AND architecture = 'DEC' AND
operating_system IS NULL;
Query OK, 0 rows affected (0.01 sec)

mysql> desc Fixed_Assets;
+------------------+---------------+------+-----+---------+----------------+

Quote:

18 rows in set (0.00 sec)

The only thing that looks different is the "date_installed" field which gets
displayed in a "formatted" sense when it's displayed, but the data is the
same.

Should I change the "date_installed" from datetime to timestamp?

- Steve

On Tue, 29 Jun 1999, Michael Widenius wrote:

Quote:

"Steve" == Steve Webb <swebb (AT) rap (DOT) ucar.edu> writes:

Steve> Another good guess, but I have a "DATETIME" and a "TIMESTAMP" field. No
Steve> "DATE" fields. I sense, from the proposed solutions so-far, that there is no
Steve> ODBC problem and just a date issue. Could it be that the clocks on the server
Steve> and the client machine are just "enough" off to cause a problem?

I don't think so.

Could you try to execute the query in the mysql client and try to find
out why it doesn't find any matching rows.

Steve> | | query: Query = "UPDATE Fixed_Assets SET login='test' WHERE ID = 9 AND
Steve> login = 'crook' AND system_name = 'alpha' AND type = 'cpu' AND description =
Steve> 'PB46A-AA' AND location = 'FL2-2080' AND serial_number = 'KA513VUKN9' AND
Steve> nsf_number IS NULL AND ppe_number = 'PPE000000701' AND po_number = '52391' AND
Steve> vendor = 'DEC' AND date_installed = 19950413000000 AND status IS NULL AND
Steve> timestamp = 19961112000000 AND project = '170113' AND architecture = 'DEC' AND
Steve> operating_system IS NULL"

Regards,
Monty

Steve Webb
Guest

Posted: Tue Jun 29, 1999 6:53 pm Post subject: Re: ODBC: "Write conflict" from access.

Quote:

Here's some more info:

mysql> select * from Fixed_Assets where id='9';
+----+-------+-------------+------+-------------+----------+---------------+------------+--------------+-----------+--------+---------------------+--------+----------------+-----------------+---------+--------------+------------------+
| ID | login | system_name | type | description | location | serial_number |
nsf_number | ppe_number | po_number | vendor | date_installed | status
| timestamp | comments | project | architecture | operating_system
|
+----+-------+-------------+------+-------------+----------+---------------+------------+--------------+-----------+--------+---------------------+--------+----------------+-----------------+---------+--------------+------------------+
| 9 | crook | alpha | cpu | PB46A-AA | FL2-2080 | KA513VUKN9 |
NULL | PPE000000701 | 52391 | DEC | 1995-04-13 00:00:00 | NULL
| 19961112000000 | Alpha 250 4/266 | 170113 | DEC | NULL
|
+----+-------+-------------+------+-------------+----------+---------------+------------+--------------+-----------+--------+---------------------+--------+----------------+-----------------+---------+--------------+------------------+
1 row in set (0.00 sec)

mysql> UPDATE Fixed_Assets SET login='test' WHERE ID = 9 AND login = 'crook'
AND system_name = 'alpha' AND type = 'cpu' AND description = 'PB46A-AA' AND
location = 'FL2-2080' AND serial_number = 'KA513VUKN9' AND nsf_number IS NULL
AND ppe_number = 'PPE000000701' AND po_number = '52391' AND vendor = 'DEC' AND
date_installed = 19950413000000 AND status IS NULL AND timestamp =
19961112000000 AND project = '170113' AND architecture = 'DEC' AND
operating_system IS NULL;
Query OK, 0 rows affected (0.01 sec)

mysql> desc Fixed_Assets;
+------------------+---------------+------+-----+---------+----------------+
| Field | Type | Null | Key | Default | Extra |
+------------------+---------------+------+-----+---------+----------------+
| ID | int(11) | | MUL | 0 | auto_increment |
| login | varchar(25) | YES | | NULL | |
| system_name | varchar(25) | YES | | NULL | |
| type | varchar(15) | YES | | NULL | |
| description | varchar(55) | YES | | NULL | |
| location | varchar(55) | YES | | NULL | |
| serial_number | varchar(55) | YES | | NULL | |
| nsf_number | varchar(16) | YES | | NULL | |
| ppe_number | varchar(16) | YES | | NULL | |
| po_number | varchar(25) | YES | | NULL | |
| vendor | varchar(100) | YES | | NULL | |
| date_installed | datetime | YES | | NULL | |
| status | varchar(55) | YES | | NULL | |
| timestamp | timestamp(14) | YES | | NULL | |
| comments | mediumtext | YES | | NULL | |
| project | varchar(12) | YES | | NULL | |
| architecture | varchar(5) | YES | | NULL | |
| operating_system | varchar(11) | YES | | NULL | |
+------------------+---------------+------+-----+---------+----------------+
18 rows in set (0.00 sec)

The only thing that looks different is the "date_installed" field which gets
displayed in a "formatted" sense when it's displayed, but the data is the
same.

Should I change the "date_installed" from datetime to timestamp?

- Steve

On Tue, 29 Jun 1999, Michael Widenius wrote:

"Steve" == Steve Webb <swebb (AT) rap (DOT) ucar.edu> writes:

Steve> Another good guess, but I have a "DATETIME" and a "TIMESTAMP" field. No
Steve> "DATE" fields. I sense, from the proposed solutions so-far, that there is no
Steve> ODBC problem and just a date issue. Could it be that the clocks on the server
Steve> and the client machine are just "enough" off to cause a problem?

I don't think so.

Could you try to execute the query in the mysql client and try to find
out why it doesn't find any matching rows.

Steve> | | query: Query = "UPDATE Fixed_Assets SET login='test' WHERE ID = 9 AND
Steve> login = 'crook' AND system_name = 'alpha' AND type = 'cpu' AND description =
Steve> 'PB46A-AA' AND location = 'FL2-2080' AND serial_number = 'KA513VUKN9' AND
Steve> nsf_number IS NULL AND ppe_number = 'PPE000000701' AND po_number = '52391' AND
Steve> vendor = 'DEC' AND date_installed = 19950413000000 AND status IS NULL AND
Steve> timestamp = 19961112000000 AND project = '170113' AND architecture = 'DEC' AND
Steve> operating_system IS NULL"

Regards,
Monty

--
_ _ ____ _
____ __ _____| |__| |__ / __ _ _ __ __ _ _ _ ___ __| |_ _
(_-< V V / -_) '_ '_ / / _` | || / _/ _` | '_|/ -_) _` | || |
/__/_/_/___|_.__/_.__/ __,_|_,_____,_|_|(_)_____,_|_,_|
____/ http://www.rap.ucar.edu/~swebb

Steve Webb
Guest

Posted: Tue Jun 29, 1999 7:04 pm Post subject: Re: ODBC: "Write conflict" from access.

Hmmm. Bummer. Removing the timestamp field from the table didn't fix it
either.

- Steve

On Tue, 29 Jun 1999, Steve Webb wrote:

Quote:

I think I got it.

I have a field called "timestamp" and if I remove that field from the query,
it works great. I tried to rename "timestamp" to "time_stamp" but it didn't
do any good. I'm going to see if I can just remove the whole "timestamp"
field from the table next.

- Steve

On Tue, 29 Jun 1999, Steve Webb wrote:

Here's some more info:

mysql> select * from Fixed_Assets where id='9';
+----+-------+-------------+------+-------------+----------+---------------+------------+--------------+-----------+--------+---------------------+--------+----------------+-----------------+---------+--------------+------------------+
| ID | login | system_name | type | description | location | serial_number |
nsf_number | ppe_number | po_number | vendor | date_installed | status
| timestamp | comments | project | architecture | operating_system
|
+----+-------+-------------+------+-------------+----------+---------------+------------+--------------+-----------+--------+---------------------+--------+----------------+-----------------+---------+--------------+------------------+
| 9 | crook | alpha | cpu | PB46A-AA | FL2-2080 | KA513VUKN9 |
NULL | PPE000000701 | 52391 | DEC | 1995-04-13 00:00:00 | NULL
| 19961112000000 | Alpha 250 4/266 | 170113 | DEC | NULL
|
+----+-------+-------------+------+-------------+----------+---------------+------------+--------------+-----------+--------+---------------------+--------+----------------+-----------------+---------+--------------+------------------+
1 row in set (0.00 sec)

mysql> UPDATE Fixed_Assets SET login='test' WHERE ID = 9 AND login = 'crook'
AND system_name = 'alpha' AND type = 'cpu' AND description = 'PB46A-AA' AND
location = 'FL2-2080' AND serial_number = 'KA513VUKN9' AND nsf_number IS NULL
AND ppe_number = 'PPE000000701' AND po_number = '52391' AND vendor = 'DEC' AND
date_installed = 19950413000000 AND status IS NULL AND timestamp =
19961112000000 AND project = '170113' AND architecture = 'DEC' AND
operating_system IS NULL;
Query OK, 0 rows affected (0.01 sec)

mysql> desc Fixed_Assets;
+------------------+---------------+------+-----+---------+----------------+
| Field | Type | Null | Key | Default | Extra |
+------------------+---------------+------+-----+---------+----------------+
| ID | int(11) | | MUL | 0 | auto_increment |
| login | varchar(25) | YES | | NULL | |
| system_name | varchar(25) | YES | | NULL | |
| type | varchar(15) | YES | | NULL | |
| description | varchar(55) | YES | | NULL | |
| location | varchar(55) | YES | | NULL | |
| serial_number | varchar(55) | YES | | NULL | |
| nsf_number | varchar(16) | YES | | NULL | |
| ppe_number | varchar(16) | YES | | NULL | |
| po_number | varchar(25) | YES | | NULL | |
| vendor | varchar(100) | YES | | NULL | |
| date_installed | datetime | YES | | NULL | |
| status | varchar(55) | YES | | NULL | |
| timestamp | timestamp(14) | YES | | NULL | |
| comments | mediumtext | YES | | NULL | |
| project | varchar(12) | YES | | NULL | |
| architecture | varchar(5) | YES | | NULL | |
| operating_system | varchar(11) | YES | | NULL | |
+------------------+---------------+------+-----+---------+----------------+
18 rows in set (0.00 sec)

The only thing that looks different is the "date_installed" field which gets
displayed in a "formatted" sense when it's displayed, but the data is the
same.

Should I change the "date_installed" from datetime to timestamp?

- Steve

On Tue, 29 Jun 1999, Michael Widenius wrote:

"Steve" == Steve Webb <swebb (AT) rap (DOT) ucar.edu> writes:

Steve> Another good guess, but I have a "DATETIME" and a "TIMESTAMP" field. No
Steve> "DATE" fields. I sense, from the proposed solutions so-far, that there is no
Steve> ODBC problem and just a date issue. Could it be that the clocks on the server
Steve> and the client machine are just "enough" off to cause a problem?

I don't think so.

Could you try to execute the query in the mysql client and try to find
out why it doesn't find any matching rows.

Steve> | | query: Query = "UPDATE Fixed_Assets SET login='test' WHERE ID = 9 AND
Steve> login = 'crook' AND system_name = 'alpha' AND type = 'cpu' AND description =
Steve> 'PB46A-AA' AND location = 'FL2-2080' AND serial_number = 'KA513VUKN9' AND
Steve> nsf_number IS NULL AND ppe_number = 'PPE000000701' AND po_number = '52391' AND
Steve> vendor = 'DEC' AND date_installed = 19950413000000 AND status IS NULL AND
Steve> timestamp = 19961112000000 AND project = '170113' AND architecture = 'DEC' AND
Steve> operating_system IS NULL"

Regards,
Monty

--
_ _ ____ _
____ __ _____| |__| |__ / __ _ _ __ __ _ _ _ ___ __| |_ _
(_-< V V / -_) '_ '_ / / _` | || / _/ _` | '_|/ -_) _` | || |
/__/_/_/___|_.__/_.__/ __,_|_,_____,_|_|(_)_____,_|_,_|
____/ http://www.rap.ucar.edu/~swebb

--
_ _ ____ _
____ __ _____| |__| |__ / __ _ _ __ __ _ _ _ ___ __| |_ _
(_-< V V / -_) '_ '_ / / _` | || / _/ _` | '_|/ -_) _` | || |
/__/_/_/___|_.__/_.__/ __,_|_,_____,_|_|(_)_____,_|_,_|
____/ http://www.rap.ucar.edu/~swebb

Steve Webb
Guest

Posted: Tue Jun 29, 1999 7:09 pm Post subject: Re: ODBC: "Write conflict" from access. (FIXED IT!)

I removed both the datetime and timestamp fields from the record and it all
magicially went back to working again!

Incredible!

Anyway, I'm going to play with it and possibly move the fields back in and see
if it changes anything, but for the time being, I think that I'm satisfied.

Thanks for all of your help..

- Steve

On Tue, 29 Jun 1999, Steve Webb wrote:

Quote:

Hmmm. Bummer. Removing the timestamp field from the table didn't fix it
either.

- Steve

On Tue, 29 Jun 1999, Steve Webb wrote:

I think I got it.

I have a field called "timestamp" and if I remove that field from the query,
it works great. I tried to rename "timestamp" to "time_stamp" but it didn't
do any good. I'm going to see if I can just remove the whole "timestamp"
field from the table next.

- Steve

On Tue, 29 Jun 1999, Steve Webb wrote:

Here's some more info:

mysql> select * from Fixed_Assets where id='9';
+----+-------+-------------+------+-------------+----------+---------------+------------+--------------+-----------+--------+---------------------+--------+----------------+-----------------+---------+--------------+------------------+
| ID | login | system_name | type | description | location | serial_number |
nsf_number | ppe_number | po_number | vendor | date_installed | status
| timestamp | comments | project | architecture | operating_system
|
+----+-------+-------------+------+-------------+----------+---------------+------------+--------------+-----------+--------+---------------------+--------+----------------+-----------------+---------+--------------+------------------+
| 9 | crook | alpha | cpu | PB46A-AA | FL2-2080 | KA513VUKN9 |
NULL | PPE000000701 | 52391 | DEC | 1995-04-13 00:00:00 | NULL
| 19961112000000 | Alpha 250 4/266 | 170113 | DEC | NULL
|
+----+-------+-------------+------+-------------+----------+---------------+------------+--------------+-----------+--------+---------------------+--------+----------------+-----------------+---------+--------------+------------------+
1 row in set (0.00 sec)

mysql> UPDATE Fixed_Assets SET login='test' WHERE ID = 9 AND login = 'crook'
AND system_name = 'alpha' AND type = 'cpu' AND description = 'PB46A-AA' AND
location = 'FL2-2080' AND serial_number = 'KA513VUKN9' AND nsf_number IS NULL
AND ppe_number = 'PPE000000701' AND po_number = '52391' AND vendor = 'DEC' AND
date_installed = 19950413000000 AND status IS NULL AND timestamp =
19961112000000 AND project = '170113' AND architecture = 'DEC' AND
operating_system IS NULL;
Query OK, 0 rows affected (0.01 sec)

mysql> desc Fixed_Assets;
+------------------+---------------+------+-----+---------+----------------+
| Field | Type | Null | Key | Default | Extra |
+------------------+---------------+------+-----+---------+----------------+
| ID | int(11) | | MUL | 0 | auto_increment |
| login | varchar(25) | YES | | NULL | |
| system_name | varchar(25) | YES | | NULL | |
| type | varchar(15) | YES | | NULL | |
| description | varchar(55) | YES | | NULL | |
| location | varchar(55) | YES | | NULL | |
| serial_number | varchar(55) | YES | | NULL | |
| nsf_number | varchar(16) | YES | | NULL | |
| ppe_number | varchar(16) | YES | | NULL | |
| po_number | varchar(25) | YES | | NULL | |
| vendor | varchar(100) | YES | | NULL | |
| date_installed | datetime | YES | | NULL | |
| status | varchar(55) | YES | | NULL | |
| timestamp | timestamp(14) | YES | | NULL | |
| comments | mediumtext | YES | | NULL | |
| project | varchar(12) | YES | | NULL | |
| architecture | varchar(5) | YES | | NULL | |
| operating_system | varchar(11) | YES | | NULL | |
+------------------+---------------+------+-----+---------+----------------+
18 rows in set (0.00 sec)

The only thing that looks different is the "date_installed" field which gets
displayed in a "formatted" sense when it's displayed, but the data is the
same.

Should I change the "date_installed" from datetime to timestamp?

- Steve

On Tue, 29 Jun 1999, Michael Widenius wrote:

"Steve" == Steve Webb <swebb (AT) rap (DOT) ucar.edu> writes:

Steve> Another good guess, but I have a "DATETIME" and a "TIMESTAMP" field. No
Steve> "DATE" fields. I sense, from the proposed solutions so-far, that there is no
Steve> ODBC problem and just a date issue. Could it be that the clocks on the server
Steve> and the client machine are just "enough" off to cause a problem?

I don't think so.

Could you try to execute the query in the mysql client and try to find
out why it doesn't find any matching rows.

Steve> | | query: Query = "UPDATE Fixed_Assets SET login='test' WHERE ID = 9 AND
Steve> login = 'crook' AND system_name = 'alpha' AND type = 'cpu' AND description =
Steve> 'PB46A-AA' AND location = 'FL2-2080' AND serial_number = 'KA513VUKN9' AND
Steve> nsf_number IS NULL AND ppe_number = 'PPE000000701' AND po_number = '52391' AND
Steve> vendor = 'DEC' AND date_installed = 19950413000000 AND status IS NULL AND
Steve> timestamp = 19961112000000 AND project = '170113' AND architecture = 'DEC' AND
Steve> operating_system IS NULL"

Regards,
Monty

--
_ _ ____ _
____ __ _____| |__| |__ / __ _ _ __ __ _ _ _ ___ __| |_ _
(_-< V V / -_) '_ '_ / / _` | || / _/ _` | '_|/ -_) _` | || |
/__/_/_/___|_.__/_.__/ __,_|_,_____,_|_|(_)_____,_|_,_|
____/ http://www.rap.ucar.edu/~swebb

--
_ _ ____ _
____ __ _____| |__| |__ / __ _ _ __ __ _ _ _ ___ __| |_ _
(_-< V V / -_) '_ '_ / / _` | || / _/ _` | '_|/ -_) _` | || |
/__/_/_/___|_.__/_.__/ __,_|_,_____,_|_|(_)_____,_|_,_|
____/ http://www.rap.ucar.edu/~swebb

--
_ _ ____ _
____ __ _____| |__| |__ / __ _ _ __ __ _ _ _ ___ __| |_ _
(_-< V V / -_) '_ '_ / / _` | || / _/ _` | '_|/ -_) _` | || |
/__/_/_/___|_.__/_.__/ __,_|_,_____,_|_|(_)_____,_|_,_|
____/ http://www.rap.ucar.edu/~swebb

Display posts from previous:

	MySQLTalk.org Forum Index -> MySQL ODBC	All times are GMT
Page 1 of 1

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum