Support for schema other than Public (postgres)

Questions
1

Is there support within the Servoy Developer to work with postgres under a different schema than “Public”?

Say, i would make a table ‘Articles’ under:

  • Public.Articles
  • Alternate.Articles

I know you can make tables in another schema, and read then back within the Servoy’s Developer.
(although, you have to distinct them by prefixing the table name, otherwise you couldn’t tell)

However, when i start using the table from the non public schema, the foundsets and qbselects can’t be used. (table unknown, so it seems…)

Regards,
Raymond

2

Raymond,

Servoy has a setting that you can put in the servoy.properties file for the server definition.

server.n.prefixTables=true

Where n is replaced with the proper server nr.

If you modify that, Servoy will prefix tables more often, and you probably can access the table in the other schema.

Note that Developer may write that file, so you need to stop Developer first, edit the file and start Developer again.

Rob

3

Note that you can also enter the schema in de connection properties.

So if you work with different schemas, you can create a database connection for each schema.
Under the “Database Servers” node in the Solution explorer, you’ll then have multiple connections to the same database, but using different schemas.