Thanks Andrus for the information.
About switching DB, my idea was more of keeping the same object model
for any new DB schema (& technology too). For example, a generic
import-export class in your application that you need to map to
different customer's specific data table (also using different DB
engines - ok, covered with the DB Adapter). In the end you want to keep
the same import-export class interface but only adapt the mapping
between your class and the different customers DB schemas.
I will give it a try!
Colin.
Andrus Adamchik wrote:
> Hi Colin,
>
> Cayenne will totally support all these requirements.
>
> * Reverse-engineering an existing database and creating an object layer
> usually takes just a few minutes using the Modeler (of course while you
> are still learning it will be longer than that).
>
> * Mapping model that you get as a result of reverse engineering can be
> used to generate a first cut of your peristent objects. You then add
> custom functionality to these objects as you go.
>
> * When the mapping evolves over time you can still use class generator to
> update peristent properties of your objects, keeping Java and DB in sync.
>
> * Switching DB (say from DB2 to Postgres) is trivial... You just change
> something called "DB Adapter", no need to even modify the mapping.
>
> Try the tutorials that come with Cayenne
> (http://objectstyle.org/cayenne/userguide/quickstart/index.html) - they
> discuss most of these steps.
>
> Good luck!
> Andrus
>
>
>>Hi,
>>
>>I am totally new to Cayenne and I am currently trying to find the best
>>tool to use to integrate my Java app with an *existing* DB. Any comments
>> & pointers that will help me understand if Cayenne is the right tool
>>for me will be very much appreciated!
>>
>>At this stage my need is quite simple (and deadline is short ;) : I need
>> to bind my application to a few tables of an existing (DB2) database, I
>> want to work with classes and abstract the object to table mapping. In
>>one table I will typically query for rows using some criteria and in the
>> other I will insert new rows. That's it.
>>
>>In the future, I will eventually need to bing my application to
>>different databases with different schemas but I would like to keep the
>>same object interface from my application perspective and only have to
>>modify or regenerate the actual mapping necessary for the new database.
>>
>>Is Cayenne right for me?
>>
>>Colin.
>
>
>
This archive was generated by hypermail 2.0.0 : Tue Apr 26 2005 - 14:31:35 EDT