You can throw your computer out of a 10-story window - but just because you can do it doesn't mean it's a good idea. It's just wrong.
In your particular case it depends on whichever library/ interface/ application you're using to communicate with PG (e.g. PGSQL manager, the dump and restore tools, PHP's library, libpq.dll etc) - as they will all have to realise that there is a dot in the table/column name, and will have to quote it, or PG will complain. And you'll have to remember to quote it too when manually writing queries - it's just extra work that's plain unnecessary. Plus if/when you encounter problems in the future, the first thing that people are going to see is the dot in the table/column names and question if that's what is causing the problem, as in problem-solving you always look for the obvious first. Why are you so insistent you want to use a dot? Can't you use underscores instead? Andy -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of sandhya Sent: Monday, 27 March, 2006 12:27 PM To: Jim C. Nasby Cc: Michael Fuhr; Postgres Subject: Re: [ADMIN] reg:create database oh.....ok Now, just because you can do this doesn't mean it's a very good idea... Why? ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
