Skip site navigation (1) Skip section navigation (2)

Re: Character invalid saving memo with UpdateSQL

From: Richard Combs <rncombs(at)covad(dot)net>
To: Cristian Custodio <cristian_custodio(at)terra(dot)com(dot)br>
Cc: pgsql-odbc(at)postgresql(dot)org
Subject: Re: Character invalid saving memo with UpdateSQL
Date: 2003-11-28 07:45:27
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-odbc
I just did a quick test using the following setup

postgreSQL 7.4 running on Linux (SuSE 8.2)
ODBC client on W2K - SP4
MDAC 2.8
Borland D7
BDE 5.01
    LANGDRIVER set to (blank - default setting none chosen)

This is the test database structure

bigtest=# \encoding

bigtest=# \d table1
            Table "public.table1"
 Column |          Type           | Modifiers
 c1     | character(40)           |
 v2     | character varying(4000) |

Sample Delphi project

  TForm1 = class(TForm)
     Table1: TTable;
     UpdateSQL1: TUpdateSQL;
     Query1: TQuery;
     Button1: TButton;
     DataSource1: TDataSource;
     DBGrid1: TDBGrid;
     procedure Button1Click(Sender: TObject);
     { Private declarations }
     { Public declarations }

  Form1: TForm1;


{$R *.dfm}

procedure TForm1.Button1Click(Sender: TObject);
//    query1.ExecSQL;
{ the query is
    insert into table1 (c1,v2)
{ updatesql1 is linked to Table1
  the insert query is
    insert into table1 (c1,v2)


All the above is linked through BDE to a user DSN
Advanced options set to
    Use Declare/Fetch
    Parse Statements
    Unknown Sizes as Longest
    Updateable Cursors
    Server side prepare
All else is default

Results after several inserts

bigtest=# select * from table1;
                    c1                    |     v2
 characters                               | varchars
 characters                               | varchars
 characters                               | varchars
 characters-n                             | varchars-n
(4 rows)

These results are seen in both psql on the server and in the
DbGrid that is linked to the table.

No "invalid" characters were found.

I also tried changing the LANGDRIVER in the BDE to other encodings,
while leaving postgreSQL at the above encoding, and got the
same results.

I can't replicate your problem.  I upgraded to postgreSQL 7.4, and
no longer have 7.3.4 running, so I don't know if that is the problem,
or if it is a problem with BDE and D5.  Also note, I'm using
D7 Pro not D5, but I don't think the BDE components have
changed all that much over the last few versions.

One other thing check Borland's usage notes on the updatesql
component, they indicate it should only be used for readonly
datasets.  You might also try Borland's newsgroups see if
there is anything about the "invalid" characters in them.



Cristian Custodio wrote:

> I'll do this, thanks.
> Cristian
>     If you're converting an application from Oracle to PG, that
>     implies that in the Oracle DB you also had such large VARCHAR
>     fields. And since that didn't give trouble, it furthermore implies
>     that the problem is in the PG ODBC drivers.
>     Perhaps you should file a bug against them?
>>                     I'm using delphi 5 and PG: 7.3.4 and BDE
>>                     I have 1 varchar(4000) column. When I try post
>>                     any value in this column
>>                     using UpdateSQL it save very invalids caracters.
>>                     Like this: ííííííííí.
>>                     Any body could help me?
>>                     Thanks,
>>                     Cristian Luciano Custodio

In response to


pgsql-odbc by date

Next:From: Gunnar GroetschelDate: 2003-11-28 10:51:43
Subject: german characters
Previous:From: Philippe LangDate: 2003-11-28 07:24:01
Subject: Re: Timestamp column & Access linked ODBC table

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group