Thread: begin update ... syntax error
I was trying to speed up a simple update query fri=# begin fri-# update tabA set nobegin=tmp.nobegin, noend=tmp.noend fri-# from tmp fri-# where tabA.acc=tmp.acc; ERROR: syntax error at or near "update" at character 7 The same query can be run with no problem if not starting with BEGIN. Does mean that BEGIN cannot preceed UPDATE? Or I am making some obvious miskate? Kemin ********************************************************************** Proprietary or confidential information belonging to Ferring Holding SA or to one of its affiliated companies may be containedin the message. If you are not the addressee indicated in this message (or responsible for the delivery of the messageto such person), please do not copy or deliver this message to anyone. In such case, please destroy this message andnotify the sender by reply e-mail. Please advise the sender immediately if you or your employer do not consent to e-mailfor messages of this kind. Opinions, conclusions and other information in this message represent the opinion of thesender and do not necessarily represent or reflect the views and opinions of Ferring. **********************************************************************
try a semicolon after the begin ?
begin;
<code>
commit;
Greg Williamson
DBA
GlobeXplorer LLC
-----Original Message-----
From: Kemin Zhou [mailto:kemin.zhou@ferring.com]
Sent: Sat 4/10/2004 2:32 PM
To: pgsql-sql@postgresql.org
Cc:
Subject: [SQL] begin update ... syntax error
I was trying to speed up a simple update query
fri=# begin
fri-# update tabA set nobegin=tmp.nobegin, noend=tmp.noend
fri-# from tmp
fri-# where tabA.acc=tmp.acc;
ERROR: syntax error at or near "update" at character 7
The same query can be run with no problem if not starting with BEGIN.
Does mean that BEGIN cannot preceed UPDATE?
Or I am making some obvious miskate?
Kemin
**********************************************************************
Proprietary or confidential information belonging to Ferring Holding SA or to one of its affiliated companies may be
containedin the message. If you are not the addressee indicated in this message (or responsible for the delivery of the
messageto such person), please do not copy or deliver this message to anyone. In such case, please destroy this message
andnotify the sender by reply e-mail. Please advise the sender immediately if you or your employer do not consent to
e-mailfor messages of this kind. Opinions, conclusions and other information in this message represent the opinion of
thesender and do not necessarily represent or reflect the views and opinions of Ferring.
**********************************************************************
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
On Saturday 10 April 2004 02:32 pm, Kemin Zhou wrote: begin; Note the semi-colon Then the update query; commit; or rollback; > I was trying to speed up a simple update query > > fri=# begin > fri-# update tabA set nobegin=tmp.nobegin, noend=tmp.noend > fri-# from tmp > fri-# where tabA.acc=tmp.acc; > ERROR: syntax error at or near "update" at character 7 > > The same query can be run with no problem if not starting with BEGIN. > > Does mean that BEGIN cannot preceed UPDATE? > > Or I am making some obvious miskate? > > Kemin > > > > > ********************************************************************** > Proprietary or confidential information belonging to Ferring Holding SA or > to one of its affiliated companies may be contained in the message. If you > are not the addressee indicated in this message (or responsible for the > delivery of the message to such person), please do not copy or deliver this > message to anyone. In such case, please destroy this message and notify the > sender by reply e-mail. Please advise the sender immediately if you or your > employer do not consent to e-mail for messages of this kind. Opinions, > conclusions and other information in this message represent the opinion of > the sender and do not necessarily represent or reflect the views and > opinions of Ferring. > ********************************************************************** > > > ---------------------------(end of broadcast)--------------------------- > TIP 5: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faqs/FAQ.html -- Adrian Klaver aklaver@comcast.net
Kemin, Instead of just begin, have "begin;" and put "commit;" at the end of the SQL statement. Go here for more information: http://developer.postgresql.org/docs/postgres/tutorial-transactions.html Regards, Yasir On Sat, 10 Apr 2004, Kemin Zhou wrote: > Date: Sat, 10 Apr 2004 14:32:46 -0700 > From: Kemin Zhou <kemin.zhou@ferring.com> > To: pgsql-sql@postgresql.org > Subject: [SQL] begin update ... syntax error > > I was trying to speed up a simple update query > > fri=# begin > fri-# update tabA set nobegin=tmp.nobegin, noend=tmp.noend > fri-# from tmp > fri-# where tabA.acc=tmp.acc; > ERROR: syntax error at or near "update" at character 7 > > The same query can be run with no problem if not starting with BEGIN. > > Does mean that BEGIN cannot preceed UPDATE? > > Or I am making some obvious miskate? > > Kemin > > > > > ********************************************************************** > Proprietary or confidential information belonging to Ferring Holding SA or to one of its affiliated companies may be containedin the message. If you are not the addressee indicated in this message (or responsible for the delivery of the messageto such person), please do not copy or deliver this message to anyone. In such case, please destroy this message andnotify the sender by reply e-mail. Please advise the sender immediately if you or your employer do not consent to e-mailfor messages of this kind. Opinions, conclusions and other information in this message represent the opinion of thesender and do not necessarily represent or reflect the views and opinions of Ferring. > ********************************************************************** > > > ---------------------------(end of broadcast)--------------------------- > TIP 5: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faqs/FAQ.html >