On May 22, 2010, at 9:55 PM, Chris C. wrote:
> I think I'm keeping up with you so far.
>
> So a record in the dataset returned by a Dabo business object is roughly
> equivalent to one instance of an object returned by an ORM?
Yes and no. Yes in that it represents the same data, but no in that you
would never work with it that way.
> 1) How does one handle this in the code if the code is expecting objects and
> attributes?
I don't know what you mean by "the code is expecting objects and
attributes". Dabo's data binding works directly with the business objects.
> 1) Can a Dabo business object return any set of records that could be
> returned by a SQL query,
Yes. You define the query, either through explicit SQL or by using the
Query Builder methods.
> and records in the dataset have to be "converted"
> into objects and object attributes?
No. You only deal with the dataset indirectly; your code would only
"talk" to the bizobj.
> 2) And/or does that mean that ORM's are more suited to OOP programs and Dabo
> is more suited to procedural programs?
Not at all. There is nothing procedural about Dabo or datasets; we use
business objects, application objects, UI objects, etc.
> I'm sure my question give away that, as a beginner programmer, I don't
> understand a lot of what's going to happen as I get into this process. But
> I'm trying find the easiest way to get my program up and running, but with
> an aim toward maintainability and future upgradability too.
Please read through the tutorial; it has an excellent overview of how
you work with data in Dabo. After you read through that, please let me know if
anything is still not clear.
http://dabodev.com/pycon_tutorial
-- Ed Leafe
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message:
http://leafe.com/archives/byMID/[email protected]
