Thanks for clearing that up Thomas. I found your reply informative, and humorous. :) And great work on H2. I am introducing it at my company as a way to write isolated unit tests against an in memory database, and it is already generating new ideas. Thanks taking the time to set me straight.
On Feb 17, 11:24 pm, Thomas Mueller <[email protected]> wrote: > Hi, > > > I clearly stated that I could not use another word > > I'm sorry, I didn't see this. > > > and asked for a work around. > > Then the workaround is to use "LIMIT". > > > Yet you still suggest that I > > find a different word > > So that you don't have to use double quotes. There is no other reason. > > > That's still not an option. > > In that case use "LIMIT". > > > But now my question is, is there something wrong with using quotes as > > illustrated? > > No. > > > Is there a performance impact, compatibility issues, is > > it deprecated? Why wasn't using quotes your suggestion? > > Just because it seems simpler not to use quoted names. > > > I'm tempted to put quotes around all column names unless there is a problem > > with it. > > You can do that. > > > So it seems that the quotes are actually part of the name rather than > > a way to escape the name. > > No, it's an escape mechanism. > > 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 -~----------~----~----~----~------~----~------~--~---
