On 05/10/11 14:09, MarkW wrote:
John - SET CLIENT is the beginning of a larger SQL statement. The
error says the SQL statement failed, "...sql begins:"
and then later down the error dump indicates a connectivity issue -
which you later identified as the probable cause.
So it is not saying th
John - SET CLIENT is the beginning of a larger SQL statement. The
error says the SQL statement failed, "...sql begins:"
and then later down the error dump indicates a connectivity issue -
which you later identified as the probable cause.
So it is not saying the encoding is the failure, just tha
Thanks for the reply, Barend. I'm not sure what you mean though. Since
we're using the gui, I've already given the path because that's how we
chose a shape file to upload. I know of no other way to specify the
path for the shape file source.
Later today we managed to finally get the file to u
He solution might be simply that somewhere further in the SQL it tries to
find your shape-file and fails. What is the path you provided for the
shape-file...?
Barend
On 05-10-11 04:05, "John Brisbin" wrote:
>G'Day all,
>
>We're in the early stages of familiarising ourselves with the basic
>ma
G'Day all,
We're in the early stages of familiarising ourselves with the basic
management tools and procedures, so apologies in advance if this is well
documented (somewhere?).
We're running in a Debian (lenny) environment, using pgAdmin3 (1.14.0),
and have manually installed the shp2pgsql-g
