Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>From the document you cited:</p> <p><a href="http://www.datanucleus.org/products/datanucleus/jdo/annotations.html#Column" rel="nofollow">http://www.datanucleus.org/products/datanucleus/jdo/annotations.html#Column</a></p> <ul> <li><p>jdbcType String ORM : JDBC Type to use for persisting into this column </p></li> <li><p>sqlType String ORM : SQL Type to use for persisting into this column </p></li> </ul> <p>In general, JDBC should provide a mapping to the underlying SQL type, and you should code your JDO implementation to the exposed JDBC type.</p> <p>This reference gives one example of where the distinction could be significant:</p> <ul> <li><a href="http://osdir.com/ml/apache.db.jdo.devel/2005-07/msg00139.html" rel="nofollow">http://osdir.com/ml/apache.db.jdo.devel/2005-07/msg00139.html</a></li> </ul> <p>Here's some more documentation that might help:</p> <ul> <li><a href="http://java.sun.com/developer/technicalArticles/J2SE/jdo/" rel="nofollow">http://java.sun.com/developer/technicalArticles/J2SE/jdo/</a></li> </ul> <blockquote> <p>Q: So JDBC types are like standard data types while SQL types are types specific to each datastore?</p> </blockquote> <p>To answer you're question, here's what the JDO 3.0 Specification says, Section 18.4, Element column:</p> <blockquote> <p><a href="http://download.oracle.com/otn-pub/jcp/jdo-3.0-mrel3-eval-oth-JSpec/jdo-3_0-mrel3-spec.pdf" rel="nofollow">http://download.oracle.com/otn-pub/jcp/jdo-3.0-mrel3-eval-oth-JSpec/jdo-3_0-mrel3-spec.pdf</a></p> <p>The sql-type attribute declares the type of the column in the database. This type is database-specific and should only be used where the user needs more explicit control over the mapping. Normally, the combination of jdbc-type. length, and scale are sufficient for the JDO implementation to calculate the sql-type.</p> </blockquote>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload