Hi,

If i can say my proposition. Then my favourite is transaction id as int64. Many 
times i must spend weeks to to overcome this limit in projects. Ok, then this 
projects are "better and faster" but cost is also bigger and bigger...

When i think about web develooment i also have problem with this limit

Regards,
Karol Bieniaszewski

----- Reply message -----
Od: "Dalton Calford" <dalton.calf...@gmail.com>
Do: "For discussion among Firebird Developers" 
<firebird-devel@lists.sourceforge.net>
Temat: [Firebird-devel] Planning the post v3 development
Data: pon., kwi 28, 2014 17:48
I will begin with the list of items I would like to see implemented.
Object Names of at least 64 bytes -                        Core 749Schemas plus 
associated objects (synonyms etc) - Core 738
Firebird native for Android  -                                   Core 
3885Scheduler for Firebird -                                           Core 
1613Database Links -                                                    Core 776

The first two items are so obvious, I can not think of anyone who would argue 
against them.   I will defend those items, but won't in this particular 
email.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.   
A scheduler for firebird would totally eliminate my own use of custom 
applications tied to database events/time events.   I am sure that I am not the 
only person who has had to develop around the lack of a scheduler/event handler 
in firebird that runs in its own transaction/user space.
Database links, which would require the Object names and schema support, would 
allow for developers to implement many features manually that are now in the 
wish list catagory.   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, I have implemented alot of this via other code).  
 You could easily develop your own replication systems.    One feature change, 
could be used to implement so many other requested features as well as 
providing a tool so that developers/users could come up with new ways of using 
firebird that are not even imagined now. 

best regards
Dalton



On 28 April 2014 10:50, Dmitry Yemanov <firebi...@yandex.ru> wrote:

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





------------------------------------------------------------------------------

"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE

Instantly run your Selenium tests across 300+ browser/OS combos.  Get

unparalleled scalability from the best Selenium testing platform available.

Simple to use. Nothing to install. Get started now for free."

http://p.sf.net/sfu/SauceLabs

Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.  Get 
unparalleled scalability from the best Selenium testing platform available.
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

Reply via email to