[sqlalchemy] Re: Add arbitrary information to some classes - Rick Morrison - com.googlegroups.sqlalchemy

14 messages in com.googlegroups.sqlalchemy[sqlalchemy] Re: Add arbitrary inform...

From	Sent On	Attachments
Paul Johnston	26 Oct 2007 05:33
Rick Morrison	30 Oct 2007 08:08
jason kirtland	30 Oct 2007 09:58
Rick Morrison	30 Oct 2007 10:13
jason kirtland	30 Oct 2007 10:22
Rick Morrison	30 Oct 2007 10:32
jason kirtland	30 Oct 2007 11:03
Rick Morrison	30 Oct 2007 11:17
Paul Johnston	31 Oct 2007 04:54
Rick Morrison	01 Nov 2007 07:40
Michael Bayer	01 Nov 2007 09:13
Rick Morrison	02 Nov 2007 11:05
Paul Johnston	05 Nov 2007 12:10
jason kirtland	05 Nov 2007 12:20

Subject:	[sqlalchemy] Re: Add arbitrary information to some classes
From:	Rick Morrison (rick...@gmail.com)
Date:	10/30/2007 10:13:33 AM
List:	com.googlegroups.sqlalchemy

personal opinion: I'm not wild about either 'attributes' or 'properties', (a) they seem too long, and (b) yes, they are too similar to generic ORM terms

many many moons ago (pre Windows-1.0) I used an Ascii-GUI thing called C-scape (I think it's called "vermont views" now).

anyway, most of its objects had a space for a pointer to arbitrary user data, and they consistently used something like "udata" for the name of the pointer.

So I'm +1 on a short, non-generic and uniquely "user-y" kind of name like "udata". I know it sounds ugly, but we're dealing with database and ORM terminology. Just about every generic name you can think of is bound to be confused with something database-oriented.

Rick