OK, I have applied the following patch. Interestingly, the SGML code
marked this block as outdated, but didn't remove it for some reason.
> On Tue, 19 Jun 2001, Michael Meskes wrote:
>
> > On Mon, Jun 18, 2001 at 03:59:56PM -0400, Thalis A. Kalfigopoulos wrote:
> > > EXEC SQL DECLARE my_cursor
But Ill have to add double slashes and even more importent I will have to
unescape every binary data going out of the server, which mean in one of my
aplication all the Images.
Wont this action be much more heavey then the way I used untill now with
MySQL (blob) ?
addslash on insert and ordinary
Wieger,
The server does not have a concept of error codes currently (it is on
the TODO list). Therefore the JDBC driver has no error code to report
since it doesn't get one from the backend. When the server supports
error codes the JDBC driver will as well.
thanks,
--Barry
Wieger Uffink w
hehe thank you for your elaborate though very clear reply :)
thanks really
Wieger
Peter Eisentraut wrote:
>
> Wieger Uffink writes:
>
> > I would like to know if postgreSQL propegates any errorcodes at all,
>
> No.
>
> --
> Peter Eisentraut [EMAIL PROTECTED] http://funkturm.homeip.net/
Wieger Uffink writes:
> I would like to know if postgreSQL propegates any errorcodes at all,
No.
--
Peter Eisentraut [EMAIL PROTECTED] http://funkturm.homeip.net/~peter
---(end of broadcast)---
TIP 2: you can get off all lists at once with
I never transfered the file anywhere, it was all done under linux. The
bottom line is pg_dump follwed by a psql import failed exactly like what was
described in this thread. When I did a dump with "proper inserts" it worked
fine. As I said, I don't know what was causing the problem, just th
Stephan Bergmann writes:
> Compiling the following returns me - executing the result.cgi - the
> error:
> ./result.cgi: can't load library 'libpq.so.2'
>
> gcc -lpq -I/usr/include/mysql -I/usr/local/pgsql/include
> -L/usr/local/pgsql/lib -L/usr/lib/mysql program.c
> -o result.cgi -Wall -DUNIX -lm
I think we may be using too many words in this discussion.
Perhaps there is a message in this thread that I have not seen.
Miroslav, have you tested for carriage returns in your data, and if so, what
did you find?
If that is the problem, the carriage returns are easily edited out, and
speculation
Peter Eisentraut, Oliver Elphick, len morgan,
Thank you.
\N did the trick with pgaccess.
I have just cleaned up over 15000 database records in BBEdit (the data
was on a Mac server) and now ama trying to remember what I did last time
to get my accents right... When will I ever learn to take note
I very much doubt that the data wouldn't "dump
right". The dump will include any data that is in the table, including CRs
if they are in there.
In the current case, the CRs were not already in
there, because PostgreSQL would not have recognized that field as null ("\N") if
they were.
Any tr
Hi,
Im accessesing a postgreSQL db through JDBC, and I would like take make
use of the method, getErrorCode in the SQLException class as in
java.sql.
So far I have been able to retreive exception messages but not the error
codes in case of an SQL exception.
I would like to know if postgreSQL pr
Hi!
Compiling the following returns me - executing the result.cgi - the
error:
./result.cgi: can't load library 'libpq.so.2'
gcc -lpq -I/usr/include/mysql -I/usr/local/pgsql/include
-L/usr/local/pgsql/lib -L/usr/lib/mysql program.c
-o result.cgi -Wall -DUNIX -lmysqlclient -lm
All files are at i
Denis Gasparin <[EMAIL PROTECTED]> writes:
> On table a (INTEGER datatype) the search is done using the index.
> Instead on table b (BIGINT datatype) the search is always done using the
> seq scan.
Try
select * from b where col1 = 123::int8;
The query planner is not presently very smart
Denis Gasparin <[EMAIL PROTECTED]> writes:
> Is it possible that the query planner thinks that is best a sequential scan
> when an index on the table is present?
Possibly. It all depends on the statistics. You have not shown us the
EXPLAIN results obtained after doing VACUUM ANALYZE...
I search in the archive and i have found that i have to specify the type of
the column at the end of the query... so the new query is :
explain select * from b where col1=123::int8;
In this way, the explain output is correct.
The e-mail i found in the archive says that the problem will be solv
"Ben-Nes Michael" <[EMAIL PROTECTED]> writes:
> On the theoretical issue, can I use TEXT field to store binary ?
TEXT will not handle null (zero) bytes. If you are using a multibyte
character set, it will likely also do the wrong thing with byte
sequences that are illegal or incomplete multibyte
"Steven D. Arnold" <[EMAIL PROTECTED]> writes:
> It is my understanding that 16 parameters are allowed in a stored
> procedure. If this is correct (please advise if not):
See INDEX_MAX_KEYS/FUNC_MAX_ARGS in src/include/config.h (or config.h.in
if you haven't yet run configure). There are no pla
Oliver Elphick writes:
> Tony Grant wrote:
> >Hello,
> >
> >I am importing via pgaccess a text file from another non-postgres
> >database and the NULL DATE values are written like 00/00/00.
> >
> >What I have tried is replacing 00/00/00 by 9/9/1999 and setting the
> >style to europe
Miroslav Koncar <[EMAIL PROTECTED]> writes:
> The only thing I can think of is the PostgreSQL versions. My collegue is
> using 7.0.3, and I use 7.1.2. Comments?
That wouldn't produce a carriage-return problem.
It's possible that we're barking up the wrong tree, and that the issue
is not carriage
Hi to all!
Is it possible to define indexes on a column with BIGINT datatype? See
this example:
testdb=# create table a (col1 integer not null primary key);
NOTICE: CREATE TABLE/PRIMARY KEY will create implicit index 'a_pkey' for
table 'a'
CREATE
testdb=# create table b (col1 bigint no
Tony Grant wrote:
>Hello,
>
>I am importing via pgaccess a text file from another non-postgres
>database and the NULL DATE values are written like 00/00/00.
>
>What I have tried is replacing 00/00/00 by 9/9/1999 and setting the
>style to european and I am getting 'can't parse /9/1999
> I am importing via pgaccess a text file from another non-postgres
> database and the NULL DATE values are written like 00/00/00.
>
> What I have tried is replacing 00/00/00 by 9/9/1999 and setting the
> style to european and I am getting 'can't parse /9/1999' errors.
Try replacing 00/00/00 with
Hello,
I am importing via pgaccess a text file from another non-postgres
database and the NULL DATE values are written like 00/00/00.
What I have tried is replacing 00/00/00 by 9/9/1999 and setting the
style to european and I am getting 'can't parse /9/1999' errors.
How do I go about importing
Now i have tried creating the table and the inserting...
The results are the same...
Is it possible that the query planner thinks that is best a sequential scan
when an index on the table is present?
I'm using postgresql 7.1.3 on a redhat 7.1.
Thanks for the help,
Denis
P.S.: I'm sorry having m
I have done VACUUM ANALYZE too but the statistics continue preferring
sequential scan...
Now i'll try to use a different approach:
- i'll create the empty table with a CREATE TABLE (and a primary key on col1)
- then i'll populate it using then INSERT..SELECT statement
- Last i'll check what the
Jan Wieck wrote:
>Oliver Elphick wrote:
>
>>Jan Wieck wrote:
>> >But the question itself tells that you're about to implement
>> >a major design error in your application. Holding database
>> >locks during user interaction IS A BAD THING. Never, never
>> >ever do it
On 23 Aug 2001 13:05:51 -0400, tomasz konefal wrote:
>i'm having trouble getting ultradev to make a connection with a postgresql
> database on my server. does anyone have any experience with this? i have a
> test .jsp script which can pull data out of a test db, but ultradev doesn't
> want
27 matches
Mail list logo
