This blog post is
12 years old! Most likely, its content is outdated.
Especially if it's technical.
I just learnt a better way to check if a PostgreSQL table exists. Before I did this to find out if table mytable is defined:
SELECT * FROM 'mytable' LIMIT 1;
But this had to be wrapped in exception catching application code because I was able to tell if the table existed if the select statement worked. That's the wrong and naive way. The correct way is to use pg_class and look at how many rows were returned:
SELECT relname FROM pg_class
WHERE relname = 'mytable';
Why have I missed this before? No explanation?
A disadvantage with using pg_class is that it's not ISO standard, meaning that it's specific to PostgreSQL only. The first pattern will work on all relational databases.
- Previous:
- Google blogs about their Maps
19 April 2005
- Next:
- Serious flaw in Bose headphones
23 April 2005
- Related:
- Select all relations in PostgreSQL
10 December 2015
- Chainable catches in a JavaScript promise
05 November 2015
- How do log ALL PostgresSQL SQL happening
20 July 2015
- Fastest database for Tornado
09 October 2013
- Careful with your assertRaises() and inheritance of exceptions
10 April 2013
- Postgres collation errors on CITEXT fields when upgrading to 9.1
21 May 2012
- Connecting with psycopg2 without a username and password
24 February 2011
- Optimization of getting random rows out of a PostgreSQL in Django
23 February 2011
- Fastest "boolean SQL queries" possible with Django
14 January 2011
- UPPER vs. ILIKE
19 April 2010
SELECT 1 FROM pg_catalog.pg_class WHERE relkind = 'r' AND relname = 'name' AND pg_catalog.pg_table_is_visible(oid) LIMIT 1