I use the following method which is not session dependent (and therefore
not as as complicated as your requirement):
Define a model for the query
Drop the table before the query is executed
Use Postgresql's 'SELECT INTO' or 'CREATE TABLE AS XXX FROM' in the query
to populate the table.
Maybe in y
Thanks again Niphlod; I think this will be a handy technique to have up my
sleeve.
--
there's no such thing as a db that holds records just for the duration of a
session automatically (with a session being n>1 requests).
Just add the usual suspects to the table"updated_on", a "user_id" and a
"status" column, with a default "temp" and change it to "confirmed" as soon
as the u
3 matches
Mail list logo