in fact, some of us don't even know what counters are needed for ;-) On Wednesday, December 17, 2014 12:53:20 PM UTC+2, David Welton wrote: > > On Tue, Dec 2, 2014 at 10:53 AM, David Welton <[email protected]> > 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/ >
-- You received this message because you are subscribed to the Google Groups "ChicagoBoss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at http://groups.google.com/group/chicagoboss. To view this discussion on the web visit https://groups.google.com/d/msgid/chicagoboss/9ab555e2-23f3-4434-89d3-b76ba8b03b5f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
