Zeoslib Portal

FPC has released 2.6.2 and the "FIXES" (stable) branch has been reversioned to 2.6.3. If there are problems with ifdef and versioning please reply in this thread (mentioning the branch) and I'll have a look. I assume Lazarus snapshots will migrate to 2.6.2 quickly, and within a month of tw...

The just released FPC 2.6.2 comes with TDS headers (and connection etc classes for SQLDB)

Note that I couldn't quickly find reports for other database types doesn't mean they don't support it.

It might be that those changes were bundled with other fixes for e.g. Mysql.

Paralel reports in sqldb:

pgsql: http://bugs.freepascal.org/view.php?id=19567

ib/FB: http://bugs.freepascal.org/view.php?id=17199 and http://bugs.freepascal.org/view.php?id=21995

This is normal when you use an outdated Zeos. (6.x)

With FPC, use the 7.x series.

IMHO such polls are useless. Either somebody is available to do the work, or not. The vote can be 200 to 1, but if nobody is willing to do the work... Also, I would do it as a separate codebase, since the databinding in Firemonkey is also different. VCL and Firemonkey are separated codebases for a r...

marcov , thank's Marco. So there is no way around to have an include file for this case. Indeed, so something like the following won't work: Then you can check the values by: {$IF defined(ZEOS_MAJOR_VERSION)} {$IF ZEOS_MAJOR_VERSION = 7} ... {$IFEND} {$ELSE} -> older then 7 {$IFEND} He or me will p...

There is none, other than passing it on the commandline (via project or not), or using an includefile. I wouldn't use components includefiles directly in applications though. It will probably give you more trouble (with paths etc) than the whole "automatic" bit is worth. Simply have an inc...

I'm totally against this. The principle of the current codebase (after my mods) is that compiler versions should never be used directly in the code. The new branches should reflect this already for the more core units. (HAVE_XX and WITH_x instead of ver<x>) The usage with compiler and version checki...

Note that on case sensitive platforms Free Pascal always tries "all lowercase". So if you keep the filenames lowercase, you can use any casing for the units.

you're right here. First, I was just trying to explain what happens on *nix. Second, there is no right or wrong way. But any way where you have to explain users several times a day where to fill in what is not optimal. But the reason for the LibrayLocation 'em selves was another one. Example: We've...

ifdef cpu64 (all 64-bit CPUs) or ifdef x86_64, but I'm not aware of a specific 64-bit issues. Afaik there is no tbookmark issue, 2.6.0 and 2.6.2 will be mostly as 2.4.x, and 2.7.x will be like D2009+ which you already support, but nobody can complain that stable zeos doesn't work with unstable FPC. ...

The whole point of that is that it is hard to explain on the Lazarus forum, if at the same time the Zeos site still advocates 6.6.6 for download as "stable".

Some strong warnings should be added.

Note that this continues to pop up regularly in Lazarus forums and maillists. Is there a chance to respin 6.6.6 with all FPC specific ifdefs removed from that file (they shouldn't be necessary anymore for at least 3 releases).? The problem is in Zeos in that it has outdated own definitions of aggreg...

Realy strange, Marco. The Bookmark handling is exacly the same, which you have introduced in \testing. No differences. Other peoples have the same trouble with the 2.x.1 releases and \trunk or \testing. Please keep your versioning straight. 2.6.1 and 2.7.1 are _totally_ different things (with 1376 ...