Hi, I found the problem. It's quite serious, and I will create a new release later this week.
Queries that are ordered by an indexed column returned no rows in certain cases (if all rows were deleted from the table previously, and there is a low number of rows in the table, and when not using other conditions, and when using the default b tree index). Regards, Thomas On Mon, Apr 6, 2009 at 3:54 AM, fed <[email protected]> wrote: > > Hi, > > i have a strange problem with H2 (Version 1.1.110), i have this > table: > > create table dipendenti_stampa( > id identity not null primary key, > id_dipendente bigint not null, > nome longvarchar not null, > cognome longvarchar not null, > matricola varchar(10) not null, > badge varchar(10) not null, > profilo_orario varchar(100), > presente tinyint, > timbratura_presenza varchar(100)); > > if on this table i do > "select * from dipendenti_stampa" i get the data back > > but if i do > > "select * from dipendenti_stampa order by id" i get NO data from it. > > > It's very strange.. i have to say that i had a similar problem with h2 > when i tried to use "order by" on another table and on an index field > (in this case id too is an index field). > > Another important consideration: i tested that if i have less than 59 > rows in the table i get this behaviour, with more or equal to 59 all > works ok and i get the data from the query. > > Bye thanks for the help. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/h2-database?hl=en -~----------~----~----~----~------~----~------~--~---
