Re: subtable <-> bigtable
| От | Andrew G. Hammond |
|---|---|
| Тема | Re: subtable <-> bigtable |
| Дата | |
| Msg-id | 1008477777.22582.7.camel@xyzzy обсуждение исходный текст |
| Ответ на | subtable <-> bigtable (Peter Pilsl <pilsl@goldfisch.at>) |
| Ответы |
Re: subtable <-> bigtable
|
| Список | pgsql-general |
On Sat, 2001-12-15 at 20:54, Peter Pilsl wrote: > I've a very big table that is read very frequently and I want to split > this table in more subtables with different permissions for > insert/update/delete. I need to keep the big table too, cause the > reading application can only deal with one table. So you want to have different permissions depending on what sort of data, right? > Is there any construct I can use to form a 'virtual table' that > contains all the subtables or any other method to make my work easier. Yep, and they're called VIEWs. Personally, if the data models well to a single table, then I'd stick with a single table design. Use VIEWs to break up access and write RULEs to handle INSERT, UPDATE and DELETES. -- Andrew G. Hammond mailto:drew@xyzzy.dhs.org http://xyzzy.dhs.org/~drew/ 56 2A 54 EF 19 C0 3B 43 72 69 5B E3 69 5B A1 1F 613-389-5481 5CD3 62B0 254B DEB1 86E0 8959 093E F70A B457 84B1 "To blow recursion you must first blow recur" -- me
Вложения
В списке pgsql-general по дате отправления: