[GitHub] [incubator-pekko-persistence-r2dbc] danischroeter commented on issue #19: Revisit usage of `pekko_` schema prefix?

["danischroeter (via GitHub)" <gi...@apache.org>]

danischroeter commented on issue #19:
URL: https://github.com/apache/incubator-pekko-persistence-r2dbc/issues/19#issuecomment-1506646772

   @mdedetrich I think the prefix should be removed. It does not add value and is inconsistent. Persistence-cassandra also does not have a prefix. E.g journal table just called `messages` see
   https://github.com/apache/incubator-pekko-persistence-cassandra/blob/main/core/src/main/scala/org/apache/pekko/persistence/cassandra/journal/CassandraJournalStatements.scala
   https://github.com/apache/incubator-pekko-persistence-cassandra/blob/main/core/src/main/resources/reference.conf#L105
   
   More interestingly most tables do not have a prefix - just projection
   
   see https://github.com/apache/incubator-pekko-persistence-r2dbc/blob/main/ddl-scripts/create_tables_postgres.sql
   ```
   DROP TABLE IF EXISTS event_journal;
   DROP TABLE IF EXISTS snapshot;
   DROP TABLE IF EXISTS durable_state;
   DROP TABLE IF EXISTS pekko_projection_offset_store;
   DROP TABLE IF EXISTS pekko_projection_timestamp_offset_store;
   DROP TABLE IF EXISTS pekko_projection_management;
   ```
   


-- 
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-unsubscribe@pekko.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org