Error Creating Table PSQLException

Classic Servoy
1

I have run into this error message a couple of times before (3.1.x) and I don’t understand what causes it or what I am doing wrong. Running 3.5rc2 (working great!) and I added a temporary column for a data load (via Postgres PGAdmin) to the backend table. Usual “in and out” of Developer to ensure update of the Repository to recognize the new column. Recent version of Postgres.

I thought I would try running the Import function to load some data and the following error is raised:

Error creating table, org.postgresql.util.PSQLException: ERROR: column “temp_country” of relation “subregion” does not exist
com.servoy.j2db.persistence.RepositoryException: org.postgresql.util.PSQLException: ERROR: column “temp_country” of relation “subregion” does not exist
org.postgresql.util.PSQLException: ERROR: column “temp_country” of relation “subregion” does not exist

I am not convinced this is a Postgres error: I can go over to PGAdmin and delete the column fine. We are using a Postgres repository (likely why the PG error report). However, the question remains as to why the column “temp_country” is thought to be connected to a non-existent relation (“subregion” is a table).

Anyone run into this before? Resolution?

Thanks, Michael

2

Could it be your driver?

3

Marcel,

Hmmm … I hadn’t thought about that angle. A couple of months ago when I saw this problem Servoy Support gave me an SQL query to examine the repository for entries highlighting this records with the “relation” = “tablename”. I ran the query and all turned out to be fine within the repository itself. Interestingly, if Servoy creates the column all is fine. It’s only when I do my usual loop (PowerDesigner, generate DDL-delta’s, adjust Postgres schema OR adjust PG directly via PGAdmin) and make changes outside Servoy that I have ever seen this intermittent error.

All of this may point to the JDBC driver itself … I’ll do some more testing today to see if I can find a pattern :-) somewhere. The usual “fun” when it is intermittent like this …

Thanks!

4

Please also see my post (potentially related but on a different topic and thread) if you are monitoring this area within Postgres … we believe this issue is potentially related (still investigating) to the Postgres release level (and driver level as well):

http://forum.servoy.com/viewtopic.php?t=8601