It's incredible small the number of custom aggregate functions overall in
projects, nor I think the focus of this feature is to make others DBMS
users migrate to Firebird due to it, specially considering that their
underlying mechanism are very different than what Firebird has.

The focus is to have a feature well integrated with Firebird others
features. That feature is going to be used by advanced Firebird users, we
known.

It's a very rarely used (develop the routine) but with high benefits
(usage).


Adriano

On Sat, Sep 29, 2018, 09:23 Dimitry Sibiryakov <s...@ibphoenix.com> wrote:

> 29.09.2018 14:02, Adriano dos Santos Fernandes wrote:
> > My propose is to use the same elegant concept for aggregation. Your
> example seems much
> > more confusing. It makes sense thinking on interfaces, but very
> different from Firebird
> > way of doing things.
>
>    Yes, but being similar to others (PG or Oracle) is a good thing for
> migration.
>
>
> --
>    WBR, SD.
>
>
> Firebird-Devel mailing list, web interface at
> https://lists.sourceforge.net/lists/listinfo/firebird-devel
>
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

Reply via email to