This has turned into a meta-discussion, but I get the criticism (I think it is exaggerated, though...). Yes, I should read more about new DAL features, and I will, I just assumed that creative-usage-patters would not necessarily be as well documented as the bare features themselves, and that some people here - you maybe - would be more proficient than me regarding such creative usage-patterns that I might not think of. Just pointing out features of the DAL, is insufficient, without some toy-examples...
Perhaps it is my way of asking for help that you don't like, but you should at least admit that I had to go quite far just to convince you that my proposal is even "potentially" beneficial at all... We never even got to the point in which you gave me concrete alternative usage-patterns of the DAL - you consistently reject the proposition I present in principal. This is not helping. As for use-cases, I wanted you to see someone else explain things better then me - so I gave you some links. It is an almost three-hour lecture, so I pin-pointed specific minutes that I think where relevant, and gave time-coded links. Is that too much to ask? As for the other 50min lecture, I could narrow it down even more, but the point was that I felt that there was a mismatch in perception of philosophies between how you perceive SQLA's philosophy (based on your prior perception of ORMs in general), and the actual philosophy of SQLA, as it's creator is presenting it, and I wanted you to see that. As for API design, I am a user of web2py. Meaning, I AM a developer, but a developer of applications - not frameworks - there is a crucial distinction to make here. You wouldn't expect users of your framework to suggest concrete-implementations of infrastructure-improvements, would you? I am not expecting any of you to figure out my business requirements (I have no idea what gave you that impression...). I am expecting a helping hand of "expertise" regarding existing usage-patterns, as well as have an architectural/abstract discussion of a proposed additional-abstraction-layer, that "might" require proficiency in the inner-workings of the DAL, which is beyond my expertise. How would you suggest I should ask for such a thing? On Mon, Apr 29, 2013 at 1:47 PM, Niphlod <[email protected]> wrote: > > > On Monday, April 29, 2013 11:47:41 AM UTC+2, Arnon Marcus wrote: >> >> >> they don't build up magically by default (though the cascade parameter >>> allows the same flexibility as the one present in your backend) but given >>> that all the six "important" events are available and fired accordingly, >>> you can hook up whatever business logic you like. >>> >>> >> >> That answer is too vague for me... Can you elaborate? >> What cascade-parameter? What do you mean by "your backend"? What "six >> important" event? >> Does this answer my questions? >> > > So, a small recap. Don't take this in the wrong way but: > - I need to watch 2 hours of presentations that you found interesting to > be able to reply > - you expect "us" (by us I mean web2py developers) to figure out YOUR > business requirement because you liked a presentation about SQLA and you > want that feature(s) on top of DAL, without providing your use-case and the > possible benefits > - you expect web2py developers to come up with an API that even you can't > figure out > - you don't want to raise a finger providing a real usecase scenario cause > "you're a user, not a developer" > - you can't take a look at the current DAL implementation to see what are > the proposed solutions to your (ATM imaginary) problems > If these are the requirements of your discussion-environment, don't be > surprised if nobody provides code for you. > > Docs are there. Given that you're using time to look at other python > modules/packages, at least be documented on what you want to use as a > starting-point (DAL) for comparisons. > > > -- > > --- > You received this message because you are subscribed to a topic in the > Google Groups "web2py-users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/web2py/vyOEkUeCNj4/unsubscribe?hl=en. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
