Hi Amarendran,
If you analyse the database, then you have to define it first using an SQL
script, or something. We felt the need for a tool that, taking a set of
classes, created the tables for us and filled them with the objects.
For example, if we have
public class Nested
{
private int a;
}
and
public class Container
{
private String primaryKey;
private int b;
private Nested nested;
}
the database layer should create two tables, add a foreign key to Nested,
and map any instances to database tables using the "primaryKey" field.
Un saludo,
Alex.
> -----Mensaje original-----
> De: Amarendran Subramanian [mailto:[EMAIL PROTECTED]]
> Enviado el: miércoles 24 de abril de 2002 16:10
> Para: 'Jakarta General List'
> Asunto: AW: Subproject Proposal - crossdb
>
>
> >Torque is nice, but you have to specify the database first
> in the XML.
> >Usually, I prefer to code Java instead of XML. If it was the
> other way
>
> i solved this by writing a little tools that analyzes the database
> and generates the xml for me. but this is for my own tool not
> for torque ;)
> it also reads the "foreign keys" and creates the right
> references in the
> mapping xml. additional stuff is done in a seperate
> "manual.xml". works fine
> !
>
> --amar
>
> --
> To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
>
