On Tue, Dec 2, 2014 at 10:53 AM, David Welton <
davidn...@gmail.com> wrote:
>> I'm the one who opened the issue.
>> The worst thing is that while you can insert a record with arbitrary key
>> into a table, you won't be able to delete it later.
>> So even if you create an another function for the counter the problem will
>> still exist.
>>
>> Imo if you do delete_counter you will have to create a create_counter as
>> well, so that all this 'counter' feature would be an on-demand one. But it
>> could be more complicated than this - a record can have multiple counters,
>> and there's an autogeneration of counter access functions in model
>> definition with -counter(foo_counter) module attribute.
>
> Ah yes, I see... the boss_db functions are not so bad, but the
> auto-generated stuff looks quite messy.
>
> Does anyone use it?
This stuff seems like a mess, and is breaking transactions on
Postgres. How many people use them? How do you use them? It might
be nice to back them out into something less obtrusive.
--
David N. Welton
http://www.welton.it/davidw/
http://www.dedasys.com/