Ok, I think I understand now.   The tables I have aren't prefixed with "ISIS_".

For example the tables I have are called Payment_Arc,  Payable, Disbursement
And they all have a common field named pym_id and other fields.

I'll look into the AbstractAutoMapper.


Jason Richardson



-----Original Message-----
From: Kevin Meyer - KMZ [mailto:[email protected]] 
Sent: Friday, December 16, 2011 9:33 AM
To: [email protected]
Subject: Re: Questions regarding the quickstart app and creating a Proof of 
Concept

Hi Jason,

> I was able to connect.    Is there a way to disable the table creation 
> feature of isis?

Umm.. that's kind of core to the SQL Objectstore.

It only creates tables that it doesn't find - and turning that off will 
guarantee failure.

If you need it to work with existing tables, all you need to do is ensure 
that the existing table name matches the looked-for name and that the 
structure is consistent. To quote the documentation:

1.4.1.2. Domain Tables

Only the "class" part of the package name is used. Thus a domain 
class called "some.package.Client", will be mapped onto a table 
"ISIS_CLIENT".




The SQL-OS at the moment does not detect schema mis-match, it 
only checks to see if the table exists.

There currently isn't a way of specifying a table name for a class, to 
override the default. This feature can be added, by intercepting 
"getTableNameFromSpecification" in the AbstractAutoMapper.



Regards,
Kevin


> 
> 
> Jason Richardson
> National Payments Service (NPS) Technical Lead



Reply via email to