Zeoslib Portal

What do you expect to get selecting two fields with the same name? I don't know what exactly the driver returns in this case but any high-level component will be confused with this task anyway. All dataset components are designed based on the presumption that field names are unique. Some "smart...

I think there's no doubts this should be an optional/configurable behavior. But then we must decide what kind of configuration to use. FireDAC's suggest to use signature patterns in domain names is not bad but it is new to Zeos which uses name-value configs on DB and dataset level. Moreover, this fe...

This question is better to discuss with project commanders like Jan and Michael (and in separate thread I guess). I personally don't bother the branch status, I just use the latest 7.3 (mostly because it has the features I need)

Speaking of the Zeos 7.3, I wonder when 7.2 will become a release and get rid of beta test status? Honestly I think one can declare any of the latest 7.2 commits "a release". In fact, the beta or release status of 7.2 won't change things much. It gets only fixes anyway, no new features or...

we might be in trouble because these files were distributed under the InterBase Public License Version 1.0. That't what the original IBEvents.pas says. I doubt that the InterBase Public Licens allows to reuse their code with any other license we wish. I'm not competent in license stuff but borrowin...

Done

Creating generic routine is not that simple as it could seem... 1) Backticks are not supported by all DBC's, f.ex. Firebird complaints on them. Moreover (for FB; I've no idea regarding other drivers) when you create a DB object with quoted name it remains quoted meaning all further operations will r...

I doubt OEM conversion is ever needed for anything... it's something ancient from the DOS ages. I'd say you could just make this stuff unavailable under WinCE platform.

What PChar() -> PWideChar() conversion problems do you face?

TDataSet components are of no use here. In ExecuteNoResult you already use parameters. So just call it with TDateTime values instead of string

No matter if the subject is a bug or not, using timestamp values converted to string is always prone to errors and of course slow.

It's not an answer but couldn't you just use TDateTime parameters in query?

Is Interbase 5 really needed to be supported? TZInterbase6DatabaseMetadata.UncachedGetProcedureColumns contains complex and very inefficient code only because IB5 lacks one metadata field. But the driver for IB mentions it only supports v6. Maybe it's time to drop support of ancient stuff?

I did consider raising exceptions if error is not hadled initially, but then realized that this way I would change current behavior of the component and decided playing safe. The other reason - I've found no way (strangely) to handle exceptions from timer events on Lazarus... TApplicationProperties...

miab3, you're right. But I guess the credits must mention original authors, mustn't they? And maybe we could borrow some code from this fork ? They say they've rewritten the unit. This unit has been almost completely re-written as the original code was not that robust - and I am not even sure if it ...

if not isHandled then raise; I'm not sure that raising exceptions in OnTimer is a good idea... Also I don't like the way errors are handeled by TZIBEventAlerter. TIBEventThread.SQueEvents uses an exception. But it only queues an error code and not the exception message. I don't see a good reason to...

There's a;ready ZIBEventAlerter unit with error handling so the change should be done accordingly. Some code style suggestions: - const ErrorMessage in TZPgErrorEvent. In 7.3 all ref-counted types in parameters made const or var to avoid excess ref changing. - FOnError instead of FErrorHandler (why ...