jon * wrote:
<snip>
> > I have an Oracle version of the default_roles_permissions.sql script - that
> > is to say one that uses NEXTVAL from the various sequences as part of the
> > INSERT statements.
>
> Actually...don't use that way...simply make the columns a number. the
> org.apache.turbine.util.db.IDBroker will take care of the rest (assuming
> that you have also imported/converted the id_table.sql script).
Hmm, I had missed the id_table script.
Is guess this is used instead of the sequences ? If so are the sequences that
are defined in the Oracle_user_roles_permissions.sql needed ? I guess the
Oracle script has become a bit stale - for example it doesn't include the
Jobentry table.
Also, is it a problem that the id_table.sql script sets the NEXT_ID to 1 ? I
mean do things get out of synch when the default_roles_permissions.sql script is
run ? Or does Turbine take this into account.
Thanks for the info on the CVS clients - I will take a look.
Finally, I first learned about Turbine from the java.apache.org page. I have
been lurking on this list for a while - and have decided to dive in and see if I
can learn more about how Turbine works. This comes after I completed work on my
own (somewhat simplistic) Servlet framework.
Gary Bartlett
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
