Re: [HACKERS] CBAC (content based access control), OIDs, auto fields
От | darcy@druid.net (D'Arcy J.M. Cain) |
---|---|
Тема | Re: [HACKERS] CBAC (content based access control), OIDs, auto fields |
Дата | |
Msg-id | m0xt3He-00000XC@druid.net обсуждение исходный текст |
Ответ на | CBAC (content based access control), OIDs, auto fields (De Clarke <de@ucolick.org>) |
Список | pgsql-hackers |
Thus spake De Clarke > In fact, while I'm dreaming: why not have a set of *three* > table creation options? > -recno causes an autonumber field to be prepended > to each record. > -user causes the user ID of the inserting process > to be prepended to each record. > -stamp causes the timestamp at insert time to be > prepended. > The fields could have fixed names (like oid), say "recno", > "user", and "stamp" -- or as a luxury option the user could > supply their names as part of the option syntax: > -user uid -stamp itime -recno seqno > > Like oid, these fields would *not appear* in result streams > unless explicitly included in the FSE. 'select *' would not > reveal them, but 'select oid,recno,user,stamp,*' would show > all fields. (If these options are specified at table create I like the general idea but I think they should either show up when '*' is selected or else automatically put them into each table. If you don't then generic functions will have problems. -- D'Arcy J.M. Cain <darcy@{druid|vex}.net> | Democracy is three wolves http://www.druid.net/darcy/ | and a sheep voting on +1 416 424 2871 (DoD#0082) (eNTP) | what's for dinner.
В списке pgsql-hackers по дате отправления: