| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: tab completion for prepared transactions? |
| Date: | 2010-01-26 07:03:29 |
| Message-ID: | 1264489409.14033.4.camel@fsopti579.F-Secure.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On sön, 2010-01-24 at 21:56 +0200, Heikki Linnakangas wrote:
> >> "PREPARE TRANSACTION is not intended for use in applications or in
> >> interactive sessions. It's purpose is to allow an external transaction
> >> manager to perform atomic global transactions across multiple databases
> >> or other transactional resources. Unless you're writing a transaction
> >> manager, you probably shouldn't be using PREPARE TRANSACTION"
> >
> > I was thinking of adding something in the psql C source code to explain
> > why certain commands are not implemented for tab completion.
>
> Yeah, that's a good idea too.
Should we remove the completion of COMMIT|ROLLBACK -> PREPARED then?
That's what initially threw me off.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2010-01-26 07:07:35 | Re: [HACKERS] problem with CVS on pgfoundry |
| Previous Message | Pavel Stehule | 2010-01-26 06:59:35 | Re: Review: listagg aggregate |