on 5/12/01 4:00 PM, "Turpin, Jay" <[EMAIL PROTECTED]> wrote:
> I don't know if this might solve your problem with using Oracle sequence,
> but to get autoincrement to work properly, we had to modify the following
> class:
>
> org.apache.turbine.util.db.map.TurbineMapBuilder
>
> It has hard-coded all of the table maps use for the Turbine Security layer
> and specified that each table should use IDBROKER. Once we changed it to
> AUTOINCREMENT for SQL Server 2000, the security classes began working
> properly with the tables we created. For Oracle, you should be able to
> change it to SEQUENCE for each table.
>
> Also, we noticed that this class overwrites the table map for TurbineUser,
> even though it's defined in it's own mapbuilder class. This class should be
> modified to either remove the TurbineUser table map definition, or perform a
> check to only create a tablemap if it doesn't already exist.
>
> Regards,
> Jay Turpin
> Intel Corporation
Now all we need to do is teach you how to submit patches so that others can
take advantages of your bug fixes...
:-)
-jon
--
If you come from a Perl or PHP background, JSP is a way to take
your pain to new levels. --Anonymous
<http://jakarta.apache.org/velocity/ymtd/ymtd.html>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
