Page 2 of 2

Posted: 22.06.2012, 21:30
by calico
Ok Miab3, com MySQL5 funciona. Mas com o postgresql 8.2 a comobo ficar em um estado muito estranho.Acho que o comportamento errado ocorre apenas com a conexão postgresql.
Tks

Posted: 22.06.2012, 21:54
by calico
Ok Miab3, com MySQL5 funciona. Mas com o postgresql 8.2 a comobo ficar em um estado muito estranho.Acho que o comportamento errado ocorre apenas com a conexão postgresql.
Tks

Posted: 22.06.2012, 21:58
by miab3
calico

Not as I understand what you're saying but for PostgeSQL 9.1, Delphi XE2 and Zeos7eh1405 Lookup looks at me like that:


Michal

Posted: 23.06.2012, 16:10
by miab3
@EgonHugeist

Hold adding the package XE2. Something is not right. I'm working on it.

Michal Abramczyk

Posted: 23.06.2012, 18:15
by EgonHugeist
@miab3,

No problem, didn't commit it actually. I've just uploaded some TZQuery.Parameter fixes for Firebird, MySQL, PostgrSQL if TZConnection.ClientCodePage is an ANSI CodePage while making breakfast and lunch. I've seen That the FullUnicode IDE's did assume allways the stUnicodeString if we say TZQuery.ParamByName('x').AsString := AString. But this is not right for ANSI connections. This is fixed now.

Concerning the calico, reported issue. Did you ownload his movies, Michal? I've opened my PostgreSQL with ClientCodePage = WIN1252 (western european ansi charset). In this ANSI mode i was able to type in the values as fast as his second monitor does show it. But on open the connection in unicode the intyped values have a different behavior. Now i can't see an issue on Zeoas 'em selves. The locate values are comming from the delphi DB-Unit. Also the buffer clearing is done from delphi.... So as far as i can see does Zeos have no possibilities to changes this behavior here. Also i can't confirm that the mouse select doesn't work correctly but i've got an feeling what's going wrong on his side.

calico,
can you tell me which fieldtype is assigned for the lookupcombobox in the second monitor? is it ftString instead of ftWideString? Also i have to know which fieldtype the lookup values do have and the datafield where they should be assigned.

Michael

Posted: 25.06.2012, 21:02
by calico
Hello folks,

Apparently the location as you typing is ok (version 1411). Now when I add the fileds in fildlist comes all fields readonly = true. Put false for all, will save when the error.
'Cannot update this query type'.

Posted: 26.06.2012, 11:51
by EgonHugeist
calico,

now i can only barrely follow you. Which fields are readonly now? These of Zeos or ADO? Which fieldtype does the ADO-Connection assume for varchar() fields?

Michael

Posted: 27.06.2012, 08:10
by miab3
@EgonHugeist

Also do not fully understand but I noticed that sometimes in readonly mode ZEOS painfully slow(about 10 times). There must be some error.

Michal

Posted: 27.06.2012, 16:01
by EgonHugeist
@miab3,

hum that is bad. Which component did you set to ReadOnly? Which protocol?

Michael

Posted: 03.07.2012, 12:09
by Shagrat3

Posted: 04.07.2012, 13:28
by EgonHugeist
Shagrat3,

no it isn't these lines do not exist on my branch..

Michael

Posted: 05.07.2012, 12:12
by miab3
@EgonHugeist

I can not play a situation in which I watched, but I remember the few times I had with this phenomenon (big slowdown) experience.
Recently I just do not use readonly.

Michal

Posted: 05.07.2012, 12:59
by EgonHugeist
miab3,

Michal, yes that's right. I'm also not able to reproduce this video issue. All is working fine for me. Btw. can sombody tell me how he made this little video? Thinking about tutorials! Somtimes pictures do say more then thausends words in my mind...

Hmm the ReadOnly is a thing i didn't touched yet. I've got an idea what's going wrong but actually no solution only thoughts..

Michael