What I want to achieve is.

Justak: What about while closing database if lock tables exist

Gellis: But I will come back again

Curnow: Sly01: already answered. you wait until the lock is released.

Brookshire: I just started using the 5.6.26 client, and suddenly my prompt is truncated.

Zerzan: Looks like n has changed behaviour

Snedeger: Can anyone take a look at these two mysql queries and change it to a left join query

Ruggles: Http://pastebin.com/9sSS5HLk

Weinheimer: SELECT * FROM transactions LEFT JOIN log_items USING id WHERE .

Kretzschmar: How can I use the output from this statement in an update query? SELECT FLOORRAND * 999 AS random_num FROM posts WHERE “random_num” NOT IN SELECT menu_order FROM posts where post_type = ‘my_cpt’ limit 1

Bissett: What do you want to update?

Kretzschmar: I want to generate random numbers in a column

Hamman: UPDATE posts SET random_column = FLOORRAND * 999 WHERE .

Kretzschmar: So I just have to omit the first select?

Portlock: Your query is confusing tbh

Riston: Dbolser: I am getting the following error.

Teklu: Mysql SELECT * FROM transactions LEFT JOIN log_items USING id WHERE status=’running’ AND created_at current_timestamp – INTERVAL 1 HOUR;

Boothroyd: ERROR 1052 23000: Column ‘created_at’ in where clause is ambiguous

Sokoloff: Jonfatin-: the answer is the same as it was an hour ago. prefix the field with the table name.

Qasba: Jonfatin-: which created_at do you mean? transactions.created_at or log_items.created_at ?

Serban: Jonfatin-: what snoyes said

Bouwman: Snoyes: what client version are you running? CAn you try “R nnntest”

Brackelsberg: 5.6.26 on Windows. Three blank lines and the word ‘test’.

Peragine: Snoyes: weird, I’m not seeing the blank lines, but rather it ‘eats’ one of the given characters, i.e. I get “t” in the above example

Berne: This is “mysql Ver 14.14 Distrib 5.6.26, for Linux x86_64 using EditLine wrapper”

Koener: Yet another reason to switch to Windows ;

Labreque: Wonder if it’s editline vs readline thing

Sordia: Hi guys, I am try to get better of dynamics between innodb_buffer_pool_dump_at_shutdown and innodb_max_dirty_pages_pct. After reading the do***entation and this article https://www.percona.com/blog/2009/04/15/how-to-decrease-innodb-shutdown-times/. I think that these parameters have a little conflict. For example if I want to use warm cache feature, I should use innodb_buffer_pool_dump_at_shutdown and not use innodb_

Schaller: Max_dirty_pages_pct. Because innodb_max_dirty_pages_pct will flush all pages to the disk, and they no longer will be part of the innodb_buffer_pool_dump_at_shutdown? Am I missing something?

Mammenga: So here’s an interesting question about performance_schema events_statements_summary_by_digest. Any query that starts with a BEGINSTART TRANSACTION generates a digest for BEGIN, but any queries within that transaction are not logged in the performance_schema

Leinenbach: MySQL tested

Kretzschmar: Erm I get the a Vasko error “near ‘AS random_num FROM posts WHERE “random_num” NOT IN SELECT menu_order FROM g’ at line 1 ”

Talboti: Dbolser: I got it to work however its not displaying the join on the left for target_id how would I add that to the join statement

Bockenkamp: Pom999: when bufferpools are “saved”, what you’re actually saving is not the data, but a small metadata file of what pages in innodb were in memory

Fornerod: Http://pastebin.com/25SMQPVc

Kessans: Pom999: when you startup again, the innodb pages listed in the save file are loaded from innodb

Rudh: Jonfatin-: ask for id with teh table prefix

Kretzschmar: What I want to achieve is generate a random number for each row in a table and save that number in an existing column. the random numbers have to be unique for each row and have to be from a specific range