ou might want to rewrite your select statements like:
> SELECT
> rgt, universeid, treeid
> FROM
> list_objects
> WHERE
> objid_auto=t_newparent
> INTO
> newparentrgt, newparentuid, newparenttid;
>
> I think it's more readable and probably a little
I'm not sure that keying off lft is safe in a multi-user environment. I
opted to create and use an objid on the tree definition table, since its
identity is static. I also found that when trees get active, allowing for
tree IDs increased operation speed quite a bit (i actually push this to
two le
umps on the dev box are ok. the distro install
must set the CFLAGS based on hardware (the laptop is a Compaq PIII/700,
and the staging box is a P4/1.7G on an intel chipset board). Anyway,
really happy this worked -- thanks again. Let me know if there's anything
I can do.
> "Martin
Tom;
Not sure how to tell. I didn't explicitly specify anything like this
during the ./configure step of install. Poking around in the souce
directory, I pulled this out of config.cache ...
configure:1243: checking whether the C compiler (gcc -O9 -funroll-loops
-ffast-math -malign-double -mcpu
;m running postgres 7.2.2 on slackware 8.1 (kernel 2.4.18).
Is there a workaround on this?
Tks and kind regards,
Martin Crundall
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
Howdy;
I'm writing a "script" to pre-populate a database system that's
already in place. The database system is in an advanced stage of
development and includes many stored procedures and TRIGGERS.
The "script" is really a stored procedure designed to be executed by
the system's admin guy
hing in an
update somewhere.
Anyway, thanks again.
> "Martin Crundall" <[EMAIL PROTECTED]> writes:
>>Some of the data tables have "AFTER INSERT" TRIGGERs on them that,
>> in
>> turn, insert some subordinate items into parallel data tables and the
>> c
Howdy;
I'm writing a "script" to pre-populate a database system that's
already in place. The database system is in an advanced stage of
development and includes many stored procedures and TRIGGERS.
The "script" is really a stored procedure designed to be executed by
the system's admin guy
