Ed Leafe wrote: > On Mar 18, 2007, at 8:19 PM, Carl Karsten wrote: > >> Host/user/password is easy - 3 textboxes, pass the values through >> the BO to the >> CO. that gets me the connection and cursor object I need. >> >> for each DB the user has rights to - that seems pretty DB stuff, so >> I guess add >> a method to a custom cursor class that returns a list of dbs. > > Not exactly. If you're going to be digging into the structure of > databases, you have to get a little "close to the silicon" than the > standard backend-agnostic cursor class. In your afterInit() of the > bizobj, re-define its self.dbapiCursorClass to be a custom subclass > of the default class that has the methods you need to query the > backend for database permissions and such. >
how is that not a custom cursor class? I am not really seeing a difference between what I described and what you described, other than there is a bit of implementation detail that I don't understand: sounds like the re-define happens at run time - why not do that at design time? >> but returns the list to what? this is where I get lost. which >> normaly means I >> need some BO code. my guess is I need a for loop in some BO >> method. maybe the >> same BO methon that I passed the host/u/pw to? I could cram >> 'everything' into >> that method but that doesn't sound very elegant. > > I'm not sure exactly what you're trying to accomplish, but it sounds > like you want to have code to determine the data the user can access, > and then execute queries within that database. IOW, more of a > database manager than a data manager. Is that close? yeah, database tester even, given that it doesn't actually change anything, which I would think a manager would do. It isn't the basic CURD kinda app, but I think I can squeeze it into the dabo.:) Carl K _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
