Anyone care to comment on this? It may seem like a trivial thing to prevent running into this but it's not.
We have an application where users provide variable names (limited to [A-Za-z][A-Za-z0-9]*) that we use as column names in tables representing the underlying data. Simply quoting them in all our SQL ought to be enough to prevent problems. As it is now we are sitting on a time bomb that already exploded once when a user picked CHECK as a variable name. Using mangled names is not an option since the database tables are accessed by external (reporting) tools and the names showing up there need to match the names provided by users. Is there anything we can do to work around this? -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
