On Apr 18, 2007, at 5:25 PM, Carl Karsten wrote:

>> If you need to set your pk differently as by the standard,
>> you should do this yourself in your bizobj.
>
> Sounds like a data thing to me.  If I change PK formulas or db  
> engines, I should
> not have to change my BO code.

        Most database stuff is set in the bizobj via pass-through  
properties, since bizobjs must create and manage their cursors. So  
yes, you may have to change some of the code in your bizobj if your  
backend changes; just not any of the 'business logic'.

> BO or otherwise,  I am assuming all of the client side PK code we  
> are talking
> about can be coded fairly abstractly so that you just specify a few  
> parameters
> for each instance of a PK that needs to be addressed.
>
> Perhaps a PK manager class that can be added to the db engines that  
> might use
> it?   I don't think it should be part of all db classes, given that  
> some db's
> have such different ways of handling it.  Maybe we need an abstract  
> class that
> just defines the interface, and 2 or 3 subclasses of that that  
> implement the
> various techniques.  Make that 4 or 5, so that MsSql can have one  
> for each of
> it's attempts.   Not really sure how these classes would actually  
> be used.

        Before everyone starts going off in 10 different directions, please  
stop and take a deep breath.

        The only issue being discussed right now is adding code in  
dbPostgreSQL.py to return the last PK sequence value when the PK is a  
basic sequence type. Let's please focus on that instead of getting  
bogged down in abstract database design issues.

        Second, we've already set adoption of SQLAlchemy to handle backend  
abstraction as a goal. Instead of wasting time on all these esoteric  
and unnecessary class designs, why not start investigating what it  
would take to incorporate SQLAlchemy into Dabo, replacing the  
dBackend stuff? At least that effort will be useful.

-- Ed Leafe
-- http://leafe.com
-- http://dabodev.com




_______________________________________________
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/dabo-users/[EMAIL PROTECTED]

Reply via email to