Re: column size too large, is this a bug? - Mailing list pgsql-performance

From Qing Zhao
Subject Re: column size too large, is this a bug?
Date
Msg-id AFEEE44A-7EB1-11D8-8B9C-000A95AB8896@quotefx.net
Whole thread Raw
In response to Re: column size too large, is this a bug?  (Stephan Szabo <sszabo@megazone.bigpanda.com>)
List pgsql-performance
It is 7.3.4 on MAC OS X (darwin). The patch we applied is
hier-Pg7.3-0.5, which<fontfamily><param>Arial</param><x-tad-bigger>
allows

to perform hierarchical queries on PgSQL using Oracle's syntax.


Thanks!


Qing

</x-tad-bigger></fontfamily>

On Mar 25, 2004, at 2:57 PM, Stephan Szabo wrote:


<excerpt>On Thu, 25 Mar 2004, Qing Zhao wrote:


<excerpt>   select

   _level_ as l,

    nextval('seq_pk_bom_detail') as bom_detail,

    prior nextval('seq_pk_bom_detail') as parent_subassembly,

   parent_part_number,

    customer_part_number,

   /* mfr_name,

    mfr_part,

    description,*/

    commodity,

    needs_date,

    target_price,

    comments,

    case qty_per

       when null then 0.00001

       when 0 then 0.00001

       else qty_per

    end,

    qty_multiplier1,

    qty_multiplier2,

    qty_multiplier3,

    qty_multiplier4,

    qty_multiplier5

  from bom_detail_work_clean

  where (0=0)

   and bom_header=20252

   and file_number = 1

   start with customer_part_number = 'Top Assembly 1'

   connect by parent_part_number = prior customer_part_number;

</excerpt>

What version are you running, and did you apply any patches (for
example

one to support the start with/connect by syntax used above?)



</excerpt>
It is 7.3.4 on MAC OS X (darwin). The patch we applied is
hier-Pg7.3-0.5, which allows
to perform hierarchical queries on PgSQL using Oracle's syntax.

Thanks!

Qing

On Mar 25, 2004, at 2:57 PM, Stephan Szabo wrote:

> On Thu, 25 Mar 2004, Qing Zhao wrote:
>
>>    select
>>    _level_ as l,
>>     nextval('seq_pk_bom_detail') as bom_detail,
>>     prior nextval('seq_pk_bom_detail') as parent_subassembly,
>>    parent_part_number,
>>     customer_part_number,
>>    /* mfr_name,
>>     mfr_part,
>>     description,*/
>>     commodity,
>>     needs_date,
>>     target_price,
>>     comments,
>>     case qty_per
>>        when null then 0.00001
>>        when 0 then 0.00001
>>        else qty_per
>>     end,
>>     qty_multiplier1,
>>     qty_multiplier2,
>>     qty_multiplier3,
>>     qty_multiplier4,
>>     qty_multiplier5
>>   from bom_detail_work_clean
>>   where (0=0)
>>    and bom_header=20252
>>    and file_number = 1
>>    start with customer_part_number = 'Top Assembly 1'
>>    connect by parent_part_number = prior customer_part_number;
>
> What version are you running, and did you apply any patches (for
> example
> one to support the start with/connect by syntax used above?)
>
>

pgsql-performance by date:

Previous
From: markw@osdl.org
Date:
Subject: Re: [HACKERS] fsync method checking
Next
From: Tom Lane
Date:
Subject: Re: column size too large, is this a bug?