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

Escape character should be added to PGSQL queries (bis) #69

Closed
kopax opened this issue Dec 24, 2016 · 5 comments
Closed

Escape character should be added to PGSQL queries (bis) #69

kopax opened this issue Dec 24, 2016 · 5 comments

Comments

@kopax
Copy link

kopax commented Dec 24, 2016

Did you noticed #48 as not been completed entirely ? I have the feeling not. (sorry for duplicate)

@easybest
Copy link
Owner

I have found the reason.

you can use 1.0.8.BUILD-SNAPSHOT and have a try again.

easybest pushed a commit that referenced this issue Dec 24, 2016
@kopax
Copy link
Author

kopax commented Dec 24, 2016

Strange, I've build from master a 1.0.8 snapshot, I've checked before if the build contains that modification

builder.append(dialect.wrapColumnName(association.getJoinColumnName())).append(",");

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

@easybest
Copy link
Owner

@JdbcType(BIGINT)
@OneToOne(referencedColumnName = "COMPANY_ID")
@NotNull
private Company company;

change to :

@OneToOne
@JoinColumn(name = "COMPANY_ID")
@NotNull
private Company company;

easybest pushed a commit that referenced this issue Dec 24, 2016
closed #69 : Escape character should be added to PGSQL queries (bis)
@easybest
Copy link
Owner

Is it OK now ? @kopax

@kopax
Copy link
Author

kopax commented Dec 24, 2016

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

easybest pushed a commit that referenced this issue Nov 12, 2019
easybest pushed a commit that referenced this issue Nov 12, 2019
easybest pushed a commit that referenced this issue Nov 12, 2019
closed #69 : Escape character should be added to PGSQL queries (bis)
easybest added a commit that referenced this issue Nov 8, 2021
easybest added a commit that referenced this issue Nov 8, 2021
easybest added a commit that referenced this issue Nov 8, 2021
closed #69 : Escape character should be added to PGSQL queries (bis)
easybest pushed a commit that referenced this issue Nov 8, 2021
easybest pushed a commit that referenced this issue Nov 8, 2021
easybest pushed a commit that referenced this issue Nov 8, 2021
closed #69 : Escape character should be added to PGSQL queries (bis)
easybest added a commit that referenced this issue Nov 8, 2021
easybest added a commit that referenced this issue Nov 8, 2021
easybest added a commit that referenced this issue Nov 8, 2021
closed #69 : Escape character should be added to PGSQL queries (bis)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants