Re: [HACKERS] psql Week 2
От | Bruce Momjian |
---|---|
Тема | Re: [HACKERS] psql Week 2 |
Дата | |
Msg-id | 199910112029.QAA04083@candle.pha.pa.us обсуждение исходный текст |
Ответ на | psql Week 2 (Peter Eisentraut <peter_e@gmx.net>) |
Ответы |
Re: [HACKERS] psql Week 2
|
Список | pgsql-hackers |
> * Ctrl-C only sends cancel request if query in progress (otherwise > default action = terminate program). This removes a major annoyance > (I hope). Yes, I always wanted that fixed. You have hit a number of other TODO items. Nice. > * Refined \c[onnect]'ion failures: Non-interactive scripts will > terminate, even recursively. However, if the underlying session was > an interactive one, it does not terminate. The database connection > will be lost, however. Nice. > * Password prompts are automatic (both startup and \connect). Can > still use -P switch, but that might prove unnecessary. [ Cheers to > Roland R.! ] Nice > * Implemented \lo_import, \lo_export, \lo_unlink, \lo_list. (Still > needs some refinement, though.) Also nice. > * Can now use \copy with oids and delimiters. No binary, yet. Yes, quite nice. > > > TODO LIST > > * generalized backslash command handling (struct, no ..else if...) > * new printing routines How about a backslash command to print the current date/time. Good for performance debugging. > * rewrite mainloop parser, strip comments > * single line mode doesn't take slash commands > * make scripts bomb out (optionally) on query error > * remove Rollback warnings in lo_ ops > * \default(s?) command > * allow several \ cmds on a line (add '\' to strtokx delims?, windows?) > > > SIDE NOTES > > 1. Since the new animal is now probably going to be 7.0, let's provide a > psql that's worthy of that name, er, number. I hope I can lay a > framework with this, but there are still a few months I think, so ideas > are welcome. > > 1.a) On a related note, since the core developers have more important > issues to worry about, I wouldn't mind maintaining/accompanying/taking > care of/keeping an eye on/whatever psql until release (and possibly > thereafter). Good. It needs it. > > 2. What about including an snprintf() into the source tree similar what is > done with strdup()? (No, don't look at me, it totally escapes me how to > do that and I don't want to cheat and look at the GNU sources for > obvious reasons.) We can do that. I thought we already did. -- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610) 853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania19026
В списке pgsql-hackers по дате отправления: