Rafal Krzewski wrote:
I'd like to sum up the discussion that followed
my proposal.
Nobody objected to removing the address info from TURBINE_USER table.
The fields that stay are:
integer USER_ID
varchar(32) LOGIN_NAME
varchar(32) PASSWORD_VALUE
varchar(99) FIRST_NAME
varchar(99) LAST_NAME
varchar(99) EMAIL
varchar(99) CONFIRM_VALUE
datetime CREATED
datetime MODIFIED
datetime LASTLOGIN
blob OBJECTDATA
Note!
USER_ID is numerical id used *internally* by DBSecurityManager -
your apps should not depend on it if you want them to be compatible
with user data backends different than a relational DB.
In a hybrid setup including user data in LDAP and roles/permissions
in a DB, TURBINE_USER table will be filled with LOGIN_NAME -> USER_ID
to retain integer only TURBINE_USER_GROUP_ROLE_PERMISSION table.
Someone reported a problem with identifiers longer than 14 characters
on DB2 (and Iterbase?). My proposal is to define a
ShortNamesTurbineMapbuilder
extending TurbineMapBuilder, and overriding the get* methods as
necessary.
I'm not sure if implementing automatic name shortening in Torque is
feasible.
I'd suggest creating a separate short-names-turbine-schema.xml, that
could
be used to generate SQL for those databases.
If nobody posts objections to the above, I'll commit the changes
tomorrow.
Rafal
--
Rafal Krzewski
Senior Internet Developer
mailto:[EMAIL PROTECTED]
+48 22 8534830 http://e-point.pl
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
