Hi Massimo,
If dict access is overhead, we can use direct variable assignments (as
mentioned in my second approach), e.g. db.cls_table (and db.cls_rows,
db.cls_row, ...).
The why: I need to do lots of processing with these DAL objects (DAL, Table,
Field, Set, Rows, Reference, Row, etc.) and it
Let me add I am worried about concurrency issues with this approach.
Where would subclassing be done? Cannot be done in models.
On Aug 19, 9:43 am, Carlos wrote:
> Hi all,
>
> Can I propose the following in order to being able to subclass DAL classes?.
>
> We can currently subclass DAL in our own
This means one dict lookup for every instance. This will results in an
lots of work and possible overhead.
I would like to see a case about why this is necessary.
I am still not convinced there is any need to subclass dal. I have
been wrong before.
massimo
On Aug 19, 9:43 am, Carlos wrote:
> Hi
3 matches
Mail list logo
