Hi, > The table may or may not have primary key, and I will not be > able to create a new column or modify the existing column as it will > give a wrong number of columns to the traget user.
So basically you would like to have some kind of primary key in a table where you didn't define a primary key. I don't think that's a good solution. It will not work in other databases. If I was you, I would define a primary key column and 'hide' that column from the other users in some way if really required. > Does the below Roadmap (Priority 2) point address my above issue ? > --> ROW_NUMBER (not the same as ROWNUM) No. ROW_NUMBER is something else. ROWID is what you want. It is also on the roadmap now, but at the very end. > Also any consideration for my below suggestion : > Thread :http://groups.google.com/group/h2-database/browse_thread/ > thread/601db912cb9eed1c/a8760b1fa25fc184?lnk=gst&q=columns > +Names#a8760b1fa25fc184 > jdbc:h2:<url>;CASE_SENSITIVE_COLUMN={TRUE|FALSE} . No, it is not my plan to implement that, I don't see why at the moment. To me, it sounds like the application should be fixed, and the database is behaving correctly (according to how other databases behave, and according to the SQL standard). Regards, Thomas --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
