On 27 Nov, 2005, at 7:08 am, Jorge Godoy wrote:
Why not using TgUser, TgGroup and TgPermission? They are specific to
TurboGears, after all...
This is actually in response to all the suggestions of names for the
identity SQLObjectProvider model classes. First the current model
classes all create tables in the database prefixed with "tg_". I
think that's a fine solution, because those tables are (basically)
turbogears specific information.
I'm reluctant to prefix the SQLObjectProvider model classes with
anything. My reluctance stems from the fact that these classes are
already uniquely identified by their module:
turbogears.identity.model.somodel. They don't *need* a prefix of any
sort. Except to get around a design flaw in SQLObject.
If I'm going to be forced to have a prefix on these classes, the
prefix WILL serve the same purpose of the package: to identify the
classes as belonging to the SQLObjectProvider model. Therefore, I
think the prefix ought to be SO rather than TG.
I'm definitely not interested in a prefix as long as "Identity". The
difference between a prefix like "SO" and "Identity" is like the
difference between accidentally poking yourself in the eye with a
sharp stick and carving your initials on the inside of your skull
with that sharp stick.
So, if I have to do the wrong thing, I'd rather do the wrong thing
that has the least letters.
--
Jeff Watkins
http://newburyportion.com/
'I know about people who talk about suffering for the common good.
It's never bloody them! When you hear a man shouting "Forward, brave
comrades!" you'll see he's the one behind the bloody big rock and the
one wearing the only really arrow-proof helmet!'
-- Rincewind gives a speech on politics. (Terry Pratchett,
Interesting Times)
