SQL Exception when creating spreadsheet
Description
Environment
Linux Debian 7,
Oracle Java 1.7
All Browsers
Observations
Attachments
- 10 Nov 2014, 03:58 PM
- 10 Nov 2014, 03:58 PM
Requirement Yogi
Activity
Adrien Ragot (Old account)December 1, 2014 at 9:43 AM
Hi Fritz,
Alright, I'll close the ticket just for my own clarity, feel free to open it again whenever needed.
Sorry it didn't work out with your installation,
Adrien
Fritz GernethDecember 1, 2014 at 9:39 AM
Hello,
unfortunatelly I could not resolve this issue. I tried enforcing explicit time zones in different ways but all failed so far.
I'll look into this once we have the capacity to organize a separate PgSQL database. For now we are only runninig on MySQL.
Thanks for your help on this issue though.
(I think you can close this issue as we were running off-topic anyway)
Regards,
Fritz
Adrien Ragot (Old account)December 1, 2014 at 12:29 AM
Hi Fritz,
Have you finally succeeded to resolve your timezone issue? I don't actively do anything on my side but if you have a suggestion, I'm open.
Cheers,
Adrien
Fritz GernethNovember 14, 2014 at 3:24 PM
Hello,
no problem. Thanks for your great support 
The reason why the timezone is invalid: some Synology-Company decided to change the time zone names to "Timezone/whatever" with non standard cities in the Postgres internal time zone database. So setting it to this non-standard time zone will break confluence for sure
Regards,
Fritz
Adrien Ragot (Old account)November 14, 2014 at 2:17 PM
Hi Fritz,
I'm really sorry but I'm out of ideas:
I don't manage timezones at all in Play SQL,
I know the timezone is set to the JDBC's client,
I know the timezone management has changed with the Postgres driver
9.2, so maybe you should check you use a more recent driver than the
database,I wonder why the "Europe/Berlin" time is still sent. You could try
setting the timezone of the Confluence JVM to something else using
-Duser.timezone="..." (Here's documentation to change Confluence's
system properties
<https://confluence.atlassian.com/display/DOC/Configuring+System+Properties>).
It will however change the time for all of Confluence.I wonder why the "Europe/Berlin" timezone is invalid. Why wouldn't it
be among the default Postgres timezones? Is it because you've upgraded from
an old version of Postgres?
I'm sorry that I can't find enough information about. Hope one of those
will help you.
Best regards,
Adrien
On Fri, Nov 14, 2014 at 2:05 PM, Fritz Gerneth (JIRA) <
Details
Details
Assignee
Reporter
Components
Fix versions
Affects versions
Requirement Yogi
Linked requirements
Requirement Yogi
When creating a new spreadsheet, we are receiving the following error (excerpt):
{"message":"ERROR: column \"current_schema\" does not exist\n Position: 143\nQuery:SQLStatement [has-table, sql=\n select COUNT(*)\n from INFORMATION_SCHEMA.TABLES\n where LOWER(TABLE_NAME) = LOWER(?)\n and TABLE_SCHEMA = CURRENT_SCHEMA\n , 1 arguments: PLAYSQL_SETTINGS]","status-code":500,"stack-trace":"com.playsql.jdbc.JdbcException: ERROR: column \"current_schema\" does not exist\n Position: 143\nQuery:SQLStatement [has-table, sql=\n select COUNT(*)\n from INFORMATION_SCHEMA.TABLES\n where LOWER(TABLE_NAME) = LOWER(?)\n and TABLE_SCHEMA = CURRENT_SCHEMA\n , 1 arguments: PLAYSQL_SETTINGS]\n\tat com.playsql.jdbc.JdbcWrapper.prepareStatement(JdbcWrapper.java:363)\n\tat com.playsql.jdbc.JdbcWrapper.query(JdbcWrapper.java:230)\n\tat com.playsql.jdbc.JdbcWrapper.query(JdbcWrapper.java:189)\n\tat com.playsql.jdbc.JdbcWrapper.queryForOne(JdbcWrapper.java:125)\n\tat com.playsql.jdbc.JdbcWrapper.queryForOne(JdbcWrapper.java:121)\n\tatA screenshot of the screen showing the error and the full message are attached.
The query works perfectly fine when making the CURRENT_SCHEMA a function call instead.
We'll provide any additional information as required of course.