Zeoslib Portal

I still couldn't get what exactly is the problem. TZAbstractConn := TZConn should always work

Umm... What's the problem?

Well, "if SupportsPing then..." is indeed looks pretty nicer than "try Ping except on E: EZUnsupOp do ... end". In any case the ability of ping (pingability!) is determined manually in the code so there's no much difference in support. Moreover, base Ping could be widened to &quo...

Personally I'm fine with new exc class as well as replacing the method, but regarding the method, Jan seems to have strong objection

Not necessarily. I really like Jan's correction, I'm thinking on modifying all the other implementations to use this method (except; throw an exception, not to return 1): Sure, this method is what I meant with "avoid where possible". But there are things that couldn't be checked by availa...

Plus, what to return for Supports*, if an earlier version of client library does not support a specific operation (thinking on your FireBird adjustment)? Yes, we could hardcode version numbers but that's something I really, really don't like. Version-dependent stuff will remain anyway... of course,...

marsupilami wrote:Maybe we should extend IZDatabaseInfo with a SupportsPing method?

Does it have any sense? Any server should be "pingable" via executing an empty query. And, BTW, Ping for FB and Pg doesn't re-establish the connection which is inconsistent to MySQL implementation

I'd say Ping should return boolean flag and only raise exception when something really bad happens

Unfortunately that didn't work out (yet). I was still asked for my Sourceforge password (ssh type URL) and for github it doesn't work out because I have the # char in my password that seems to have a special meaning in URLs. Bit I seem to remember, that a credential manager can be enabled that can ...

Having a small bash script execute these commands once per hour is no problem. The problem is that I have no clue (yet) on how to store the necessary credentials with git since it seems that I canot provide them on the command line. The simplest solution is to edit %repo%\.git\config, change field ...

:D Actually I was already using TGit for my projects and SmartGit for getting SVN repos. I just added TSVN for native SVN support (and it works flawlessly with TGit-generated patches, even better than TGit itself!). Anyway my changes were not too extensive so I was comfortable with described chain. ...

As a side note, I couldn't manage to make git-svn work so I had to use SmartGit. It has UI somewhat differing from Tortoise and I still find it inconvenient for everyday work. So my workflow is: - sync Zeos SVN repo into local Git repo with SmartGit - make changes in local repo and commit them with ...

I personally is a total gitter and find SVN awkward compared to it . But other guys might be more familiar with SVN.

Fantastic! )) just let me know if the above implementation can be optimized somehow Well, we still support D7 so type helpers are a no-go. For other things it's better to wait EgonHugeist The bad thing? It only cancels connect operations. This is quite usual, I guess we need two methods - CancelConn...

Hmm, have you tried using the same connection from within canceller thread? Of course it's always a bad practice but using another connection for cancelling seems an overhead to me. Anyway these functions were supposed to work somehow! F.ex., FB function is able (and supposed to!) work with the same...