Re: [h2] Low prio change request: Add support for ALTER TABLE .. RENAME COLUMN .. TO ..
Added support for these 2 things -- 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 h2-database+unsubscr...@googlegroups.com. To post to this group, send email to h2-database@googlegroups.com. Visit this group at https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
Re: [h2] Unique index or primary key violation in version 1.4.191
I've been using MVCC with PageStore for years. LOBS don't work very well (but I didn't want them in the db anyway, so we don't use LOBS). Haven't had any issues with anything else though. Doesn't mean bugs don't exist though. You only get the issue with MVCC on though hey? On 17/02/2016 1:18 PM, Noel Grandin wrote: At some point in the future is all I can say, not anytime soon. My point was more that MVCC on PageStore is a dead end for us, so we're not going to expend any effort debugging problems with it. So if you want reliability, use PageStore without MVCC. -- 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 h2-database+unsubscr...@googlegroups.com. To post to this group, send email to h2-database@googlegroups.com. Visit this group at https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
Re: [h2] Low prio change request: Add support for ALTER TABLE .. RENAME COLUMN .. TO ..
Thank you very much! 2016-02-17 10:21 GMT+01:00 Noel Grandin : > Added support for these 2 things > > > -- > You received this message because you are subscribed to a topic in the > Google Groups "H2 Database" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/h2-database/8zt8k8hU1jA/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > h2-database+unsubscr...@googlegroups.com. > To post to this group, send email to h2-database@googlegroups.com. > Visit this group at https://groups.google.com/group/h2-database. > For more options, visit https://groups.google.com/d/optout. > -- 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 h2-database+unsubscr...@googlegroups.com. To post to this group, send email to h2-database@googlegroups.com. Visit this group at https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
Re: [h2] Unique index or primary key violation in version 1.4.191
I have not tested the scenario with MVCC off because that is pretty much a non-starter for our performance requirements. It is kind of an odd bug because the application, the embedded h2 web console, and the h2 shell do not have a problem with the database file. Only other database viewers seem to have the problem - of which I certainly do not have an exhaustive list. When I started looking into the bug I did not realize that I'd be able to access the database file via the H2 shell, so it was initially a higher priority bug. As I mentioned, the most important thing for me that has come out of this is learning about MVCC support/stability for PageStore. Noel mentioned it is not a priority for them, which I totally agree with, and I would not want anyone to spend more of their time trying to research this because the solution for me is to switch to MVStore and to use the H2 shell instead of some of db viewer. On Wednesday, February 17, 2016 at 7:08:20 AM UTC-6, Kartweel wrote: > > I've been using MVCC with PageStore for years. LOBS don't work very well > (but I didn't want them in the db anyway, so we don't use LOBS). Haven't > had any issues with anything else though. > > Doesn't mean bugs don't exist though. > > You only get the issue with MVCC on though hey? > > On 17/02/2016 1:18 PM, Noel Grandin wrote: > > At some point in the future is all I can say, not anytime soon. My > > point was more that MVCC on PageStore is a dead end for us, so we're > > not going to expend any effort debugging problems with it. > > > > So if you want reliability, use PageStore without MVCC. > > > > > -- 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 h2-database+unsubscr...@googlegroups.com. To post to this group, send email to h2-database@googlegroups.com. Visit this group at https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
[h2] JDBC API Non-compliance in Connection.createArray()
As per the JavaDoc, Connection.createArray() should raise a SQLFeatureNotSupportedException if the feature is not supported, and a SQLException for other errors such as if a database error occurs, the JDBC type is not appropriate for the typeName and the conversion is not supported, the typeName is null or this method is called on a closed connection. H2 versions 1.4.190 and 1.4.191 tested. This is important when one is attempting to code SQL-portable applications and needs to discover the functionality exposed by the underlying JDBC database. Also, the SQLState value should be in the class "0A" (zero-A), but instead it's returned as "HYC00". You should also endeavor to fix all the other instances of non-conformance in other methods, since DB feature discovery is an important part of the WORA model. -- 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 h2-database+unsubscr...@googlegroups.com. To post to this group, send email to h2-database@googlegroups.com. Visit this group at https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
