Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Column default expressions using sequences are not treated as identity columns in H2 - Merge [#5331] #5336

Closed
lukaseder opened this issue Jun 7, 2016 · 0 comments
Closed

Column default expressions using sequences are not treated as identity columns in H2 - Merge [#5331] #5336

lukaseder opened this issue Jun 7, 2016 · 0 comments
Labels
C: Code Generation C: DB: H2 P: Medium R: Fixed T: Defect
Milestone
Version 3.8.3

Comments

@lukaseder
Copy link
Member

No description provided.

@lukaseder lukaseder added this to the Version 3.8.3 milestone Jun 7, 2016
lukaseder added a commit that referenced this issue Jul 4, 2016
@lukaseder
Version 3.8.3 - July 4, 2016
795dcbf 
================================================================================

This is a patch release with some useful fixes for the 3.8 branch

Features and Improvements
-------------------------
#5338 - Log a warning in the code generator if a table is reported to have two identity columns

Bug Fixes
---------
#5324 - Wrong precision generated in automatic CAST for DB2 and other databases
#5336 - Column default expressions using sequences are not treated as identity columns in H2
#5339 - Nested record generated when TABLE.COLUMN "overlaps" with a table called TABLE_COLUMN for MySQL
#5359 - Incorrect order of HSQL column definition tokens: "DEFAULT" and "NULL"
#5365 - Avoid parsing ? in plain SQL if followed immediately by another operator-like character in PostgreSQL
#5367 - Record.update() produces wrong update counts in HSQLDB
#5369 - Plain SQL batches produce wrong INFO messages about bind value count mismatches
#5381 - MySQL STRAIGHT_JOIN is not implemented correctly
#5386 - Excessive WARN log level when a generated object has no name
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C: Code Generation C: DB: H2 P: Medium R: Fixed T: Defect
Projects
None yet
Milestone
Version 3.8.3
Development

No branches or pull requests
1 participant
@lukaseder