Re: [HACKERS] Re: [COMMITTERS] 'postgres95/src/bin/destroydb destroydb.sh'
| От | Ross Johnson |
|---|---|
| Тема | Re: [HACKERS] Re: [COMMITTERS] 'postgres95/src/bin/destroydb destroydb.sh' |
| Дата | |
| Msg-id | 8ac7ca7f323f7cb51f4d288d9fa661f8 обсуждение исходный текст |
| Ответ на | [HACKERS] Re: [COMMITTERS] 'postgres95/src/bin/destroydb destroydb.sh' (The Hermit Hacker <scrappy@hub.org>) |
| Список | pgsql-hackers |
On Sun, 1 Jun 1997, The Hermit Hacker wrote: > On Sun, 1 Jun 1997, Thomas G. Lockhart wrote: > > > Marc G. Fournier wrote: > > > I am including a patch for destroydb to ask for confirmation before > > > deleting databases (after I accidentally deleted mine)...destroydb -y > > > would force delete without any confirmation. > > > > Uh, "destroydb" would seem to be a specific-enough command that if you > > type it, you actually wanted to delete a database :) > > > > Would have preferred that the behavior remained as-is, myself. > > Its too simple to backout (I love CVS *grin*)...anyone else have an > opinion one way or the other? Its sort of like some systems alias rm -i to > rm...just in case Having had to restore entire systems because someone typed "rm -r abc *" instead of "rm -r abc*", I'd put the confirmation in. IE. it's not that you didn't mean to type "destroydb", but whether you get the database name correct or not. How often does someone destroy a database anyway that a confirmation makes it more of a pain? Why not provide a command line flag to override confirmation for those who might call destroydb from a script. +----------------------+---+ | Ross Johnson | | E-Mail: rpj@ise.canberra.edu.au | Info Sciences and Eng|___| | University of Canberra | FAX: +61 6 2015227 | PO Box 1 | | Belconnen ACT 2616 | WWW: http://willow.canberra.edu.au/~rpj/ | AUSTRALIA | +--------------------------+ ------------------------------
В списке pgsql-hackers по дате отправления: