Hi!
Thank you.
>If you decide that it's without, you could apply a TRIM in a trigger on each
>INSERT and UPDATE. Then, you could replace the table by a view of the same
>name >and implement the TRIM on SELECT there. This way, you don't have to
>touch anything in the application.
How you provid
Hi Andrus,
Le sam. 4 avr. 2020 à 10:09, Andrus a écrit :
> Hi!
>
> >> In case of varchar field values will appear in database sometimes with
> >> trailing spaces and sometimes without.
> >> This requires major application re-design which much is more expensive
> than
> >> continuing using char f
Hi!
In case of varchar field values will appear in database sometimes with
trailing spaces and sometimes without.
This requires major application re-design which much is more expensive than
continuing using char fields.
A simple BEFORE INSERT OR UPDATE trigger would take care of that.
Changi
On Tue, 2020-03-31 at 15:13 +0300, Andrus wrote:
> > It is a simple ALTER TABLE.
>
> Client is Visual FoxPro application. It sends data with trailing spaces
> sometimes and sometimes not.
> In case of varchar field values will appear in database sometimes with
> trailing spaces and sometimes wit
Hi!
It is a simple ALTER TABLE.
Client is Visual FoxPro application. It sends data with trailing spaces
sometimes and sometimes not.
In case of varchar field values will appear in database sometimes with
trailing spaces and sometimes without.
This requires major application re-design which m
On Tue, 2020-03-31 at 11:29 +0300, Andrus wrote:
> Databases contain lot of char(n) type fields containing ascii characters.
> Most of fields contain less characters than field width.
> Changing them to varchar is not easy.
It is a simple ALTER TABLE.
> Database is accessed from Debian Postgres 1
Hi!
>Updated doc reference:
>https://www.postgresql.org/docs/12/libpq-connect.html
>They mention that compression is insecure and disabled by default. Taking this
>into account, compression will require that both ODBC and PostgreSQL are set
>>up with compression enabled. I could not figure out q
Sorry, forgot the reply all :-)
On Tue, Mar 31, 2020 at 11:39 AM Andrus wrote:
> Hi,
>
> >See the section about sslcompression in
> https://www.postgresql.org/docs/9.2/libpq-connect.html. It should be your
> answer.
>
> I added
>
> sslcompression=1
>
> to psqlodbc connection string but log file
Hi,
>See the section about sslcompression in
>https://www.postgresql.org/docs/9.2/libpq-connect.html. It should be your
>answer.
I added
sslcompression=1
to psqlodbc connection string but log file shows that connection is still
uncompressed:
LOG: connection authorized: user=me database=my
Hi!
Databases contain lot of char(n) type fields containing ascii characters.
Most of fields contain less characters than field width.
Changing them to varchar is not easy.
Database is accessed from Debian Postgres 12.2 over internet using psqlodbc
with
TLS v1.3.
Mostly results seelct commands
10 matches
Mail list logo
