Hello Bruce!
> Yes, we inherited these arrays from Berkeley and haven't had any need to
> remove them. Are you trying to do things that the other interfaces like
> ODBC and JDBC don't handle?
About the groups: I just want to write a function that will return the users
names belonged by a given group. I understand I can load the arrays in
memory, then sequentially compare the members from pg_shadow, but doing it
goes against the database priciple after all.
About the procs: the Borland's dbExpress specification demands a
input/output list of parameters for stored procedures, and I'm going to use
functions as stored procedures. But I need to make a types list to be able
list what are those params.
> The group array is a hack but the pg_proc array would be hard to replace
> becauseit acts as part of the unique key used for cache lookups.
This design itself bothers me.
We have no other option left ? Like arrays being referenced in relations ?
That's far from perfect, but at least would solve those issues and others
which might appear in other catalogs...
Best Regards,
Steve Howe
