Sounds good to me. I think this is out of scope for this phase, but I'll ask anyway... Does this mean that the Table maps structures can/will be initialized at once, ala Henning's old patch that was never rolled into the main line? I've been meaning to rework that into the current version to support some import/export code but haven't found the time.
> -----Original Message----- > From: Thomas Fischer [mailto:[EMAIL PROTECTED] > Sent: Saturday, April 01, 2006 7:28 AM > To: [email protected] > Subject: Reworking of runtime database information structure > > > Hi, > > In the present state, the information the runtime is keeping > about the > databases it acesses is not organized cleanly. At the moment, > Torque keeps > different Maps of database adapters, of database maps, of data source > factories etc. Also, things are hidden where they are not > expected: in my > eyes it makes no sense to keep the id broker in the database > map, or the > schema name in the data source factory. > > I'd therefore propose to change the internal representation > of the data > such that there is one top level object per database, called > "Database", > which keeps all the information the runtime has about a > certain database. > Specifically, it would provide access to the database map, > the data source > factory, the database adapter, the id broker, the id > generators, and the > schema name. > > To soften the transition, the id broker, the id generators, and the > schema name would stay at their current places (database map and data > source factory), but the acessors would be deprecated. After the next > release, the references themselves would be moved to the > database map and > the deprecated methods would be removed. > > Please send objections, requests for clarifications etc in > the next few > days, otherwise I'll simply do it. > > Thomas > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > Duke CE Privacy Statement Please be advised that this e-mail and any files transmitted with it are confidential communication or may otherwise be privileged or confidential and are intended solely for the individual or entity to whom they are addressed. If you are not the intended recipient you may not rely on the contents of this email or any attachments, and we ask that you please not read, copy or retransmit this communication, but reply to the sender and destroy the email, its contents, and all copies thereof immediately. Any unauthorized dissemination, distribution or copying of this communication is strictly prohibited. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
