Обсуждение: Connecting settings in PsqlODBC

Hello,

I use PostgreSQL ODBC driver. This is 6.30.0246 version of
that product.

One of the advanced options of the driver (in section 'Connection') is
field
called as 'Connecting settings'. It gives the ability to run SQL
commands
at the momment of connecting. They say, that if someone wants to run a
few commands, they should be separated by a semi-colon (;). My problem
is that it doesn't work on my computer! Does anyone have any suggestions

where the problem is?

I have no problem with running one command. When I put a few of
them, only the first one is run. I use ODBC on Pentium133 to connect
resources
of PostgreSQL database with Access97.

Thanks in advance

Wojtek Pietron

wojtek wrote:
>
> Hello,
>
> I use PostgreSQL ODBC driver. This is 6.30.0246 version of
> that product.
>
> One of the advanced options of the driver (in section 'Connection') is
> field
> called as 'Connecting settings'. It gives the ability to run SQL
> commands
> at the momment of connecting. They say, that if someone wants to run a
> few commands, they should be separated by a semi-colon (;). My problem
> is that it doesn't work on my computer! Does anyone have any suggestions
>
> where the problem is?
>

I was able to run multiple commands.  Of course, only the first one
actually "responds" with anything, but the other commands were indeed
run.

BTW, what commands were you running?

Byron

wojtek wrote:
>
> Hello,
>
> I use PostgreSQL ODBC driver. This is 6.30.0246 version of
> that product.
>
> One of the advanced options of the driver (in section 'Connection') is
> field
> called as 'Connecting settings'. It gives the ability to run SQL
> commands
> at the momment of connecting. They say, that if someone wants to run a
> few commands, they should be separated by a semi-colon (;). My problem
> is that it doesn't work on my computer! Does anyone have any suggestions
>
> where the problem is?

Sorry, you were right.  Only the first command is getting run *after*
the first connect.  The reason is that the semicolans in the connect
settings is interfering with the semicolans used to separate the
SQLDriverConnect string.

I will fix it in the next release.

Byron