Search found 5 matches
- 20.04.2009, 15:08
- Forum: 6.6 - stable
- Topic: Slowdown in zeos
- Replies: 1
- Views: 356
Slowdown in zeos
Hello, I'm using zeoslib 6.6.4 with postgresql 8.3 latest stable. My problem is that while the DB works fast (I enabled logging inside postgre) zeos seems to do a huge slowdown clientside. I do have sortfields but they're not causing it. Keyfields are causing an "internallookup" which seem...
- 08.02.2009, 16:21
- Forum: 6.6 - stable
- Topic: PostgreSQL "readonly" problem
- Replies: 1
- Views: 333
PostgreSQL "readonly" problem
Hi, I have an odd problem, but perhaps it's because I'm using table inheritance.. I don't know. In my application (using postgreSQL 8.1 and lazarus) I have a TZQuery which is used to display and edit "persons" table. "persons" inherits from "givers" table so it's a chil...
- 18.01.2008, 23:03
- Forum: 6.5.1 (alpha) - 6.6.x (beta)
- Topic: Patch for Lazarus .lpk
- Replies: 5
- Views: 1387
Hmm no idea, I just updated and bam, got missing units errors. I'll try reverting and if I get the errors again I'll paste. I don't think FPC is the culprit here, I use 2.2.1. Lazarus might have changed something though (I use always latest trunk). What about linux support? Last I tried I got some u...
- 16.01.2008, 12:50
- Forum: 6.5.1 (alpha) - 6.6.x (beta)
- Topic: Patch for Lazarus .lpk
- Replies: 5
- Views: 1387
Patch for Lazarus .lpk
I'm not sure if my SVN source is right, but if it's the active trunk then here's a patch to fix Lazarus compilation (in windows). You just forgot to update the lpk files with the new units. NOTE: I might have added some units to the zdbc.lpk which might not be strictly required. NOTE2: zoes doesn't ...
- 26.06.2007, 16:43
- Forum: 6.1.5
- Topic: Bug, and fix, for zeoslib(trunk) with FPC/Lazarus in Linux
- Replies: 1
- Views: 2404
Bug, and fix, for zeoslib(trunk) with FPC/Lazarus in Linux
I tried zeoslib from trunk on Linux (32bits, ubuntu) with FPC 2.1.5 and Lazarus/trunk. Everything went fine up until ZAbstractRODataset.pas It seems that an odd define/ifdef caused a wrong number of elements problem in procedure TZAbstractRODataset.CheckFieldCompatibility(Field: TField;FieldDef: TFi...