Re: tgname munged

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Le 04/08/2010 17:30, gnuoytr@rcn.com a écrit :
> Can anyone explain why the following query (used by AQT to display its tree):
>
> SELECT trig.tgname,
> tab.relname,
> case trig.tgenabled
> when '1' then 'yes'
> else 'no'
> end,
> trig.oid
> FROM pg_catalog.pg_trigger trig,
> pg_catalog.pg_class tab,
> pg_catalog.pg_namespace nam
> WHERE trig.tgrelid=tab.oid
> AND tab.relnamespace=nam.oid
> AND nam.nspname ='public' -- ?
> ORDER BY 1
>
> produces tgname like (from memory) RIFKConstraint...<number>
> while without the   ORDER BY  (and it doesn't matter how you identify the column) tgname displays correctly (well,
thesame as what you see if you SELECT * FROM pg_trigger). 
>

Hi,

Which version of PostgreSQL is it ?
I can't see any difference with PG 8.4.4.

Regards,

- --
Stéphane Schildknecht
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkxZjfsACgkQA+REPKWGI0HiMQCfWf54uFM3WMy3LsxQ+513J1il
ETsAoLD23uOijdlwOR7X4av+n9pmSi02
=eOIx
-----END PGP SIGNATURE-----