On Fri, May 3, 2024 at 11:08 PM Adrian Klaver <adrian.kla...@aklaver.com> wrote:
> On 5/3/24 14:06, Magnus Hagander wrote: > > > > > > On Fri, May 3, 2024 at 10:58 PM David Gauthier <dfgpostg...@gmail.com > > <mailto:dfgpostg...@gmail.com>> wrote: > > > > psql (15.3, server 14.5) on linux > > > > Someone else's DB which I've been asked to look at. > > > > \dt gives many tables, here are just 3... > > > > public | some_idIds | table > > | cron_user > > public | WarningIds | table > > | cron_user > > public | cpf_inv_driverIds | table > > | cron_user > > > > but \d public.some_idIds gives.. > > > > Did not find any relation named "public.some_idIds". > > > > > > > > Looks like you might need a \d "some_idIds" (include the quotes) since > > it has an uppercase characters? > > This: > > "Did not find any relation named "public.some_idIds"." > > to me indicates it did look for the properly cased name. > That is arguably a really bad error message, because it puts those quotes there whether needed or not. if you put the quotes in there, you get: Did not find any relation named "public."some_idIds"". -- Magnus Hagander Me: https://www.hagander.net/ <http://www.hagander.net/> Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>