Hi, The column_list is more a comment currently, maybe it should be removed. I wonder if the following could be used?
select c.table_schema, c.table_name, c.unique_index_name, c.column_list, i.column_name from information_schema.constraints c, information_schema.indexes i where c.table_schema = i.table_schema and c.table_name = i.table_name and c.unique_index_name = i.index_name; Regards, Thomas On Wed, Feb 12, 2014 at 3:09 PM, Lukas Eder <[email protected]> wrote: > > 2014-02-12 15:03 GMT+01:00 Noel Grandin <[email protected]>: > > >> >> On 2014-02-12 16:00, Lukas Eder wrote: >> >>> >>> In the extremely unlikely event of someone using a comma in their column >>> names AND using that column in a constraint, >>> then the INFORMATION_SCHEMA.CONSTRAINTS.COLUMN_LIST column will yield >>> wrong values. Example: >>> >> >> Patches are welcome :-) > > > I knew that would come :-) > > First, you guys decide if CSV is a valid workaround for H2, or if you have > any other idea. Then, I might provide a patch, although I'm sure this would > take you 10seconds as opposed to me 20mins and then you 30seconds again ;-) > > -- > 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 http://groups.google.com/group/h2-database. > For more options, visit https://groups.google.com/groups/opt_out. > -- 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 http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/groups/opt_out.
