Hi, Only the most popular features of other database can be implemented in a "compatibility mode" item. In this case, I don't think it is a popular nor important compatibility item, sorry.
Regards, Thomas On Wednesday, March 7, 2012, Joe Parsons wrote: > I was under the impression that the purpose of a "compatibility mode" was > to make the product more compatible and to better support the syntax of a > specific RDBMS. Why would adding this change under the PostgreSQL > compatibility mode affect MySQL? > > -Joe > > -- > You received this message because you are subscribed to the Google Groups > "H2 Database" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/h2-database/-/IFVB7JPU99cJ. > To post to this group, send email to > h2-database@googlegroups.com<javascript:_e({}, 'cvml', > 'h2-database@googlegroups.com');> > . > To unsubscribe from this group, send email to > h2-database+unsubscr...@googlegroups.com <javascript:_e({}, 'cvml', > 'h2-database%2bunsubscr...@googlegroups.com');>. > For more options, visit this group at > http://groups.google.com/group/h2-database?hl=en. > -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to h2-database@googlegroups.com. To unsubscribe from this group, send email to h2-database+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
