When looking for a table, a user will always search their own schema first, then the public schema. When combined with table inheritance, this allows the creation of user-specific tables that isolate a user’s data but can still be included in aggregate queries by selecting from the master table.
The statement: ‘COPY tablename FROM STDIN;’ performs an INSERT of data received from the client, but does not obey RULEs ON INSERT to a view. It will still activate triggers, but unfortunately, creating triggers on views is currently beyond my skill level.
Database or Schema | Magnus Hagander
This post was a lifesaver, my thanks to Magnus for writing it. It explains the possible use of separate user schemas in designing a shared database. I was looking for this exact technique for an online poker hand history application that I’m working on.
wow i’ve learned a lot in the last couple weeks… too much to write about right now. hopefully i can take a vacation once schools out. tonight i’m researching postgreSQL table inheritance, it’s going to change my life
Apparently there was a faulty stick of RAM lying on my desk, when I put it into the server and turned the machine on there was a loud popping sound, sparks, and a bad smell. So no more linux until I get a new motherboard/cpu/ram combo. le sigh
I was trying to listen to “El Revolver” on IMEEM today for my Spanish lit class and it wouldn’t work… WHYY? It would have been nice to listen to it in audio.
In the end I went to google translate for El Revolver by Emilia Pardo Bazan
It’s pretty fun trying to contribute better translations… But I better get back to trying to write the essay I’m supposed to turn in.