> My idea was, in fact, to create a set of procedures to use( Insert, Select,
> etc ) for
> "basics" needs and use SQL directly only when _strictly_ necessary.
> Is this approach correct or you can point to other( better ) ways to make
> things faster with FB?
I nearly always use Add/Edit/Delete/Etc Stored procedures for 'enities' in
This is not neccasarlly beacuse it is faster, than SQL on the client (they
are certainly not slower), but because it adds a layer of abstraction on top
of the tables. This means an 'Add_Customer' stored procedure could add a
record to several tables (Customer, Address, etc.), and you would not have to
bother about FK's on the client. It also means you can change the structure
of you DB (e.g. spliting the Customer table into several), without changing,
or even recompiling the client.
6:37pm up 18 days, 1:03, 1 user, load average: 0.21, 0.07, 0.03