Existing DB Mapping Error

Question

I'm now trying to map a class with an existing db table. Firstly, here is
my package.jdo
<?xml version="1.0"?>
<jdo>
     <package name="test">
          <class name="Testclass">
               <extension vendor-name="kodo" key="table" value="test_table"/>
               <extension vendor-name="kodo" key="lock-column" value="none"/>
               <extension vendor-name="kodo" key="pk-column" value="test_id"/>
               <extension vendor-name="kodo" key="class-column" value="none"/>
               <field name="testField">
                    <extension vendor-name="kodo" key="data-column" value="test_field"/>
               </field>
          </class>
     </package>
</jdo>
And this is the error that I get.
javax.jdo.JDOUserException: No database mapping was found for type "class
test.Testclass"; all persistent types must be registered in the database;
this is done automatically through the SchemaTool.
     at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.getClassMapping(JDBCStoreManager.java:674)
     at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCExpressionFactory.(JDBCExpressionFactory.java:49)
     at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCQuery.getExpressionFactory(JDBCQuery.java:178)
Ideas?

Answer 1

Hi,
I think we're getting somewhere now:)
It appears to be running the query (unsuccessfully). Here is my data
test_column_a test_column_b test_column_c
1 andrew 12
2 row2 33
This is my query.
public Collection getTests(String sFilter, PersistenceManager aPM) {
          Extent anExtent = aPM.getExtent(Test.class, true);
          Query aQry = aPM.newQuery(Test.class, anExtent, sFilter);
          Collection aTestList = (Collection) aQry.execute();
          System.out.print("The number of test items is: ");
          System.out.println(aTestList.size());
          return aTestList;
I call this via:
Test aTest = new Test();
aTest.getTests("", JDOFactory.getPersistenceManager());
The logging in the getTests() method says the number of items in the
collection returned from the query is 0. (I'm expecting 2).
I've also passed null as the filter when creating the newQuery().
So I'm getting close...
Patrick Linskey wrote:
[email protected] (Andrew) writes:
I'm 99% certain they are iTestColumnA, B and C.
iTestColumnA is the primary key, and my xml file looks exactly like the
first one you've
listed. I initially didn't have the iTestColumnA in my class file (I think
I read in the
documents that it shouldn't be), but I got an error when running the
enhancer so I put
it back in.
Looking at the second xml listing, I've tried the same type of thing
there, and I got an
error with that as well. I will try these things again tomorrow though,
and let you know
the results. Oh, one point I just noticed is that I haven't mentioned an
identity type!
I've looked through the documents and didn't find how this was done, but I
see it now in
your listing, perhaps that will help solve the problems.
All the primary keys are handled by me, so unique generation etc is fine
(we're using
oracle and I dont' know the details, but as long as I know the difference
it will be
handled).
Thanks for your help, I'll let you know how I go tomorrow.
Andrew
BTW, note that my XML for application identity was incorrect. I forgot
to specify an app id oid class. Something like this would probably be
better:
<?xml version="1.0"?>
<jdo>
<package name="test">
<class name="Testclass" identity-type="application"objectid-class="TestKey">
<extension vendor-name="kodo" key="table" value="TEST"/>
<extension vendor-name="kodo" key="lock-column" value="none"/>
Note that we provide a tool to simplify the process of generating
application id keys. Run 'java
com.solarmetric.kodo.tools.appid.ApplicationIDTool' on your .jdo files
to generate template app id classes.
-Patrick>>
Patrick Linskey wrote:
Andrew,
Based on the error that you are seeing and on your class, I bet that the
fields are actually 'iTestA', 'sTestB', and 'iTestC'.
Is 'iTestA' the primary key field? Also, did you specify application
identity or data store identity in your XML metadata?
I'm guessing that your XML should look like one of the two following
examples. The first uses datastore identity; the second application
identity.
In the first case, I have removed the iTestA field. This field
should also be removed from your class file. This is because I'm
guessing that the test_column_a column is the primary key column, and
when using data store identity, you cannot map the pk to a field in your
class.
<?xml version="1.0"?>
<jdo>
<package name="test">
<class name="Testclass" identity-type="datastore">
<extension vendor-name="kodo" key="table" value="TEST"/>
<extension vendor-name="kodo" key="lock-column" value="none"/>
<extension vendor-name="kodo" key="pk-column" value="test_column_a"/>
<extension vendor-name="kodo" key="class-column" value="none"/>
<field name="sTestB">
<extension vendor-name="kodo" key="data-column"
value="test_column_b"/>
</field>
<field name="iTestC">
<extension vendor-name="kodo" key="data-column"value="test_column_c"/>
</field>
</class>
</package>
</jdo>
In the second case, the iTestA field is in both the Java class and the
metadata. It is your responsibility to ensure that this field be given a
unique id, as it is the primary key, and this configuration uses
application-controlled identity.
<?xml version="1.0"?>
<jdo>
<package name="test">
<class name="Testclass" identity-type="application">
<extension vendor-name="kodo" key="table" value="TEST"/>
<extension vendor-name="kodo" key="lock-column" value="none"/>
<extension vendor-name="kodo" key="class-column" value="none"/>
<field name="iTestA" primary-key="true">
<extension vendor-name="kodo" key="data-column"
value="test_column_a"/>
</field>
<field name="sTestB">
<extension vendor-name="kodo" key="data-column"value="test_column_b"/>
</field>
<field name="iTestC">
<extension vendor-name="kodo" key="data-column"value="test_column_c"/>
</field>
</class>
</package>
</jdo>
-Patrick
[email protected] (Andrew) writes:
Hi, Something like this (I'm at home now, but this is pretty close):
public class Test {
public Test() {
super();
// This bit isn't exact, but just imagine it's the tutorial
example,
no
//restrictions.
public Collection getTestList(String sFilter, PersistenceManager
pm) {
// Copied out of the tutorial....
Extent e = pm.getExtent(Test.class, sFilter);
Collection aTestList = aQry.execute();
return aTestList;
private int iTestColumnA = 0;
private String sTestColumnB = null;
private int iTestColumnC = 0;
Patrick Linskey wrote:
[email protected] (Andrew) writes:
I'm just working with a small test table at the moment with 1
primary
key
column and 2 other columns. When the JDO tries to access the
database,
this is an error I get.
javax.jdo.JDODataStoreException: [SQL=SELECT t0.test_column_a,t0.ITESTAX,> > > > > > t0.test_column_c, t0.test_column_b FROM TEST t0 ORA-00904: invalidcolumn
name
Now, I'm not sure where this ITESTAX column is coming from??
Andrew,
What does your test class look like?
-Patrick
Patrick Linskey [email protected]
SolarMetric Inc. http://www.solarmetric.com
Patrick Linskey [email protected]
SolarMetric Inc. http://www.solarmetric.com
Patrick Linskey [email protected]
SolarMetric Inc. http://www.solarmetric.com