| From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | "V S P" <toreason(at)fastmail(dot)fm> |
| Cc: | "Gerhard Heift" <ml-postgresql-20081012-3518(at)gheift(dot)de>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: [Q]updating multiple rows with Different values |
| Date: | 2008-11-23 19:08:30 |
| Message-ID: | dcc563d10811231108i3ff036acmf401342edbbc6f19@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Sun, Nov 23, 2008 at 8:43 AM, V S P <toreason(at)fastmail(dot)fm> wrote:
> Thank you very much
> this is exactly what I am looking for
>
> As well as the example provided
> ' case when id=1 then 10 '
>
> - it will work as well.
>
>
> Now just one more question:
> I will not have a lot of values to update (less than a 1000
> at a time) -- but the values for col1 will be text that is
> up to 64K. So I will not be able to construct SQL strings
> and just send them (because it will probably exceed the character
> limits for the SQL statements).
There are no character limits for sql statements in pgsql
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2008-11-23 20:58:32 | Re: Postgres mail list traffic over time |
| Previous Message | Scott Marlowe | 2008-11-23 18:23:55 | Re: Using Postgres to store high volume streams of sensor readings |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Devrim GÜNDÜZ | 2008-11-23 19:35:34 | Logging auto_explain outputs to another log file |
| Previous Message | Tom Lane | 2008-11-23 19:05:12 | Re: Visibility map, partial vacuums |