By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,855 Members | 1,988 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,855 IT Pros & Developers. It's quick & easy.

updating records

P: n/a
Hi all.
I am using Visual FoxPro via ODBC to update records on a 7.3.4
PostgreSql server and it appears that it always uses delete/insert
instead of updating the current record. Can this be changed to update
the existing record instead?
--
Eugene Vital
Any technology indistinguishable from magic is insufficiently advanced.


---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html

Nov 12 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
On Fri, Oct 03, 2003 at 11:27:11 -0400,
Gene Vital <ge*******@karibe.com> wrote:
Hi all.
I am using Visual FoxPro via ODBC to update records on a 7.3.4
PostgreSql server and it appears that it always uses delete/insert
instead of updating the current record. Can this be changed to update
the existing record instead?


Depneding on why you want to do this, it might not help. Postgres
uses MVCC and updates are effectively inserts and deletes.

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to ma*******@postgresql.org so that your
message can get through to the mailing list cleanly

Nov 12 '05 #2

P: n/a
On Fri, 3 Oct 2003, Gene Vital wrote:
Hi all.
I am using Visual FoxPro via ODBC to update records on a 7.3.4
PostgreSql server and it appears that it always uses delete/insert
instead of updating the current record. Can this be changed to update
the existing record instead?


I'm not sure if you are saying that Foxpro is doing a delete / insert, or
that postgresql is doing one.

Every update in postgresql is, in fact, a delete / insert, with the delete
delayed until no more transactions are looking at that version of the row
and vacuum has been run.

So, if Visual Foxpro is in fact issuing a delete insert, it's likely no
great performance hit for postgresql, which would wind up doing the same
basic thing anyway.
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

Nov 12 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.