Brett Sanger wrote:
> 
> Because databases don't store arrays?

Postgres does support arrays, and I suspect some others do too. This was
part of the "Object Relational" database movement which never took off.
I'm not a personal fan of this feature and haven't used it yet myself. 

> As I said, putting the permissions into databases is more powerful,
> but sometimes the above is easier to maintain than a table of permissions,
> a table of users, a table of which users are in which groups, a table of
> what permissions each group has, etc.

As someone who once when down the road of using all those tables to
store access information, I have to agree. :) 

And here's some documention of a recent spring day "at the office":

http://mark.stosberg.com/About/Currents/2002/spring_fever_juggling.swf
http://mark.stosberg.com/Skate/Photos/hip_ollie_large.jpg

 -mark

---------------------------------------------------------------------
Web Archive:  http://www.mail-archive.com/[email protected]/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to