> oops - 7144
>
> OK - but I think it is at the moment. Why shouldn't it be? Yes we will
> have to change a number of supporting programs but if it makes the
> framework perform better and is much more stable shouldn't that be
> required?
>
> ClassDesigner, AppWizard and a few other areas will require changes. But it
> all can be done. I believe all the supported databases provide enough
> information to automate the task of creating the data structures for the
> bizobjs. I'm not sure about SQLite???
>
> I may be completely wrong here - but it seems like a lot of effort (over the
> years) has been directed at determining the simplest of things like a
> python data type. The framework could assume that the python data type was
> present from the start - if the data structure was present. I'm not sure
> how this would effect dynamic SQL statements or the use of datasets. But
> to me all this effort to determine a python datatype should signal that we
> are doing something wrong.
>
> Johnf
The following code worked in the past and causes an issue in the framework
today.
self.addField("extract(year from age(born)) as studentage")
(BTW not a very good field name when it returns a year)
You probably can guess from the description that it returns an int. But how
would the framework know without the use of a data structure - it guesses (or
it use too). This type of statement of course can NOT be automated. But I
had to modify the bizobj to add the statement - so adding additional info in
the data structure is not a lot to ask of the developer. I think the same
holds true for virtual fields.
Hey Paul if by chance you have written code to automate the build of a data
structure would you mind passing it on?
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/2088505.ngZeTN6LeN@linux-12
