on 7/3/2000 12:40 PM, "Riley, Cameron" <[EMAIL PROTECTED]> wrote:
> Thanks, glad it was of use, the only thing I would suggest is putting the
> executeOdbcTurbineSchema.java, Turbine-AccessY2K.mdb and the
> turbine-table-relationships.gif into a directory off of schemas named "ODBC"
> or something like that. It looks a bit ugly thrown in with the SQL files.
I think it is fine. If you know what you are looking for, it all becomes
pretty clear. Maybe what would be good is for you to write up a bit of HTML
documentation on how to use all the ODBC stuff. I personally like to just
use Netscape Composer to draft up stuff. It makes it pretty easy.
> VISITOR and VISITORROLE arent connected to permissions or roles by any
> relationships. Is the idea of the schema to give each role many permissions
> and for a visitor to only have one role or many roles? I dont think I am
> clear on how the permissions and roles link up to the visitor table.
essentially, it is a terminology issue: VISITOR == USER. The confusion is
that some stuff is called VISITOR and some stuff is called USER. It is a
legacy issue that isn't really worth resolving because it is easy enough to
figure it out. :-)
> ok got it. I have put the DBOdbc.java for the turbine connection pool up at;
>
> http://users.rcn.com/kymcam/
My only suggestion here is to throw SQLException ("Not implemented") in the
places where things are not implemented or not needed.
Lastly, why are you using ODBC? :-) Are there no native JDBC drivers for
your database? ODBC is a kludge these days. I haven't seen someone using it
with Java in quite a long time. JDBC + ODBC is like a compatibility layer on
top of a compatibility layer.
-jon
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
