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.

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

Compilation error in compiled code when column is called "null" #4236

Closed
lukaseder opened this issue Apr 27, 2015 · 0 comments
Closed

Compilation error in compiled code when column is called "null" #4236

lukaseder opened this issue Apr 27, 2015 · 0 comments

Comments

@lukaseder
Copy link
Member

Interestingly, null is not in the list of keywords, as it isn't a keyword in Java - but it's still a reserved words which shouldn't be generated as such.

It's rare for a DB column to be called "NULL" as it would need to be quoted in SQL as well.

@lukaseder lukaseder added this to the Version 3.7.0 milestone Apr 27, 2015
lukaseder added a commit that referenced this issue Apr 29, 2015
================================================================================

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

Bug fixes
---------
#4224 - ORA-00904: "SYS"."ALL_PROCEDURES"."OBJECT_ID": invalid
identifier when using the code generator with Oracle 10g
#4225 - ScalaGenerator logs that it generates XXX.java files
#4227 - ScalaGenerator should have its own list of reserved words
#4235 - JDBCDatabase calls Meta.getPrimaryKeys() for all schemas, not
just for input schemas
#4236 - Compilation error in compiled code when column is called "null"
#4240 - JDBCDatabase fetches tables from all schemas, not just from
input schemas
#4246 - HANADataType isn't initialised in SQLDataType's static
initialiser block
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant