From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | sunpeng <bluevaley(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: why can't see the updated value after SPI_execute("update ....", false, 1); |
Date: | 2010-09-12 15:11:27 |
Message-ID: | 8700.1284304287@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
sunpeng <bluevaley(at)gmail(dot)com> writes:
> First I use SPI_execute("update ....
> bool succ;
> SPI_connect();
> int ret = SPI_execute("update ....where uid = 1", false, 1);//later will
> add error processing
> if (ret == SPI_OK_UPDATE && SPI_processed == 1) {
> succ = true;
> }
> SPI_finish();
> Then I use SPI_execute("select .....where uid = 1", ....
> SPI_connect();
> int ret = SPI_execute("select .....where uid = 1", true, 1);//later will
> add error processing
> if (ret == SPI_OK_SELECT && SPI_processed == 1) {
> HeapTuple tuple;
> tuple = SPI_tuptable->vals[0];
> ...
> datum = heap_getattr(tuple,attrno,SPI_tuptable->tupdesc,&isnull);
> ....
> }
> the datum doesn't change, why ?
You're missing a CommandCounterIncrement() call between the two actions.
If you hadn't passed read_only = true to the second SPI_execute, it
would have done one for you.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Casey Jones | 2010-09-12 18:44:22 | Re: Huge amount of memory errors with libpq |
Previous Message | adi hirschtein | 2010-09-12 14:02:35 | Re: Monitoring Object access |