NoOova: Because that’s the.

Amescua: Can anyone help me with this simple question?

Bloyer: Amescua: You don’t have to ask to ask, or state: “I have a question”, Don’t ask: “Is anyone around?” or “Can anyone help?”. Just Ask The Question. Also, please read:

Amescua: My last INSERT feels wrong, but it seems to work perfectly

Waltos: So, I’ll give that backupfile to my colleague, who asked me to make the dump.

Mackert: Salle, something like this?,47078,51428

Heximer: Amescua: So your feel is wrong

Turomsha: How to Recover InnoDB MySQL Table Data from ibdata and .frm Files

Amescua: Im I using composite keys wrong?

Yerbich: Salle: it is not works, i guess

Heximer: Amescua: SELECT * FROM Orders; right after INSERT will help you understand why.

Amos: I have a new problem, my server running mysql and recently the queries became much slower than use to be, i tried many options but for some reason nothing help, my.cnf file:

Norsen: Salle: RESULTS in query with ‘FOR UPDATE’ including fantom rows. Results in simple select query does not include fantom rows.

Heximer: Amescua: Paste the result which should contain one row and explain why do you think it is wrong

Amescua: Just wait a min, my mysql-workbench crashed

Dircks: Salle: if i do ‘select .’ and then same ‘select . for update’ i got different rows!

Shifflette: In repeatable read mode!

Heximer: Amescua: Forget aboyt workbench if you want to learn MySQL

Buttram: Amescua: also forget everythink about sql standarts, if you want to learn mysql

Heximer: NoOova: With explicit START TRANSACTION or without it? With autocommit mode ON or OFF?

Reyner: In transaction ofcource

Lafferty: With repeatable read isolation level

Heximer: NoOova: You are always in transaction with InnoDB

Radell: Ok. with begin keyword

Heximer: NoOova: I am not interested in playing “20 questions game” you know. Pastebin somewhere a repeatable test case

Blalack: Salle, can one extract that database and from file from ibdata?

Aspen: Salle: sorry about it

Heximer: Amescua: Even better. SELECT after each of your INSERTs because that will give you much better idea what is going on. You can use sqlfiddle too

Strobeck: Salle, if so, then I might ask someone to help me with that task.

Amescua: OrderNo: 1 orderDate: 2014-12-15 deliveryDate: NULL orderStatus: NULL Customer_customerNo: 1

Amescua: Seems right to me, and it works on more “advanced” queries. But then I might be blind to the actuall problem.

Heximer: Floogy: Most probably no

Heximer: Amescua: So what is the problem? :

Droke: Is there another possibility to recover the database?

Heximer: Amescua:!9/ecea34/1

Flies: The owner didn’t made any backups. I just try to get backups/dumps, to transfer everything to a sane server.

Amescua: I just cant grasp that when I set a pk to be composite, I only need to refer to that table with the single number and not a composite value

Brocks: Salle:

Heximer: Amescua: All looks fine there except for the mangled DATE, but that’s sqlfiddle quirk

Heximer: NoOova: That’s because SELECT is non-locking in InnoDB

Steich: Yep. it reads from snapshot

Lyne: But why select for update read actual records? Not snapshoted?

Purdie: Salle, can you tell me some of the methods in question, as keywords for giving hints to the service stuff of the new server?

Heximer: NoOova: Because that’s the first time this transaction is trying to lock rows