> The right way to do this at the C level would be to use the same
> infrastructure as nextval() does to accept arguments like 'foo' and
> '"Foo"."Bar"'. There's no reason to restrict the two-argument form
> to the current search_path.
Is it possible to do that in SQL? eg. is there anything you can do to go:
select '"Foo"."Bar"'::regclassoid;
Or something?
I'm trying to avoid doing it in C as it seems like it would be a pita.
Chris
