18.03.2014 13:30, Alex wrote: > The main reason is an ability to delete provider's object better sooner > than later. > - yvalve object is tiny and consumes very low resources > - provider's object may be relatively big
But they both are on client side. As you said, client's memory consumption is client's problem. > - and as a last '+' we can unload provider after nullifying next pointer It is rather '-'. Consider application that attach to a db, do something and then detach and start again in the loop. It is not wise to unload-load provider on each loop. -- WBR, SD. ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
