> > The functions are there to prevent the same queries coming up over and
>
> On first reading, I took the above to mean "the same [SQL] queries"
> being repeated; at my second read, it seemed to refer to FAQs.
> Now, I am not sure which, but the two issues intertwine.
>
I meant the first reading
Hello Erik and all,
On Sat, Aug 15, 2015 at 04:48:22PM +0200, Erik Huelsmann wrote:
> The functions are there to prevent the same queries coming up over and
On first reading, I took the above to mean "the same [SQL] queries"
being repeated; at my second read, it seemed to refer to FAQs.
Now, I a
Hi Rob,
On Sat, Aug 15, 2015 at 4:36 PM, R. Ransbottom wrote:
> Reading here, LSMB is to be based on pg/sql functions.
> The idea is to cast the system in stone (functions) and
> stop redundant or brittle sql popping up.
The functions are there to prevent the same queries coming up over and
ov
Reading here, LSMB is to be based on pg/sql functions.
The idea is to cast the system in stone (functions) and
stop redundant or brittle sql popping up. This rubs me
wrong a bit; using sql to analyse and make bulk changes
is one of the attractions of LSMB. The wrong may be that
I am used to my
