| From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
|---|---|
| To: | Anand Raman <araman(at)india-today(dot)com> |
| Cc: | postgresql <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: plpgsql always returning null.. |
| Date: | 2001-02-02 19:14:48 |
| Message-ID: | Pine.BSF.4.21.0102021101070.22065-100000@megazone23.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Okay, that's basically what I tried on my 7.1b3 system which
worked, both with quantity as int2 and int4. It'll probably
work there. In the mean time, what kinds of queries are you
using this in, maybe a subselect would work as a temporary fix.
On Sat, 3 Feb 2001, Anand Raman wrote:
> hi
>
> we have 2 databases on the test environment both running 702 ..
> The answer for consitent in both the machines.. Both the databases when
> queries returned null..
>
> The table inventory is a very simple 2 column table containing
> exhibit_distribution_id and quantity as the column..
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nic Ferrier | 2001-02-02 19:32:38 | Postgres SQL 7.1 a thank you and a possible bug |
| Previous Message | Alex Pilosov | 2001-02-02 19:05:00 | PostgreSQL profiling? |