-
Notifications
You must be signed in to change notification settings - Fork 73
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
Escape character should be added to PGSQL queries (bis) #69
Comments
I have found the reason. you can use 1.0.8.BUILD-SNAPSHOT and have a try again. |
Strange, I've build from master a 1.0.8 snapshot, I've checked before if the build contains that modification
and I still have this error : ### Error updating database. Cause: org.postgresql.util.PSQLException: ERROR: column "company_ID" of relation "CUSTOMER" does not exist
Position: 150
### The error may involve com.domain.customerManagement.Customer._insert-Inline
### The error occurred while setting parameters
### SQL: insert into "CUSTOMER"("ACTIVE","CREATION_DATETIME","FIRST_NAME","LAST_NAME","MODIFICATION_DATETIME","PRINCIPAL_PHONE","PRINCIPAL_ADDRESS","VERSION","company_ID") values(?,?,?,?,?,?,?,?,?) So now it is escaped with double quote, but the table table name is still a lower case |
@JdbcType(BIGINT)
@OneToOne(referencedColumnName = "COMPANY_ID")
@NotNull
private Company company; change to : @OneToOne
@JoinColumn(name = "COMPANY_ID")
@NotNull
private Company company; |
closed #69 : Escape character should be added to PGSQL queries (bis)
Is it OK now ? @kopax |
I've just tested out but not in depth, It is now working without any hassle. Thank you for that, At the mean time, merry x-mas && happy new year |
closed #69 : Escape character should be added to PGSQL queries (bis)
closed #69 : Escape character should be added to PGSQL queries (bis)
closed #69 : Escape character should be added to PGSQL queries (bis)
closed #69 : Escape character should be added to PGSQL queries (bis)
Did you noticed #48 as not been completed entirely ? I have the feeling not. (sorry for duplicate)
The text was updated successfully, but these errors were encountered: