SQL-Ledger Homepage

SQL-Ledger User Forum

Forum index page

Log in | Register

Back to the board
Thread view  Mix view  Order
hartundweich(R)

Homepage

Austria,
11.04.2016, 09:56
 

Important Notice about DBD::Pg Version (General)

Hello everybody,

sorry for posting so much in the last days - but now I have found the solution for my german special characters problem which occurs since SL 3.2.0 - thanks for giving some information about his server setup to user "localguru".

It turned out, that SL 3.2.0 is not working properly with DBD-PG > 3.2.1 - I tried with 3.4.2 and 3.5.3 - both were not able to handle my german special characters.
Once i uninstalled DBD-PG V3.x and installed the latest V2 of DBD-Pg everything worked as supposed to do.


Also have a look at this forum post: http://www.nntp.perl.org/group/perl.dbd.pg/2016/01/msg778.html

Maybe it gets fixed in the next DBD::Pg Release?

As a temporary workaround I will continue using DBD-Pg 2.19.3 or DBD-Pg 3.2.1 - this version also works as supposed to do.

So sorry for thinking that SL has a bug included - IMHO it is DBD-Pg which is buggy since version greater than 3.2.1


Regards,

Andreas Fragner

pjaouen(R)

13.04.2016, 12:32

@ hartundweich

Important Notice about DBD::Pg Version

Hello everybody,

sorry for posting so much in the last days - but now I have found the
solution for my german special characters problem which occurs since SL
3.2.0 - thanks for giving some information about his server setup to user
"localguru".

It turned out, that SL 3.2.0 is not working properly with DBD-PG > 3.2.1 -


Happy to read that.
I have french characters problems for about 6 months without any change other than different upgrades

hartundweich(R)

Homepage

Austria,
13.04.2016, 14:24

@ pjaouen

Important Notice about DBD::Pg Version

Hello,

it would be helpful if you share your config and versions with us - especially:

what says "locale" on the console?
Collation and encoding of Postgres database - best seen at phppgadmin web interface
Which version of Apache webserver?
Which version of perl language?
Which version of DB-Pg?
Which version of SQL Ledger?
Have you set "AddDefaultCharset On" in your Apache configuration for your SQL Ledger installation?
And finally: which language settings do you use in your SQL Ledger installation?

Do you french special characters look allright in phppgadmin webinterface?

When you work with PDF documents generated from SQL Ledger - which encoding do these files have? And uses the latex document the same encoding as the database/your SQL Legder language settings/the file encoding of the latex document itself?

I think your problem can be easily solved if you share these informations with us.

But one thing is sure: if you use SQL Ledger 3.2.0 with DBD-PG > 3.2.1 there are issues with UTF 8 encoding in sending and receiving data from the postgres database. If you intend to use SQL Ledger you must not use DBD-PG greater than version 3.2.1

pjaouen(R)

14.04.2016, 04:18

@ hartundweich

Important Notice about DBD::Pg Version

Hello,

it would be helpful if you share your config and versions with us -
especially:

what says "locale" on the console?
Collation and encoding of Postgres database - best seen at phppgadmin web
interface
Which version of Apache webserver?
Which version of perl language?
Which version of DB-Pg?
Which version of SQL Ledger?
Have you set "AddDefaultCharset On" in your Apache configuration for your
SQL Ledger installation?
And finally: which language settings do you use in your SQL Ledger
installation?

Do you french special characters look allright in phppgadmin webinterface?

When you work with PDF documents generated from SQL Ledger - which encoding
do these files have? And uses the latex document the same encoding as the
database/your SQL Legder language settings/the file encoding of the latex
document itself?

I think your problem can be easily solved if you share these informations
with us.


all utf-8 since 2008 without problem

SuSE 421 :
postgres 9.4
apache 2.4.16
perl 5.18.2
DB-Pg 3.5.1
sql ledger 3.2.0
DBI 1.628

I have another machine SuSE 11.4 running for my osCommerce website (needs old php)
postgres 9.0.19
apache 2.2.17
perl 5.12.3
DB-Pg 2.17.2
SQL ledger 3.0.5
DBI 1.616

I am pretty sure SQL-Ledger is running correctly on this old config but I cannot access my data anymore (dataset is newer than version)

I use the 3.2.0 version and I correct data with phpPgAdmin if needed (hopefully bad data are always at the end of tables)

pjaouen(R)

14.04.2016, 07:34

@ pjaouen

Important Notice about DBD::Pg Version

I have another machine SuSE 11.4 running for my osCommerce website (needs
old php)
postgres 9.0.19
apache 2.2.17
perl 5.12.3
DB-Pg 2.17.2
SQL ledger 3.0.5
DBI 1.616

I am pretty sure SQL-Ledger is running correctly on this old config but I
cannot access my data anymore (dataset is newer than version)


I have restarted postgresql server with the remaining old data set (2013) etc... on the old machine : no problem
I have upgraded to SQL-Ledger 3.2.0 : no problem

my SQL-Ledger problem is due to other programs (probably DB-Pg newer version)

hartundweich(R)

Homepage

Austria,
14.04.2016, 15:16

@ pjaouen

Important Notice about DBD::Pg Version

DB-Pg 3.5.1
sql ledger 3.2.0

Hello,

the above combination is your problem - you must downgrade DBD-Pg to a version equal or lower 3.2.1.

I googled a little bit for that - I found a suitable rpm for x86_64: ftp://rpmfind.net/linux/opensuse/di...l-DBD-Pg-2.19.3-2.1.3.x86_64.rpm

Or you can also downlad the latest working DBD-Pg version here and compile it on your own:
http://search.cpan.org/~turnstep/DBD-Pg-3.2.1/

But I think you have to uninstall DBD-Pg 3.5.1 first before you can install an older version. I do not know how exactly you can install these special versions on your OpenSuse system, because I am using gentoo for about 20 years - it is a source based distribution. That means a little bit more work for the first install of a machine, but very very very flexible when you have to install certain versions of special software.

I hope this helps - at the moment this is the only way how to solve the special characters issue with SQL Ledger 3.2.0 - and you have to remove "AddDefaultCharset On" from your vhost configuration.

Best whishes,

Andreas Fragner

pjaouen(R)

14.04.2016, 17:24

@ hartundweich

Important Notice about DBD::Pg Version

DB-Pg 3.5.1
sql ledger 3.2.0

Hello,

the above combination is your problem - you must downgrade DBD-Pg to a
version equal or lower 3.2.1.

I googled a little bit for that - I found a suitable rpm for x86_64:
ftp://rpmfind.net/linux/opensuse/di...l-DBD-Pg-2.19.3-2.1.3.x86_64.rpm


works correctly

Thanks

Brian Dunn(R)

23.06.2016, 18:26

@ hartundweich

Important Notice about DBD::Pg Version

solution for my german special characters problem which occurs since SL
3.2.0


Does SQL-Ledger v3.2.1 work with DBD-PG > 3.2.1? The SQL-Ledger change log mentions character encoding options.

hartundweich(R)

Homepage

Austria,
15.12.2016, 04:10

@ Brian Dunn

Important Notice about DBD::Pg Version

Upgraded my SL today from 3.2.0 to 3.2.1 - had to add "AddDefaultCharset utf-8" to my vhost configuration to get my web frontend with all characters in the right way.
Then I tried to use DBD-PG V3.4 and V3.5 - no success, switched back to 2.19.3 and everything is working like a charme.
As already mentioned: I think it is a bug in DBD-PG which appeared when V3.x was released and was not corrected until now.

Back to the board
Thread view  Mix view  Order
986 Postings in 324 Threads, 327 registered users, 127 users online (0 registered, 127 guests)
SQL-Ledger User Forum | Admin contact
RSS-Feed
powered by my little forum