--- Joshua <[EMAIL PROTECTED]> wrote:
> Hello,
>
> Thank you all for your assistance. I did end up finding NULL in the
> 'onorder' column which should have been zero's this was in a test
> table that happened to have some NULL in it for one reason or another
> but I should not find this i
Hello,
Thank you all for your assistance. I did end up finding NULL in the
'onorder' column which should have been zero's this was in a test
table that happened to have some NULL in it for one reason or another
but I should not find this in the production version of the table.
I also app
Joshua wrote:
Hello,
I am new to this list and have been working with PostgreSQL since January.
Here is my problem, I hope someone here has some experience or can point
me in the right direction. I am writing the following query for a C#
program I am writing:
SELECT 'PV.LINEITEM:' || partnu
Hello,
I am new to this list and have been working with PostgreSQL since January.
Here is my problem, I hope someone here has some experience or can point
me in the right direction. I am writing the following query for a C#
program I am writing:
SELECT 'PV.LINEITEM:' || partnum || ',' || rou
"Jason Grout" <[EMAIL PROTECTED]> writes:
> 2. Is there a big difference in speed between using an array versus
> using a SELECT in a WHERE condition? In other words, which is generally
> going to be faster:
>
> SELECT * from table where field IN (some function returning a SETOF);
>
> or
>
> SEL
I have a performance related question (and a few code snippets to
contribute to the list archives).
I am trying to write a function that recursively walks a hierarchal
structure to find all ancestors or descendants of a particular item or
list of items. My relationships are set up with the table
Thank you guys!
I'm currently migrating an Oracle database to postgres and have
created tables using the scripts that were readily available. Glad I
can now improve this old system.
On 29/05/07, Gregory Stark <[EMAIL PROTECTED]> wrote:
"Andrew Kroeger" <[EMAIL PROTECTED]> writes:
> Raj A wrote
"Andrew Kroeger" <[EMAIL PROTECTED]> writes:
> Raj A wrote:
>> I have a table
>>
>> CREATE TABLE survey_load
>> (
>> meter_id character(5) NOT NULL,
>> number_of_bays integer NOT NULL,
>> bay_1_use integer,
>> bay_2_use integer,
>> bay_3_use integer,
>> bay_4_use integer,
>> bay_5_use inte
Raj A wrote:
> I have a table
>
> CREATE TABLE survey_load
> (
> meter_id character(5) NOT NULL,
> number_of_bays integer NOT NULL,
> bay_1_use integer,
> bay_2_use integer,
> bay_3_use integer,
> bay_4_use integer,
> bay_5_use integer,
> date date NOT NULL,
> inspection_id integer NOT NU
