Quoting Dan Diephouse <[EMAIL PROTECTED]>:
> OK, I think I wasn't clear about my question....
>
> I wasn't having problems creating the database, I just wanted to point
> out
> that anyone who has a version before 3.23.2 is going to have problems
> (like
> me, but not Jason Harrop).
Sorry, I misunderstood your question too.
> My real question is once those tables are created why isn't slide
> populating
> them like it did with hsql? Slide doesn't seem to read in the
> domain.xml
> file and populate the database with default actions, users, etc like it
> did
> with hsql....
>
> Is it supposed to do this or do I need to do:
> INSERT INTO OBJECTS VALUES ("/actions", "org.apache.slide.ActionNode")
> etc, until I have a working set of actions and users so I use slide....
No, it should work just the same.
Your trace last time indicated errors dealing with the transactional commands,
so that's probably why the namespace wasn't populated.
The errors pointed to an enlist error, which could be caused by the mySQL
driver throwing an exception when tryin to call connection.setAutoCommit(false);
The newest mySQL actually supports transactions, so that may be why it works
better.
A solution could be to do a mySQL store stripped of all transactional commands.
I'll try to commit a specilized store soon.
Remy
