Thread: Option 'xactisolevel' is not recognized (???)

Option 'xactisolevel' is not recognized (???)

From
Dave Stewart
Date:
Hi and Happy New Year!

I posted this query to the WebObjects mailing list first, thinking
someone in there would be familiar with what's going on. Unfortunately,
no one has responded yet (maybe I'm just impatient, I posted it on
Tuesday but we did have a holiday since then ...), therefore I thought
I'd try on this list and see if anyone could give me a clue. I'd even
consider buying one for the right price ... ;-)


Help!

I've installed PostgreSQL 7.3 on my system and I'm trying to connect to
it with EOModeler, but I'm getting some weird error that's meaningless
to me (besides the obvious part that it isn't working). I can start the
DB with :

/usr/local/bin/postmaster -D /usr/local/pgsql/data -i

The -i option is supposed to make it listen for TCP/IP connections (I
think it's doing that). OK, fine; my terminal gets tied up with a few
lines that start with LOG:, the last one tells me the database system
is ready (I want to make this happen as a separate process instead of
tying up my terminal, but that's only after the crazy thing works!).

Now onto EOModeler ... I create a New Model, using JDBC connectivity
(yes, I also installed that driver and tested it with a simple java
class and confirmed it's working fine), enter in the particulars
("postgres" as the name, the correct password,
"jdbc:postgresql://127.0.0.1/DatabaseName", and the name of the driver
itself which is org.postgresql.Driver), hit OK and ...

Both EOModeler AND Postgresql claim "Option xactisolevel is not
recognized". No duh ... what in the flaming pits of hades is that? Is
it supposed to be recognized by me? (It isn't.) Anyone have a clue as
to what to do about this? Can I have one?
;-)

TIA


Dave Stewart
Aqua-flo (Goleta)
dstewart@aquaflo.com


Re: Option 'xactisolevel' is not recognized (???)

From
Tom Lane
Date:
Dave Stewart <dstewart@aquaflo.com> writes:
> Both EOModeler AND Postgresql claim "Option xactisolevel is not
> recognized". No duh ... what in the flaming pits of hades is that?

Hm.  XactIsoLevel is the internal variable that's set by the
SET TRANSACTION ISOLATION LEVEL command.  I think it used to be
possible to set it using its internal name (goes off and experiments
... yes, that seems to work in releases before 7.3).

What you've got there is an app or client library that uses the
unportable, undocumented, and now unsupported syntax "set XactIsoLevel
to something" instead of the SQL-spec syntax "set transaction isolation
level something".  Time to fix it...

            regards, tom lane