Search found 754 matches

by aehimself
18.11.2019, 16:19
Forum: ZeosLib 7.3/8.0 Forum
Topic: Create a new exception type for unsupported operations?
Replies: 19
Views: 590

Re: Create a new exception type for unsupported operations?

So, what about the new exception class? :)

I would also like to get rid of the RaiseUnsupportedException method, as now we have like 3 versions doing the same thing, plus 10 places simply raising the exception itself :)
by aehimself
18.11.2019, 14:20
Forum: ZeosLib 7.3/8.0 Forum
Topic: Create a new exception type for unsupported operations?
Replies: 19
Views: 590

Re: Create a new exception type for unsupported operations?

Fr0sT wrote:Version-dependent stuff will remain anyway... of course, we try to avoid such conditionals where possible.
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):
Supported.PNG
by aehimself
18.11.2019, 13:35
Forum: ZeosLib 7.3/8.0 Forum
Topic: Create a new exception type for unsupported operations?
Replies: 19
Views: 590

Re: Create a new exception type for unsupported operations?

Maybe we should extend IZDatabaseInfo with a SupportsPing method? I am strongly against it. The reason I started to think about this was the implementation of .AbortConnection, I just brought .Ping as an example. With this idea, we should create a Supports* to every method possible. This would be a...
by aehimself
18.11.2019, 09:23
Forum: ZeosLib 7.3/8.0 Forum
Topic: Create a new exception type for unsupported operations?
Replies: 19
Views: 590

Re: Create a new exception type for unsupported operations?

If a method is not implemented in the driver and / or not supported by the client library, we throw an exception: function TZAbstractDbcConnection.PingServer: Integer; begin Result := 1; RaiseUnsupportedException; end; Which is implemented like: procedure TZAbstractDbcConnection.RaiseUnsupportedExce...
by aehimself
17.11.2019, 20:18
Forum: ZeosLib 7.3/8.0 Forum
Topic: Create a new exception type for unsupported operations?
Replies: 19
Views: 590

Re: Create a new exception type for unsupported operations?

...if we inherit it from EZSQLException, no previous code should break :)
by aehimself
17.11.2019, 18:54
Forum: ZeosLib 7.3/8.0 Forum
Topic: Create a new exception type for unsupported operations?
Replies: 19
Views: 590

Create a new exception type for unsupported operations?

A couple of times I already had to determine if .Ping failed with an exception or is not supported at all. At the moment there's no other way but to check the exception class and compare the message as string. Do you think it'd break things if we would introduce a new, EZUnsupportedException type? W...
by aehimself
16.11.2019, 22:22
Forum: Off Topic
Topic: Sourceforge.io? Faster access? Smoother looking forum?
Replies: 15
Views: 41127

Re: Sourceforge.io? Faster access? Smoother looking forum?

And the forum logs me off now automatically. This is not nice :(
by aehimself
14.11.2019, 07:51
Forum: ZeosLib 7.2 Forum
Topic: ZConnection - force a complete reload of database libraries
Replies: 54
Views: 2748

Re: ZConnection - force a complete reload of database libraries

Fyi, two ways to keep an SVN repo in sync with GitHub automatically:

https://github.com/frones/ZeosLib/issues/1 (see comments)
https://github.com/gabrys/svn2github They say this used to be an online service, but this script was the heart of it
by aehimself
13.11.2019, 21:59
Forum: ZeosLib 7.2 Forum
Topic: ZConnection - force a complete reload of database libraries
Replies: 54
Views: 2748

Re: ZConnection - force a complete reload of database libraries

I see @Jan you are not using Windows, but it might help other fellas one day. In my Git global config I set

[credential]
helper = manager

First time during sync VS code asked for a user name / password and saved it to Network Passwords. And never asked again :)
by aehimself
13.11.2019, 20:52
Forum: ZeosLib 7.3/8.0 Forum
Topic: Zeos 7.3 testers-thread
Replies: 286
Views: 46760

Re: Zeos 7.3 testers-thread

Is there a place with logs to see why builds failed on specific IDEs / platforms?
I guess my code broke some, but I don't have access to these to see where and what I have to correct.

Thanks!
by aehimself
12.11.2019, 21:17
Forum: ZeosLib 7.2 Forum
Topic: ZConnection - force a complete reload of database libraries
Replies: 54
Views: 2748

Re: ZConnection - force a complete reload of database libraries

Anything to satisfy new developers ;) Honestly you are not the first to ask about git. Does it mean you already consider me as a contributor for Zeos? :) Would be an honor, as I started using this suite back in the 6.6 days. Feels good to finally give something back :) Maybe it can help in attracti...
by aehimself
12.11.2019, 11:44
Forum: ZeosLib 7.2 Forum
Topic: ZConnection - force a complete reload of database libraries
Replies: 54
Views: 2748

Re: ZConnection - force a complete reload of database libraries

Sure thing! I guess I'll keep using testing-7.3-aehimself, will just cherry pick things back to testing-7.3 and only send pull requests on that branch. I hope these extra things are not a huge hassle though, I kinda feel like a special snowflake who requires special treatment :S Btw - is the branch ...
by aehimself
12.11.2019, 10:19
Forum: ZeosLib 7.2 Forum
Topic: ZConnection - force a complete reload of database libraries
Replies: 54
Views: 2748

Re: ZConnection - force a complete reload of database libraries

So I played around a little bit with an automatic syncing and I messed up my repository so much I had to recreate it. I lost the test app in the process, but I still could copy the code from the cancelled pull request so all is fine :) I came up with a small batch file which will (should :D ) sync a...
by aehimself
12.11.2019, 08:40
Forum: ZeosLib 7.2 Forum
Topic: ZConnection - force a complete reload of database libraries
Replies: 54
Views: 2748

Re: ZConnection - force a complete reload of database libraries

So maybe it works, maybe it does not, but it does something :) I find it a bit more safe not to add the "upstream" repository (to avoid accidental commits) and fortunately there is a way: https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repo...