Hello, sorry for late reply; the mail with sample is on your way.
Thank you!
Search found 27 matches
- Fri 18 Mar 2016 18:55
- Forum: dbExpress driver for PostgreSQL
- Topic: accentuated characters problem with latest release
- Replies: 4
- Views: 24439
- Fri 11 Mar 2016 14:13
- Forum: dbExpress driver for PostgreSQL
- Topic: accentuated characters problem with latest release
- Replies: 4
- Views: 24439
accentuated characters problem with latest release
Hello, after upgrading from 3.5.7 to 3.7.10 I am having troubles with accentuated characters.
Settings of my postgresql 9.5 database are encoding UTF8 and locale C.
If for example in my database I have character à it is retrieved as Ã
I've done some tests and write operations are not affected, only retrieval.
Reverting back to previous release solve the issue.
Please let me know if you need more details to reproduce.
Thank you.
Settings of my postgresql 9.5 database are encoding UTF8 and locale C.
If for example in my database I have character à it is retrieved as Ã
I've done some tests and write operations are not affected, only retrieval.
Reverting back to previous release solve the issue.
Please let me know if you need more details to reproduce.
Thank you.
- Mon 04 May 2015 10:01
- Forum: Universal Data Access Components
- Topic: Postgresql slow query fetch
- Replies: 27
- Views: 4451
Re: Postgresql slow query fetch
Hello,
someone tested if this behaviour does affect recent versions of plain simple pgdac too?
someone tested if this behaviour does affect recent versions of plain simple pgdac too?
- Fri 23 Jan 2015 13:25
- Forum: dbExpress driver for PostgreSQL
- Topic: postgres v. 9.4
- Replies: 3
- Views: 10511
Re: postgres v. 9.4
great! thank you
- Tue 20 Jan 2015 11:18
- Forum: dbExpress driver for PostgreSQL
- Topic: postgres v. 9.4
- Replies: 3
- Views: 10511
postgres v. 9.4
Hello,
does the current version of driver works with PG 9.4?
thanks...
does the current version of driver works with PG 9.4?
thanks...
- Sat 13 Oct 2012 18:04
- Forum: PostgreSQL Data Access Components
- Topic: problem after installing pgdac
- Replies: 2
- Views: 1767
Re: problem after installing pgdac
That was!! I was convinced I've already installed the hotfix, but was in another virtual machine.... All ok now, thanks a lot...
- Thu 11 Oct 2012 22:02
- Forum: PostgreSQL Data Access Components
- Topic: problem after installing pgdac
- Replies: 2
- Views: 1767
problem after installing pgdac
Hi all,
I've tried to setup pgdac latest release 3.5.9 on my XE2 installation (all upgrades and hotfixes applied). But trying to start Delphi it does tell me that is unable to upload dlcpgdac160.bpl because fmx163.bpl is missing (???). So I uninstalled 3.5.9 and I tried installing previous release 3.2.8 but I obtained the same error.
What's wrong???
I've tried to setup pgdac latest release 3.5.9 on my XE2 installation (all upgrades and hotfixes applied). But trying to start Delphi it does tell me that is unable to upload dlcpgdac160.bpl because fmx163.bpl is missing (???). So I uninstalled 3.5.9 and I tried installing previous release 3.2.8 but I obtained the same error.
What's wrong???
- Tue 22 May 2012 13:42
- Forum: PostgreSQL Data Access Components
- Topic: PgDac and hotfix
- Replies: 4
- Views: 1707
Re: PgDac and hotfix
Everything can be done... simply it does cost me too much effort... uninstall and reinstall all the components etc... no thanks, I wait next build of pgdac... next time before experimenting myself is better I wait a little bit and let someone else do the test for me....
- Tue 22 May 2012 12:56
- Forum: PostgreSQL Data Access Components
- Topic: PgDac and hotfix
- Replies: 4
- Views: 1707
Re: PgDac and hotfix
...I have no alternative but to wait... sorry no money to upgrade right now, and this hotfix cannot be rolled back (it's clearly stated in readme)..... I hope this post can be useful for someone else, at least.....
- Tue 22 May 2012 09:33
- Forum: PostgreSQL Data Access Components
- Topic: PgDac and hotfix
- Replies: 4
- Views: 1707
PgDac and hotfix
Hi,
I've installed the Delphi XE2 4.1 hotfix, but now when I start the IDE it does complain that dacfmx160.bpl, dclpgdac160.bpl and pgdacfmx160.bpl should be recompiled; I think a new recompiled release of PgDac is required... too bad hotfix cannot be installed, so the new release is pretty urgent
Thanks...
I've installed the Delphi XE2 4.1 hotfix, but now when I start the IDE it does complain that dacfmx160.bpl, dclpgdac160.bpl and pgdacfmx160.bpl should be recompiled; I think a new recompiled release of PgDac is required... too bad hotfix cannot be installed, so the new release is pretty urgent
Thanks...
- Mon 20 Feb 2012 14:08
- Forum: PostgreSQL Data Access Components
- Topic: problem with macro
- Replies: 3
- Views: 1683
- Mon 20 Feb 2012 11:09
- Forum: PostgreSQL Data Access Components
- Topic: problem with macro
- Replies: 3
- Views: 1683
problem with macro
Hello, this is the first time I try to use macro, but I'm having a problem...
sql of a pgquery component is declared this way:
select * from table where field in &IN
then in code I prepare my string like this: S := '(1, 2, 3)' and assign S to the macro with pgquery1.macrobyname('IN').AsString := S
but when I try to open pgquery1 I receive an error.
Looking through dbmonitor I can see that macro get quoted inside SQL statement, so what is passed to postgresql is:
select * from table where field in '(1, 2, 3')'
I've tried to assign macro with AnsiDequotedStr(S) but (as I expected, by the way) didn't work.
Thanks for help......
sql of a pgquery component is declared this way:
select * from table where field in &IN
then in code I prepare my string like this: S := '(1, 2, 3)' and assign S to the macro with pgquery1.macrobyname('IN').AsString := S
but when I try to open pgquery1 I receive an error.
Looking through dbmonitor I can see that macro get quoted inside SQL statement, so what is passed to postgresql is:
select * from table where field in '(1, 2, 3')'
I've tried to assign macro with AnsiDequotedStr(S) but (as I expected, by the way) didn't work.
Thanks for help......
- Wed 25 Jan 2012 16:17
- Forum: dbExpress driver for PostgreSQL
- Topic: issue with twidememo param
- Replies: 1
- Views: 2776
issue with twidememo param
dear sirs,
here's what I've found:
environment:
postgresql 9.1; database UTF-8
D2006 w all patches; last release of dbexpress driver used
Issue found:
updating a table using parametrized query if there’s a text field to update all goes well if the parameter is set to null or some non-empty string;
if the parameter is set to empty string we receive error ‘insufficient data left in message’in case of unicode on in connection; access violation if unicode is off (but probably because of twidememo datatype in param, didn’t check with ftmemo simple)
In case you need more details pls ask me
to speed up things I've already sent test case zipped file to alexp..
best regards
Roberto Icardi
here's what I've found:
environment:
postgresql 9.1; database UTF-8
D2006 w all patches; last release of dbexpress driver used
Issue found:
updating a table using parametrized query if there’s a text field to update all goes well if the parameter is set to null or some non-empty string;
if the parameter is set to empty string we receive error ‘insufficient data left in message’in case of unicode on in connection; access violation if unicode is off (but probably because of twidememo datatype in param, didn’t check with ftmemo simple)
In case you need more details pls ask me
to speed up things I've already sent test case zipped file to alexp..
best regards
Roberto Icardi
- Thu 29 Dec 2011 13:59
- Forum: dbExpress driver for PostgreSQL
- Topic: socket error 10061
- Replies: 2
- Views: 3955
- Wed 28 Dec 2011 17:21
- Forum: dbExpress driver for PostgreSQL
- Topic: socket error 10061
- Replies: 2
- Views: 3955
socket error 10061
Hello,
error in subject is what I see at every db operation. This error is visible only while debugging (directly launching the application the error is probably
trapped inside driver and not seen outside). Honestly today is the first time
I see this error...
Rather annoying, I ended up telling Delphi to ignore that exception class...
But I'd like to know where does come from...
My environment: Delphi 2006 and Postgres 8.3 last release of driver.
Thanks!
error in subject is what I see at every db operation. This error is visible only while debugging (directly launching the application the error is probably
trapped inside driver and not seen outside). Honestly today is the first time
I see this error...
Rather annoying, I ended up telling Delphi to ignore that exception class...
But I'd like to know where does come from...
My environment: Delphi 2006 and Postgres 8.3 last release of driver.
Thanks!