Hello all,
I would like to propose that we remove blob fields from the
following tables:
permission, role, group, user
I am not sure of the purpose of the fields. Were they meant to be
a catch all of some sort?
Here's why:
1. For a your basic web app, these fields won't be needed.
2. If you do need to add more fields to the individual tables,
a better design would be to just extend off the base class and add the
additional fields that you do need, or create another table that
has a foreign key into one of the aforementioned tables. A great
use of torque anyway.
3. If you are using a database that doesn't support blobs, you need
to remove or re-map the fields anyway.
4. We can tidy up the documentation. We really don't need to tell
people how to patch their jdbc driver to add blob support. Assuming
if one's wants blob support, they will chose a database that supports
it or they will have to knowledge to patch the jdbc driver themselves.
While we are on the subject, at one point their was discussion of
renaming the group table. People seem to be confused of how
we use the group table with how they are used to thinking about
groups. What if we rename the table to realm or project realm?
mike
--
-------------------------------------------------
I am Vinz, Vinz Clortho. Keymaster of Gozer,
Volguus Zildrohar, Lord of the Sebouillia.
Are you the Gatekeeper?
-------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
