> Indeed. Patch attached.
I just applied it :) Thanks a lot !
> Be warned that it DOES require recreating the tables (because it
> replaces the integer 'type' column with a varchar column. By the way -
> you might want to check the type and size I used there - I don't know
> much SQL, so it might not be the best choice).
>
> I spent quite a while trying to figure out why things weren't working
> after I editing the wrong version of the file, not realising another
> existed - why are there two (very similar, but not identical) copies of
> each of the stores? The patch is for the one which is actually used - is
> the other dead code, or is it used under other circumstances (in which
> case the patch needs to be applied to that as well - it should do so
> reasonably cleanly, but no guarantees).
Sorry about the trouble.
The other one is indeed temporarily dead (I think I'll remove it to avoid
confusing people).
The reason for having multiple JDBC stores is the compatibility problems in
SQL with the advanced types (varchar, ....). I'm not a database guru, so the
only thing I could come up with is a hSQL ready JDBC store. Apparently, it
doesn't work with mySQL, and probably others.
The other store will be a production oriented JDBC store, with the goal of
making it as compliant as possible. It should probably also be optimized
(the current one abuses joins).
The set of stores in "reference" will be a set of reference implementation
of stores, which can be used for testing (finding if a bug in in Slide's
core or a behavior problem in the store).
> > I'll also add a set of standard roles to make things easier (Guest,
User,
> > Root).
>
> I haven't done this, but it's pretty trivial. Anyway, roles now actually
> work with the JDBC store. Yay!
Cool !
Remy
