> Just because you guys may not see a need for it doesn't mean it's not
> needed.
> If you don't need it, don't use it, but other databases have it
> because there is a need for it and it's very useful.
>

I changed SQL Server for FB some years ago. At that time, i used
commits and rollbacks inside stored procedures, and at the first
moment i missed this feature in FB.

Today i see there are other ways to achieve the same behavior and i
don't see any big benefit to have this feature implemented. I'm not
saying it's useless. Just that it probably doesn't worth to implement it.

Regards.