[Meservy]

Thank you that solution worked wonderfully. . . . Appreciate your help.

'peterlaursen' wrote on '19:

This is a server problem (all 4-digit error messages starting with “1” are) .  The same error would occur with any client executing the same statement.

Please check this google-result:

http://www.google.dk/search?client=opera&rls=da&q=Error+Code+:+1206+The+total+number+of+locks+exceeds+the+lock+table+size&sourceid=opera&ie=utf-8&oe=utf-8

.. if you find something relevant.  

I suggest that you try to

1) execute UNLOCK TABLES

2) (or simpler) restart the server

3) and if server is a version affected by one of the bugs reported in above search upgrade the server. BTW: what is the server version?

[Meservy]

'peterlaursen' wrote on '10:

“I would think the order if no order is specified it would be the order that the records were added”.  I think it is not always. The server may order by a(n visible or non-visible) index .  I do not remember details but I think I had one case once where InnoDB and MyISAM behaved differently in this respect. 

I can understand the problem of course.  You have a large table when you open the table in SQLyog DATA tab you see old data that are not interesting.  The problem however is in my understanding a problem with SQL databases as such and not a problem with a client program.

But this “I can get to the end of the table using these fields if I could put numbers in larger than 999,999” is valid, I think.  Even if only 6 digits are displayed it should take longer input and the inputted value should 'roll'.

This definitely should be a BUG request because the maximum digits that can be entered is 6 digits.

[Meservy]

'peterlaursen' wrote on '09:

 Please explain: What is the “first” and “last” record in a table and what is “the end of the table”.  A database table is not ordered.  Only when specifying an ORDER BY clause in a a query, data are ordered.

It is true of course that the server will return a specific order if no ORDER BY is specified.  But that order may differ depending on server version, storage engine, indexes on the table etc. Only in case there is an auto_increment Primary Key I think this will be possible.  After executing SQL commands like 'REPAIR TABLE' the “order” may change. Also after dumping and importing it may change.

But please detail … we'd like to improve usability for users of course,  but we cannot promise that 'last records' are displayed as there are no 'last records' unless you *define* an ordering criteria (the PK-order or a timestamp column for instance) as what you consider the order.  

I understand what your are saying but regardless of whether an order by is specified or not a record SET is returned and displayed in a specific order. I would think the order if no order is specified it would be the order that the records were added. This is all beside the point as I am looking at the functionality of the Table Data tab. . . if I click on the “All rows” radio button and the table is too large I will get an error and SqlYog will memory dump. I have a file that contains more than a million records. The row positioning fields are “First row nnnnnn and nnnnnn rows” I can get to the end of the table using these fields if I could put numbers in larger than 999,999. Why is the field so short. I can't imagine I am on the only person with a table that has more than a million records.

If I have all rows displayed then the “ctrl end” combination of keys will take me to the end of the displayed table. I need to postion to the end of the selected table set without pulling the entire table into memory.

[Author]

Posts