On Friday, May 18, 2012 09:13:00 AM Paul McNett wrote:
> I'm confused about several things, but let's start with something we can be
> explicit about.
>
> On 5/18/12 7:24 AM, John Fabiani wrote:
> > oops - 7144
>
> Ok, so r7144 is the *last* revision that works as you expected? I'm confused
> because the only thing r7145 does is "remove debugging output" from
> ide/ClassDesigner.py.
>
> Paul
Maybe I went about it wrong in my attempt to explain the general problem. I
don't care about the issue I'm having with forms at the moment. In fact I
posted a fix that works for me.
"What I think should happen is we should require data structures be defined.
"
I think you have been on the right track for years. Using data structures
solves several of the issues I've run into over the years. I started thinking
about this about a month ago when I asked a question on how the framework
worked with DataStructure() (I didn't get an answer).
I believe if the data structure is required many of the issues that surround
the bizobj may start to disappear. Example:
self.addField("extract(year from age(born)) as studentage")
self.addField("esenroll.pkid::text", alias= 'pkidtext')
self.addField("escourse.name_1 as course_name")
All of the above are legal. But each presents a problem when defining the
python datatype. But if the developer defined the type - not an issue.
Tell me why you started defining data structures!
Johnf
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
Searchable Archives: http://leafe.com/archives/search/dabo-dev
This message: http://leafe.com/archives/byMID/1557220.b58IHvhDNA@linux-12
