mysql> select version();
+--+
| version()|
+--+
| 5.1.30-community-log |
+--+
1 row in set (0.00 sec)
mysql> select @@tx_isolation;
+-+
| @@tx_isolation |
+-+
| REPEATABLE-READ |
+
Are you doing the insert and the select in different sessions, ie
different connections to the server(different terminals)?
This might simply be an intended symptom of isolation levels and InnoDB
MVCC(multi versioning concurrency control).
In addition, can you tell us what you get from:
mysql>
I´d just like to know why do you wanna do a select in a record which was
just inserted.
Could you explain a little more?
""Tachu®"" escreveu na mensagem
news:339ce61f-848a-4c83-b566-ef0e176e6...@gmail.com...
> I'm having some weird issues that might be common but im not sure. I have
> a ve
I'm having some weird issues that might be common but im not sure. I
have a very write intensive innodb table that sometimes i do an insert
and then do a select for the row i just inserted and it wont show up.
this is on the same host its not replication lag but on the same host.
on differe
