Has anyone out there worked extensively setting up proxies? I am
experimenting with connecting to a postgresql database on a debian
machine from an xp box by way of an intermediate debian machine running
the proxy. When i try to execute an insert statement (via $dbh->do()) I
reach a point at which the proxy server child process terminates with a
parse error in the ProxyServer module. (line 344 is referenced, the
point at which the module seems to be determining the characteristics of
the columns being populated.)
I can generally get it to accept two scalars in the values section of
the statement, but when I add the third the error appears. This doesn't
seem to have anything to do with the table column type, I have
experimented with varchar, char, and integer, and the error occurs no
matter how I shuffle. (The statement will execute if I replace that
triggering scalar with a quoted sting.) The only example that doesn't
correspond to this pattern that I have to offer resulted from an
experiment I conducted this morning, when I attempted to concantenate
the entire ca. 100 byte record and stick it into one big varchar. That
triggered the parse error on its own, which got me to thinking that I
may be running afoul of internal enviroment limitations.
Any perspectives would be appreciated.
john cuson
([EMAIL PROTECTED], [EMAIL PROTECTED])
The world is full of obvious things which nobody by any chance ever
observes.
Sir Arthur Conan Doyle
