Posted
over 16 years
ago
One of the small differences I see between the findNode method and the locateObject method (latest revision: 1453):
[code]locateObject:
521 if (sm.getClassMetaData().hasExtension("name"))
522 {
[b] 523
|
Posted
over 16 years
ago
Hello,
I think there is an issue during ddl output file generation.
Here is the ModelObject:
[font=courier new]public class Node {
private Set parents = new HashSet();
private Set children = new HashSet();
}[/font]
Here is the metadata file:
[font=courier new]
|
Posted
over 16 years
ago
Hi all,
I'm pretty new to object persistence through the JDO API so i've read a lot of documentation on this site but now i have got a question :)
I've seen the benchmarks executed by PolePosition using a HSQLDB RDBMS datastore. In
|
Posted
over 16 years
ago
hi,
i use the datanucleus1.0.1m1 maven plugin and tried to export the schema generation with the paramater during the goal schema-create. Where are the create tables statements in the output file ???
i use the following properties:
# JDO
|
Posted
over 16 years
ago
This problem has reappeared. If I insert a second object with the same primary key value, there is no exception and the duplicate object is persisted in the xml file. I'm using yesterday's nightly build... it should be revision 1460. I'm not sure
|
Posted
over 16 years
ago
Am I being impatient here. Should I wait for for m2 samples ?
Anyway, I tried it as described at
http://www.datanucleus.org/guides/jdo/tutorial.html
But when using the jars of
datanucleus-accessplatform-rdbms-1.0.0.m2
I get message this
|
Posted
over 16 years
ago
I am getting errors when I try to run
datanucleus-samples-jdo-tutorial-1.0.0.m1
using
datanucleus-accessplatform-rdbms-1.0.0.m2
"NUCLEUS_TABLES" and its columns are not being found. But the table and its columns are there in my database(called nucleusm2 in this case). See attached file for complete log.
|
Posted
over 16 years
ago
I have an M-N relationship (with a unidirectional 1-N relation on the N object) where if, on retrieval, I set the maxFetchDepth to -1 everything works fine. If I set the fetch depth to something other than -1 I receive the following exception:
|
Posted
over 16 years
ago
[img]http://www.datanucleus.org/images/logos/DataNucleus_AccessPlatform_80.jpg[/img]
We're pleased to announce the release of the second milestone for Access Platform version 1.0 ("Faraday").
You can read the release announcement [url=http://www.datanucleus.com/news/access_platform_1_0_m2.html]here[/url].
|
Posted
over 16 years
ago
I have a class:
[code]public class A {
@PrimaryKey
//@Extension(vendorName = "datanucleus", key = "XmlAttribute", value = "true")
private String OID = null;
@Persistent
private String Name = null;
@Persistent
private ArrayList Stats = null;
}[/code]
And persisting an instance of A I get:
[code]
...
|