pjfanning commented on issue #275: URL: https://github.com/apache/pekko-persistence-jdbc/issues/275#issuecomment-2740425435
@patsta32 Hear me out. I'm not trying to shoot down #276 and I'm willing to collaborate on that PR. But: Since we are already in a bit of a mess here with schema support, I'm wondering if the first step is to see if we can document our way out of the problem. So with Postgres DB, you can define a default schema for a user. ``` ALTER USER your-user set SEARCH_PATH = 'schema_name'; ``` Would you be in a position to try that out? The sql scripts in https://github.com/apache/pekko-persistence-jdbc/tree/main/core/src/main/resources/schema/postgres could theoretically be modified to have the `public.` part of the commands removed. Or for the scripts to be modified to use `?` as a placeholder for the schema name. We would then run the commands in the scripts as preparedStatements and when executing them, we would provide the schemaName. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@pekko.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@pekko.apache.org For additional commands, e-mail: notifications-h...@pekko.apache.org
