You are viewing a plain text version of this content. The canonical link for it is here.
Posted to torque-dev@db.apache.org by Thomas Fischer <tf...@apache.org> on 2006/04/01 14:28:02 UTC
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: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org
Re: Reworking of runtime database information structure
Posted by "Clemens Utschig - Utschig (Oracle)" <cl...@oracle.com>.
Thomas,
even that I haven't had no chance for months to look into the features,
but this sounds pretty worth :-) (and like the toplink approach :-D)
+1
/clemens
Thomas Fischer wrote:
> 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: torque-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: torque-dev-help@db.apache.org
>
--
+-----------------------------------+
| Clemens Utschig - Utschig |
| Oracle SOA Product Management |
| |
| >work: +1 (650) 506-3629 |
| >cell: +1 (650) 703-6357 |
| >mail: clemens.utschig@oracle.com |
| >blog: clemensblog.blogspot.com |
+-----------------------------------+
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org
Re: Reworking of runtime database information structure
Posted by Thomas Vandahl <th...@tewisoft.de>.
Thomas Fischer wrote:
> This is something I'd see as a different (but related) subject. I did not
> intend to touch this in the first step, I only wanted to move accessors for
> a few objects and get the initialisation process to work with the new
> structure. But it may be a basis for further changes.
Yes, I see. My point was, just try to keep this option open.
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org
Re: Reworking of runtime database information structure
Posted by Thomas Fischer <fi...@seitenbau.net>.
Thomas Vandahl <tv...@apache.org> schrieb am 02.04.2006 15:31:24:
> ... In some ancient ToDo-list
> there was something about making the generated classes independent from
> the database adapter. If you do anything, please keep this aim in mind.
>
This is something I'd see as a different (but related) subject. I did not
intend to touch this in the first step, I only wanted to move accessors for
a few objects and get the initialisation process to work with the new
structure. But it may be a basis for further changes.
Thomas
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org
Re: Reworking of runtime database information structure
Posted by Thomas Vandahl <tv...@apache.org>.
Thomas Fischer wrote:
> Please send objections, requests for clarifications etc in the next few
> days, otherwise I'll simply do it.
I'm definitely +1 on this one in any case. In some ancient ToDo-list
there was something about making the generated classes independent from
the database adapter. If you do anything, please keep this aim in mind.
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org