Absolutely... will do. If I survive :-)
On 9/16/2019 9:24 PM, Tellier Benoit wrote:
Nice,
Thanks for the feedback!
I believe writing a short blog-post that we could then share with the
community, once you get this up and running will be really valuable.
Regards,
Benoit
On 17/09/2019
Nice,
Thanks for the feedback!
I believe writing a short blog-post that we could then share with the
community, once you get this up and running will be really valuable.
Regards,
Benoit
On 17/09/2019 00:27, Jerry Malcolm wrote:
> Thanks so much for all of the advice. I think I've got a
Thanks so much for all of the advice. I think I've got a resolution.
1) First misassumption... mySQL makes no attempt to order tables based
on foreign key dependency. I just assumed the tables would be ordered
correctly (bad habit assuming). But due to possible cyclic
dependencies,
Jerry
It looks like the export did not export the data in the proper order. You are
trying to put mail into the mail table that is assigned to mailboxes that do
not exist yet. Three options:
1, create ‘dummy mailboxes’ for those messages to fall into. This may be the
faster workaround for the
Hi Jerry,
James is relying on an ORM (openjpa) for database persistance.
We do test things on top of a H2 database, and (a ltle bit) on top
of PostgresSQL & derby database.
SQL database compatibility is a tough topic, we had some issues in the
past with some reserved name, too long table
This is a bit off-topic... more of a database question... but it IS
about the James database. Hopefully somebody understands the James
schema details enough to recognize the errors below and explain why the
import is failing. I posted this in the AWS RDS forum. But no help
there so far
