Rus wrote:
>
> That's strange. I thought that auto_increment field not suppose to use same
> value. May be it's problem connected with transaction. Check doc's on
> COMMIT. Try to set AUTOCOMMIT=1
It's real. Here is a demonstration. First, the table definition...
+---------+------------------+------+-----+---------+----------------+
| Field | Type | Null | Key | Default | Extra |
+---------+------------------+------+-----+---------+----------------+
| vik_ID | int(10) unsigned | | PRI | 0 | auto_increment |
| vikname | varchar(255) | | | | |
+---------+------------------+------+-----+---------+----------------+
And here is a demonstration of the behavior. It is pretty weird:
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 22 to server version: 3.22.32
Type 'help' for help.
mysql> select * from Vik;
+--------+---------+
| vik_ID | vikname |
+--------+---------+
| 1 | Da man |
| 2 | Da sow |
+--------+---------+
2 rows in set (0.01 sec)
mysql> delete from Vik where vik_ID=2;
Query OK, 1 row affected (0.00 sec)
mysql> select * from Vik;
+--------+---------+
| vik_ID | vikname |
+--------+---------+
| 1 | Da man |
+--------+---------+
1 row in set (0.00 sec)
mysql> insert into Vik (vikname) VALUES ('George');
Query OK, 1 row affected (0.00 sec)
mysql> select * from Vik;
+--------+---------+
| vik_ID | vikname |
+--------+---------+
| 1 | Da man |
| 2 | George |
+--------+---------+
2 rows in set (0.00 sec)
mysql>
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
