Re: [Firebird-devel] Planning the post v3 development

2014-05-01 Thread Leyne, Sean
> > If you look at SQL Server, there jobs themselves are not defined for a > > specific database (although they may depend on one or more databases). > > AFAIK they are stored in the master database. Execution requires an > > Agent service to be running. > > We neither have a master database, no

Re: [Firebird-devel] Planning the post v3 development

2014-04-29 Thread Jim Starkey
On 4/28/2014 10:29 AM, Carlos H. Cantu wrote: > 3) A way to schedule some tasks direct in FB, for example, > running procures, sweeps, statistics recalcs, etc. at specific > scheduled days/times. What would be accepted as a task could be > limited to whatever you guys thinks that would be "safe" to

Re: [Firebird-devel] Planning the post v3 development

2014-04-29 Thread Carlos H. Cantu
>> So, for Firebird, I think that it would be up to the user and/or the >> software developer to decide how they would want to execute such >> tasks(either creating their own service, or using a batch/script to >> execute the commands scheduled via a task scheduler). As an example, >> our applicati

Re: [Firebird-devel] Planning the post v3 development

2014-04-29 Thread Adriano dos Santos Fernandes
On 29/04/2014 12:04, Dmitry Yemanov wrote: > 29.04.2014 18:11, Claudio Valderrama C. wrote: > >>> Maybe true for the current FB code, but not generally. Other >>> databases can handle this reliably. >> But they have a limited degree of data versioning, if any. > AFAIK, PostgreSQL can handle transac

Re: [Firebird-devel] Planning the post v3 development

2014-04-29 Thread Dmitry Yemanov
29.04.2014 18:11, Claudio Valderrama C. wrote: >> Maybe true for the current FB code, but not generally. Other >> databases can handle this reliably. > > But they have a limited degree of data versioning, if any. AFAIK, PostgreSQL can handle transactional DDL. And yes, it's pretty as much MGA as

Re: [Firebird-devel] Planning the post v3 development

2014-04-29 Thread Jim Starkey
On 4/24/2014 6:19 AM, Dmitry Yemanov wrote: All, We're getting closer to the v3.0 feature freeze which is going to happen this summer. Everything roadmapped for v3 but not implemented before the deadline will be postponed. The next-after-v3 release is likely to incorporate most of the postponed

Re: [Firebird-devel] Planning the post v3 development

2014-04-29 Thread Claudio Valderrama C.
> -Original Message- > From: Dmitry Yemanov [mailto:firebi...@yandex.ru] > Sent: Martes, 29 de Abril de 2014 3:44 > > 29.04.2014 01:21, Claudio Valderrama C. wrote: > > > I know people will feel outraged with my opinion, but > anyway: make DDL > > operations atomic and immediate. > > A

Re: [Firebird-devel] Planning the post v3 development

2014-04-29 Thread Alex Peshkoff
On 04/29/14 16:46, Daniel Rail wrote: > Hi, > > At April 29, 2014, 5:09 AM, Mark Rotteveel wrote: > >> On Tue, 29 Apr 2014 11:58:57 +0400, Dmitry Yemanov >> wrote: >>> Who should initiate that dedicated listener deamon/user after a server >>> restart? Should the server attach all the databases its

Re: [Firebird-devel] Planning the post v3 development

2014-04-29 Thread Daniel Rail
Hi, At April 29, 2014, 5:09 AM, Mark Rotteveel wrote: > On Tue, 29 Apr 2014 11:58:57 +0400, Dmitry Yemanov > wrote: >> Who should initiate that dedicated listener deamon/user after a server >> restart? Should the server attach all the databases itself to check >> whether one needs a startup? W

Re: [Firebird-devel] Planning the post v3 development

2014-04-29 Thread Carlos H. Cantu
DY> 28.04.2014 23:05, Carlos H. Cantu wrote: >> I think most of them needs basic asynchronous replication, covering >> single and multi-master scenarios. For those who needs more complex >> scenarios, there are third party comercial tools. Anyway, I'm not the >> right person to answer, since I di

Re: [Firebird-devel] Planning the post v3 development

2014-04-29 Thread Carlos H. Cantu
>> 5) An embedded Firebird version for Android (even if only "basic" >> server features could be available): >> http://tracker.firebirdsql.org/browse/CORE-3885 A> Why do you treat it as post-v3? I plan to activate work with Android A> port after beta1. Really?! That's a great news!!! []s Carlo

Re: [Firebird-devel] Planning the post v3 development

2014-04-29 Thread Alex Peshkoff
On 04/29/14 13:49, Dimitry Sibiryakov wrote: > 29.04.2014 11:07, Alex wrote: >> On 04/29/2014 12:49 PM, Dimitry Sibiryakov wrote: >> >>> May be stop separate metadata cache at all and use ordinary data >>> cache for reading >>> system tables directly every time. >> And have prepare time incr

Re: [Firebird-devel] Planning the post v3 development

2014-04-29 Thread Dimitry Sibiryakov
29.04.2014 11:07, Alex wrote: > On 04/29/2014 12:49 PM, Dimitry Sibiryakov wrote: > >> May be stop separate metadata cache at all and use ordinary data cache >> for reading >> system tables directly every time. > > And have prepare time increased many times... > Not an option due to performan

Re: [Firebird-devel] Planning the post v3 development

2014-04-29 Thread Dimitry Sibiryakov
29.04.2014 11:17, Dmitry Yemanov wrote: > So user snapshot transaction should not seen changes done by itself (as > user thinks, as it executes DDL in the same transaction)? That's why I think that executing DDL in separate autocommit transaction is a bad idea. -- WBR, SD. --

Re: [Firebird-devel] Planning the post v3 development

2014-04-29 Thread Dmitry Yemanov
29.04.2014 13:05, Vlad Khorsun wrote: > Technically - it is possible. Practically - what generation of altered object > user transaction should work with ? Statements already having the object cached - the old version. Statements to be [re]prepared - the new version, as the metadata cache will

Re: [Firebird-devel] Planning the post v3 development

2014-04-29 Thread Dmitry Yemanov
29.04.2014 13:12, Dimitry Sibiryakov wrote: > According to its isolation level, I'd say. So user snapshot transaction should not seen changes done by itself (as user thinks, as it executes DDL in the same transaction)? Of course it can be documented, but I'd rather avoid such a tricky behavior.

Re: [Firebird-devel] Planning the post v3 development

2014-04-29 Thread Dimitry Sibiryakov
29.04.2014 11:05, Vlad Khorsun wrote: > Practically - what generation of altered object > user transaction should work with ? According to its isolation level, I'd say. -- WBR, SD. -- "Accelerate Dev Cycles with

Re: [Firebird-devel] Planning the post v3 development

2014-04-29 Thread Alex
On 04/29/2014 12:49 PM, Dimitry Sibiryakov wrote: >> And reimplement the metadata cache to become two-level - global and >> transaction-wise, with objects in the latter overriding objects in the >> former. > May be stop separate metadata cache at all and use ordinary data cache > for reading

Re: [Firebird-devel] Planning the post v3 development

2014-04-29 Thread Vlad Khorsun
> 29.04.2014 12:03, Vlad Khorsun wrote: > >> So, i see autocommit as only possibility, if we choose "Oracle way" > > Out of curiosity, why cannot it be done in a separate *non-system* > transaction? I.e. instead of committing user transaction start we and > immediately commit a new one. Te

Re: [Firebird-devel] Planning the post v3 development

2014-04-29 Thread Dimitry Sibiryakov
29.04.2014 10:03, Dmitry Yemanov wrote: > 29.04.2014 02:02, Dimitry Sibiryakov wrote: > >> I may be wrong as often, but AFAIU this dream may be a reality if: >> >> 1) Eliminate DFW >> 2) Perform DDL (operations with system tables) in user transaction > > 3) Make garbage collector to handle system

Re: [Firebird-devel] Planning the post v3 development

2014-04-29 Thread Dimitry Sibiryakov
29.04.2014 0:16, Claudio Valderrama C. wrote: >> -Original Message- >> From: Dimitry Sibiryakov [mailto:s...@ibphoenix.com] >> Sent: Lunes, 28 de Abril de 2014 18:03 >> >> I may be wrong as often, but AFAIU this dream may be a reality if: >> >> 1) Eliminate DFW > > I'm not sure "eliminate"

Re: [Firebird-devel] Planning the post v3 development

2014-04-29 Thread Dmitry Yemanov
29.04.2014 12:03, Vlad Khorsun wrote: > So, i see autocommit as only possibility, if we choose "Oracle way" Out of curiosity, why cannot it be done in a separate *non-system* transaction? I.e. instead of committing user transaction start we and immediately commit a new one. Dmitry -

Re: [Firebird-devel] Planning the post v3 development

2014-04-29 Thread Alex
On 04/29/2014 12:03 PM, Vlad Khorsun wrote: >>> I know people will feel outraged with my opinion, but anyway: make DDL >>> operations atomic and immediate. > This is the "Oracle way". > >> Atomic and immediate means autocommitted or always executed in a >> separate (e.g. system) transaction

Re: [Firebird-devel] Planning the post v3 development

2014-04-29 Thread Dmitry Yemanov
29.04.2014 12:09, Mark Rotteveel wrote: > If you look at SQL Server, there jobs themselves are not defined for a > specific database (although they may depend on one or more databases). > AFAIK they are stored in the master database. Execution requires an Agent > service to be running. We neither

Re: [Firebird-devel] Planning the post v3 development

2014-04-29 Thread Mark Rotteveel
On Tue, 29 Apr 2014 11:58:57 +0400, Dmitry Yemanov wrote: > Who should initiate that dedicated listener deamon/user after a server > restart? Should the server attach all the databases itself to check > whether one needs a startup? What about databases unknown to the server > (not present in da

Re: [Firebird-devel] Planning the post v3 development

2014-04-29 Thread Dmitry Yemanov
29.04.2014 02:02, Dimitry Sibiryakov wrote: > I may be wrong as often, but AFAIU this dream may be a reality if: > > 1) Eliminate DFW > 2) Perform DDL (operations with system tables) in user transaction > 3) Make garbage collector to handle system tables well And reimplement the undo log to hand

Re: [Firebird-devel] Planning the post v3 development

2014-04-29 Thread Vlad Khorsun
>> I know people will feel outraged with my opinion, but anyway: make DDL >> operations atomic and immediate. This is the "Oracle way". > Atomic and immediate means autocommitted or always executed in a > separate (e.g. system) transaction? I have strong opinion that system transaction

Re: [Firebird-devel] Planning the post v3 development

2014-04-29 Thread Dmitry Yemanov
28.04.2014 23:31, Dalton Calford wrote: > > Architecturally, Firebird database is not active without user > connections. This slightly changes with the LINGER support, but not so > much. So the question is who should be waiting for the timer events when > nobody is connected. And if

Re: [Firebird-devel] Planning the post v3 development

2014-04-29 Thread Mark Rotteveel
On Mon, 28 Apr 2014 15:36:45 -0300, Adriano dos Santos Fernandes wrote: > On 28/04/2014 15:30, Dmitry Yemanov wrote: >>> 2. Add JAVA, .NET PROCEDURE and FUNCTION (not just C++) >> You can do it in v3 as soon as someone writes the required interfacing >> plugins (external engines). Volunteers anyo

Re: [Firebird-devel] Planning the post v3 development

2014-04-29 Thread Dmitry Yemanov
29.04.2014 01:21, Claudio Valderrama C. wrote: > I know people will feel outraged with my opinion, but anyway: make DDL > operations atomic and immediate. Atomic and immediate means autocommitted or always executed in a separate (e.g. system) transaction? > Uncommitted DDL and DML working in un

Re: [Firebird-devel] Planning the post v3 development

2014-04-29 Thread Dmitry Yemanov
28.04.2014 23:05, Carlos H. Cantu wrote: > I think most of them needs basic asynchronous replication, covering > single and multi-master scenarios. For those who needs more complex > scenarios, there are third party comercial tools. Anyway, I'm not the > right person to answer, since I didn't need

Re: [Firebird-devel] Planning the post v3 development

2014-04-29 Thread Dmitry Yemanov
29.04.2014 02:13, Thomas Beckmann wrote: > Main focus should be in asynchronous multi master scenarios, as Carlos > pointed out. Everything else seems to be as specialization... Dimitry Sibiryakov will surely correct me, but I always thought that multi-master replication can hardly work without

Re: [Firebird-devel] Planning the post v3 development

2014-04-29 Thread Alex
On 04/28/2014 09:59 PM, Dmitry Yemanov wrote: >> A scheduler for firebird would totally eliminate my own use of custom >> applications tied to database events/time events. > Architecturally, Firebird database is not active without user > connections. This slightly changes with the LINGER support,

Re: [Firebird-devel] Planning the post v3 development

2014-04-28 Thread Alex
On 04/28/2014 06:29 PM, Carlos H. Cantu wrote: > 5) An embedded Firebird version for Android (even if only "basic" > server features could be available): > http://tracker.firebirdsql.org/browse/CORE-3885 Why do you treat it as post-v3? I plan to activate work with Android port after beta1. ---

Re: [Firebird-devel] Planning the post v3 development

2014-04-28 Thread Simonov Denis
Simonov Denis wrote: > > My list is as follows. > still would like to have implemented something safe from what it was postponed FB3: Groups of users and rights http://tracker.firebirdsql.org/browse/CORE-751 Ability to grant role to another role http://tracker.firebirdsql.org/browse/CORE-1815 A

Re: [Firebird-devel] Planning the post v3 development

2014-04-28 Thread Simonov Denis
Dmitry Yemanov wrote: >> 2. Standby can be based on nbackup >> http://tracker.firebirdsql.org/browse/CORE-2990 > > And it can be based on other solutions too. Why do you think this one is > the best? > I am not sure that is the best way to implement, but probably the easiest. Other ways could b

Re: [Firebird-devel] Planning the post v3 development

2014-04-28 Thread Carlos H. Cantu
ABS> I am pretty near and will do it with pleasure ! :) One less speaker at FDD so :P []s Carlos http://www.firebirdnews.org FireBase - http://www.FireBase.com.br ABS> Em 28/4/2014 18:21, Claudio Valderrama C. escreveu: >>> -Original Message- >>> From: Carlos H. Cantu [mailto:lis...@warm

Re: [Firebird-devel] Planning the post v3 development

2014-04-28 Thread Adriano dos Santos Fernandes
On 28-04-2014 19:02, Dimitry Sibiryakov wrote: > 28.04.2014 23:21, Claudio Valderrama C. wrote: >> I know people will feel outraged with my opinion, but anyway: make DDL >> operations atomic and immediate. Uncommitted DDL and DML working in unison >> with stable DB structure is a naive dream, perio

Re: [Firebird-devel] Planning the post v3 development

2014-04-28 Thread Alexandre Benson Smith
Em 28/4/2014 18:21, Claudio Valderrama C. escreveu: >> -Original Message- >> From: Carlos H. Cantu [mailto:lis...@warmboot.com.br] >> Sent: Lunes, 28 de Abril de 2014 12:30 >> >> DY> Thanks, but I seemed to explicitly state that plain >> wishlists don't >> DY> count. >> >> It seems that I a

Re: [Firebird-devel] Planning the post v3 development

2014-04-28 Thread Claudio Valderrama C.
> -Original Message- > From: Dimitry Sibiryakov [mailto:s...@ibphoenix.com] > Sent: Lunes, 28 de Abril de 2014 18:03 > > 28.04.2014 23:21, Claudio Valderrama C. wrote: > > I know people will feel outraged with my opinion, but > anyway: make DDL > > operations atomic and immediate. Uncomm

Re: [Firebird-devel] Planning the post v3 development

2014-04-28 Thread Thomas Beckmann
We are right now discussing this in our (new) company again. We implemented replication mechanisms similar to ibreplicator (and probably others) on our own, as probably did many people. Yes, having this kind of feature build in would be a big help. Current application design leads to more and more

Re: [Firebird-devel] Planning the post v3 development

2014-04-28 Thread Dimitry Sibiryakov
28.04.2014 23:21, Claudio Valderrama C. wrote: > I know people will feel outraged with my opinion, but anyway: make DDL > operations atomic and immediate. Uncommitted DDL and DML working in unison > with stable DB structure is a naive dream, period. I may be wrong as often, but AFAIU this dream ma

Re: [Firebird-devel] Planning the post v3 development

2014-04-28 Thread Claudio Valderrama C.
> -Original Message- > From: Dalton Calford [mailto:dalton.calf...@gmail.com] > Sent: Lunes, 28 de Abril de 2014 11:49 > > For example, you could put each schema into a remote > server/database, allowing for basic clustering (before you > jump on me, I know it is more complex than that,

Re: [Firebird-devel] Planning the post v3 development

2014-04-28 Thread Claudio Valderrama C.
> -Original Message- > From: Dmitry Yemanov [mailto:firebi...@yandex.ru] > Sent: Lunes, 28 de Abril de 2014 14:21 > > > 7) It is known that mixing DDL/DML in the same transaction can cause > > corruption in DBs. If this cannot be 100% fixed, I suggest to > > introduce some mechanism to de

Re: [Firebird-devel] Planning the post v3 development

2014-04-28 Thread Claudio Valderrama C.
> -Original Message- > From: Carlos H. Cantu [mailto:lis...@warmboot.com.br] > Sent: Lunes, 28 de Abril de 2014 12:30 > > DY> Thanks, but I seemed to explicitly state that plain > wishlists don't > DY> count. > > It seems that I also didn't understand that you wanted separated > message

Re: [Firebird-devel] Planning the post v3 development

2014-04-28 Thread Dalton Calford
Hi Dmitry, On 28 April 2014 13:59, Dmitry Yemanov wrote: > Isn't sqlite solid enough? ;-) At least for the tasks a tablet can run. > > Today's tablets blow away the server systems I used to run interbase on. In some cases, they are more powerful than some realtime firebird servers we have - don

Re: [Firebird-devel] Planning the post v3 development

2014-04-28 Thread Carlos H. Cantu
This is another one that I missed in my first list: Alter domain depedence problem when changing VAR(CHAR) size http://tracker.firebirdsql.org/browse/CORE-1427 Existing comments speaks for itself. []s Carlos H. Cantu www.FireBase.com.br - www.firebirdnews.org www.warmboot.com.br - blog.firebase.

Re: [Firebird-devel] Planning the post v3 development

2014-04-28 Thread Carlos H. Cantu
>> 2) I second Jesus Garcia request for native replication, since people at >> FDD and in FireBase's list are always claiming about the lack of such >> feature. DY> Replication is a too common word. What do they really need? Warm DY> standby? Hot standby? Sync replication? Async replication? Mult

Re: [Firebird-devel] Planning the post v3 development

2014-04-28 Thread Adriano dos Santos Fernandes
On 28/04/2014 15:30, Dmitry Yemanov wrote: >> 2. Add JAVA, .NET PROCEDURE and FUNCTION (not just C++) > You can do it in v3 as soon as someone writes the required interfacing > plugins (external engines). Volunteers anyone? > Java was done, but due to everything (Jaybird and Firebird APIs) being c

Re: [Firebird-devel] Planning the post v3 development

2014-04-28 Thread Dmitry Yemanov
28.04.2014 16:14, Simonov Denis wrote: > > optimizer > 1. Enable use MERGE / HASH JOIN for OUTER JOINs > 2. Performing EXISTS / IN SEMI JOIN as including using MERGE / HASH, and > NESTED LOOP using index > 3. HASH aggregation Add to an existing method using sorting I don't think the optimizer algo

Re: [Firebird-devel] Planning the post v3 development

2014-04-28 Thread Dmitry Yemanov
28.04.2014 18:37, Scott Morgan wrote: >> This message is the invitation to both project members and users who >> closely follow the development. > > UTC time zone support. Vital for international work and handy even for > general use. Nice reminder, although I don't think it's trivial to implemen

Re: [Firebird-devel] Planning the post v3 development

2014-04-28 Thread Dmitry Yemanov
28.04.2014 18:29, Carlos H. Cantu wrote: > > Here is my list: Arrrgh! :-) I've skipped the items I have nothing to say about (mostly due to lack of interest, sorry for fairness). > 2) I second Jesus Garcia request for native replication, since people at > FDD and in FireBase's list are always

Re: [Firebird-devel] Planning the post v3 development

2014-04-28 Thread Dmitry Yemanov
28.04.2014 19:48, Dalton Calford wrote: > Android and iOS native clients if not native servers, are extremely > important given the market growth in those areas and the lack of a good > solid database engine to work with. Isn't sqlite solid enough? ;-) At least for the tasks a tablet can run. >

Re: [Firebird-devel] Planning the post v3 development

2014-04-28 Thread Dmitry Yemanov
28.04.2014 20:30, Carlos H. Cantu wrote: > It seems that I also didn't understand that you wanted separated > messages for each feature discussion :( Well, we may start with the features intermixed inside this thread and then separate them for a more detailed discussion, if necessary. I just as

Re: [Firebird-devel] Planning the post v3 development

2014-04-28 Thread Carlos H. Cantu
DY> Thanks, but I seemed to explicitly state that plain wishlists don't DY> count. It seems that I also didn't understand that you wanted separated messages for each feature discussion :( []s Carlos http://www.firebirdnews.org FireBase - http://www.FireBase.com.br --

Re: [Firebird-devel] Planning the post v3 development

2014-04-28 Thread Dalton Calford
I will begin with the list of items I would like to see implemented. Object Names of at least 64 bytes -Core 749 Schemas plus associated objects (synonyms etc) - Core 738 Firebird native for Android - Core 3885 Scheduler for Firebird -

Re: [Firebird-devel] Planning the post v3 development

2014-04-28 Thread Mark Rotteveel
On 28-4-2014 16:29, Carlos H. Cantu wrote: > 8) Enhancement to the numerics calculations. The currently rule of > summing the scale of the types involved in muls/divs is very bad and > can easily cause overflow. Maybe FB could automatically truncate the > result to the maximum precision possible to

Re: [Firebird-devel] Planning the post v3 development

2014-04-28 Thread Carlos H. Cantu
Here is my list: 1) I still would like to see this implemented (without the need of external mechanisms), but I'm not sure if it would be possible at all: http://tracker.firebirdsql.org/browse/CORE-1738 2) I second Jesus Garcia request for native replication, since people at FDD and in FireBase's

Re: [Firebird-devel] Planning the post v3 development

2014-04-28 Thread Dmitry Yemanov
28.04.2014 16:14, Simonov Denis wrote: > > My list is as follows. Thanks, but I seemed to explicitly state that plain wishlists don't count. Choose top five from your list, start separate thread per feature and argue why we should prefer these features over other ones. Dmitry ---

Re: [Firebird-devel] Planning the post v3 development

2014-04-28 Thread Scott Morgan
On 24/04/14 11:19, Dmitry Yemanov wrote: > This message is the invitation to both project members and users who > closely follow the development. UTC time zone support. Vital for international work and handy even for general use. It doesn't look like v3 has it (are we sure v3 can't catch this be

Re: [Firebird-devel] Planning the post v3 development

2014-04-28 Thread Dimitry Sibiryakov
28.04.2014 14:14, Simonov Denis wrote: > 3. Built as a plug -row replication . The standard delivery enable > replication between servers firebird. For other servers, you can write > your own plugin. I'm sleeping on it. > Create a bunch of triggers to support replication is not the nicest way.

Re: [Firebird-devel] Planning the post v3 development

2014-04-28 Thread Simonov Denis
My list is as follows. optimizer 1. Enable use MERGE / HASH JOIN for OUTER JOINs 2. Performing EXISTS / IN SEMI JOIN as including using MERGE / HASH, and NESTED LOOP using index 3. HASH aggregation Add to an existing method using sorting 4. Conditional INDEX ONLY SCAN as in Postgresql (dimitr s

[Firebird-devel] Planning the post v3 development

2014-04-24 Thread Dmitry Yemanov
All, We're getting closer to the v3.0 feature freeze which is going to happen this summer. Everything roadmapped for v3 but not implemented before the deadline will be postponed. The next-after-v3 release is likely to incorporate most of the postponed features, but there may be new features as