Doesn't work. I like wrapping up the entire file in a transaction so that if
I make a stupid syntax error or the like, I can just do a rollback. Because
of that, the transaction enters abort state. I suppose I can just stop using
transactions and use this method.
---(end
How can I duplicate the behavior of:
DROP TABLE IF EXISTS mytable;
CREATE TABLE mytable (
blah,
blah
);
INSERT INTO mytable
(blah)
VALUES
(blah);
in other words, so that I have a single sql file that restores the database
to a known state.
---(end of broadcast)---
d the ability to remove
rows the ability to do so, but to not loose the information for a week or
so, so that the choice can be double checked by someone else.
jason watkins
