----- Original Message -----
From: Christian Nichols <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, June 25, 2000 9:17 PM
Subject: Database access in TurbineUser classes
> We are very interested in this project for integration into our reporting
> portal product for e-commerce companies. I have a couple of questions for
> the developers of the database "peer" classes of TurbineUser.
>
> 1. While most of the database access is based on the minimal set of
> functionality present in the util and db packages, it seems that the
> TurbineUserPeer class also uses (and duplicates) some functionality in the
> working-dogs.com Village package. For instance, the Schema, Column and
> other classes are used to build a list of column names for use in saving
the
> hash table. It seems (on a first look) that this functionality is
available
> via the TurbineDatabaseMap class. Is this class in transition or is it
> basically complete?
>
The code in TurbineUserPeer that I think you are referring to was written
early on while the Map classes were being written. It attempts to save
anything in the permanent hashtable whose key is a column name in the
visitor table to the correct column and then everything else goes into
object_data. If you see some efficiency gains or just clearer code please
submit patches. Otherwise I would say, it works.
> 2. The documentation states that the peer classes are the best way to use
> the database classes as these are the classes which are used internally by
> Turbine. Will this be true in the future or is it expected to change.
>
The peer classes are the preferred way in Turbine to get object-relational
persistence. The primary advantage being that it is simple and "complete".
There are problems for which a fuller persistence layer would be desirable
and then you are free to start with what the Opal developers left us,
Castor, EJB, or some other persistence mechanism. Of course, if the license
is right and a better general solution presents itself, it can replace Peers
as the basic persistence mechanism.
John McNally
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
