Mark Michalek

Jeff, that is an excellent find. Sorry you had to struggle with that. I opened an issue in the Symmetric issue tracker so this can get fixed. https://www.symmetricds.org/issues/view.php?id=4211 Thanks, Mark

Hoarau, SymmetricDS will write the sym tables to the default database for your JDBC URL/user combination. You might be able to specify the public schema on your URL. Or you could create a symmetric database user whose database search path / default database is public. Mark

Hello. I like your idea #1. Can you describe in more detail what a "reinit" is for you? Thanks, Mark

Steven - did you try the sym_trigger SOURCE_SCHEMA_NAME maybe? If your triggers are appearing on the wrong table, the problem is most likely in the sym_trigger configuration which is what controls the physical trigger creation. Mark

Hi Steven, here's basically how this works: 1) You configure your engine.properties file with a database URL and database user. That DB connection will have a default database that it connects to. 2) The sym tables will be created on the default database from the properties file. 3) When it comes to your triggers, if you leave off the catalog/schema, then it the triggers would attempt to create on the default database from the properties file. 4) If your application tables are in a different database...

Hello userx, Can you describe the problem you are trying to solve a little more? It seems like you are trying to get a message back to central, but what is the nature of that message? My guess is it woould be better to implement a seperate status table and set that up for sync as well. The setSqlMessage is really reserved for SQL errors generated during Symmetric's internal processing, so I would not recommend modying that field. Does that make sense? Thanks, Mark

Stian, good job digging into it and thank you for posting your solution.

Nicolas, I think you are on the right track. Good work and thanks for posting your solution.