Re: minor issue in createdb 8.0.0beta4 - Mailing list pgsql-bugs

From Magnus Hagander
Subject Re: minor issue in createdb 8.0.0beta4
Date
Msg-id 6BCB9D8A16AC4241919521715F4D8BCE476065@algol.sollentuna.se
Whole thread Raw
In response to minor issue in createdb 8.0.0beta4  (Silvio Scarpati <silvio.scarpati@customsolutions.it>)
Responses Re: minor issue in createdb 8.0.0beta4
List pgsql-bugs
> Hi !
>=20
> I discovered this particular feature in "createdb" tool=20
> 8.0.0beta4 running on Win32 Platform:


> c:\windows> createdb testdb;
> CREATE DATABASE

<snip>

> testdb;=3D# \l
>         List of databases
>    Name    |  Owner   | Encoding
> -----------+----------+-----------
>  template0 | postgres | SQL_ASCII
>  template1 | postgres | SQL_ASCII
>  testdb;   | silvio   | SQL_ASCII
> (4 rows)
>=20
> testdb;=3D#
>=20
> -------------------- Cut And Paste ---------------------------
>=20
> As you can see, createddb doesn't skip the semicolon after=20
> the database's name, so you have a db name ending with=20
> semicolon. This is not a problem really, but this happens=20
> only in this version/platform.

I don't think this is a postgresql issue, really. It's a shell issue.

sh/bash or whatever you're running on a unix platform has ; as a command
separator. The win32 command prompt does not. (For example, run "echo
foo; echo bar" and notice the differences between bash and cmd). If you
run the command under a bash interpreter (or other shell that uses
semicolon as command separator) on win32, you will se the unix like
behaviour.

Not sure if we want to add a workaround for that? It'd be needed for
every single command, so I personally don't think it's a good idea.

//Magnus

pgsql-bugs by date:

Previous
From: Silvio Scarpati
Date:
Subject: minor issue in createdb 8.0.0beta4
Next
From: Silvio Scarpati
Date:
Subject: Re: minor issue in createdb 8.0.0beta4