there are two possible ways to solve it (besides actually creating ID_TABLE
and dropping yours, btw what's the reason you can't do that?):
- create your own version of IDBroker and change table/column names in there
- they are hardcoded in the source (or better create version which takes
table & column names from props and submit the patch)
- if your database allows that, create a view, named ID_TABLE with proper
column names based on your table. If your DB allows updatable views this
should work (i have not tried this, tell us about the results). This is
probably the fastest way.
fedor.
-------------------------------
The Joy of CVS
> -----Original Message-----
> From: Nick Pomfret [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, September 06, 2001 2:01 AM
> To: turbine-dev
> Subject: using turbine with an alternative id table
>
>
> I'm new to turbine so I'm not too sure if I've got the right
> group to send
> this to, however...
>
> My problem is that I'd like to use turbine with an existing schema
> containing a table for generating primary key values (in a
> similar way to
> the 'id_table' in turbine). This id table has a different name and
> structure and I'm having trouble getting it to work. When
> attempt to insert
> a new row I get a "java.sql.SQLException: ERROR: Relation
> 'id_table' does
> not exist" error - which I guess makes sense as turbine
> doesn't 'know' about
> my id table.
>
> So is it possible to describe to turbine my id table, or do I need to
> override some functionality to get this to work?
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
