[
https://issues.apache.org/jira/browse/JDO-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916803#action_12916803
]
Andy Jefferson commented on JDO-633:
Thx Michael.
- I added TODOs since the job of &
[
https://issues.apache.org/jira/browse/JDO-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson updated JDO-633:
---
Attachment: list_get_method.patch
Attached patch adds MeetingRoom class (and some seemingly necessary
[
https://issues.apache.org/jira/browse/JDO-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12915224#action_12915224
]
Andy Jefferson commented on JDO-633:
Considered adding new test(s) for List
[
https://issues.apache.org/jira/browse/JDO-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson resolved JDO-573.
Resolution: Fixed
SVN trunk now has the multiple navigation tests enabled, and the RI passes
(tested
[
https://issues.apache.org/jira/browse/JDO-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson updated JDO-660:
---
Attachment: JDO-660.patch
Please find attached a patch to add "position" attribute
Project: JDO
Issue Type: New Feature
Components: api, specification
Reporter: Andy Jefferson
>From the jdo-dev mailing list
Craig Russell :-
"http://openjpa.apache.org/docs/latest/manual/manual.html#ref_guide_fetch_impl
says that "Even when a direct re
Post from 25 August 2008 by Craig.
> http://openjpa.apache.org/docs/latest/manual/manual.html#ref_guide_fetch_im
> pl says that "Even when a direct relation is not eagerly fetched,
> OpenJPA selects the foreign key columns and caches the values. This way
> when you do traverse the relation, OpenJP
http://java.sun.com/xml/ns/jdo/jdo_2_0.xsd
is present, but there are no jdo_2_1.xsd or jdo_2_2.xsd now.
These cannot just be deleted, since there are specs that refer to them, and
people could be using older versions of software that refer to them. Anyone
know what's going on ?
Regards
--
An
[
https://issues.apache.org/jira/browse/JDO-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886786#action_12886786
]
Andy Jefferson commented on JDO-652:
@Matthew, annotation processing with 1.6 will
+1
--
Andy
DataNucleus (http://www.datanucleus.org)
Issue Type: Improvement
Components: api, specification, tck
Reporter: Andy Jefferson
Fix For: JDO 3 maintenance release 1
While the user can define to use a datastore sequence currently, with a
particular name, they cannot define the allocation size and star
Hi Craig,
> at http://people.apache.org/~clr/dist
http://people.apache.org/~clr/dist/m1-ibiblio-rsync-
repository/javax.jdo/poms/jdo-api-3.0.pom
has
${jdo.currentVersion}
Ought to be 3.0 in that field
--
Andy
DataNucleus (http://www.datanucleus.org)
[
https://issues.apache.org/jira/browse/JDO-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884572#action_12884572
]
Andy Jefferson commented on JDO-652:
@Matthew, you open Eclipse (and set it up to
[
https://issues.apache.org/jira/browse/JDO-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884309#action_12884309
]
Andy Jefferson commented on JDO-652:
For the QueryDSL approach : a user would not hav
[
https://issues.apache.org/jira/browse/JDO-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884274#action_12884274
]
Andy Jefferson commented on JDO-652:
See also http://www.datanucleus.org/servlet/
> > I'd like to simplify the jdo repository that now contains lots of
> > projects that are no longer being used or maintained.
+1
> > The only projects in trunk that have active development are api and
> > tck. There are a few files that we need to keep, such as LICENSE and
> > JDO3.MF, but most
[
https://issues.apache.org/jira/browse/JDO-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12881723#action_12881723
]
Andy Jefferson commented on JDO-652:
If anyone is interested in contributing ideas
[
https://issues.apache.org/jira/browse/JDO-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878531#action_12878531
]
Andy Jefferson commented on JDO-483:
DataNucleus already provides something related.
[
https://issues.apache.org/jira/browse/JDO-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson updated JDO-580:
---
Fix Version/s: JDO 3 maintenance release 1
Likely could go in JDO 3.1 since the RI has a rewritten
[
https://issues.apache.org/jira/browse/JDO-615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878501#action_12878501
]
Andy Jefferson commented on JDO-615:
Complete ?
> MetaData specificat
[
https://issues.apache.org/jira/browse/JDO-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson updated JDO-619:
---
Fix Version/s: JDO 3
The vast majority of this is already done, embodied in the API, and also in the
[
https://issues.apache.org/jira/browse/JDO-657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson resolved JDO-657.
Resolution: Won't Fix
You refer to an article on some external website (well its SUN, but a co
released today, and intended to be the RI for JDO 3.0
http://www.datanucleus.org/servlet/forum/viewthread_thread,6159
Regards
--
Andy
DataNucleus (http://www.datanucleus.org)
Issue Type: New Feature
Components: api, specification, tck
Reporter: Andy Jefferson
With an RDBMS datastore, when generating the schema, it is desirable to be able
to specify the positioning of the column(s) of a field in the generated table.
With spreadsheet document
Hi,
> I've got a minor revision ready for review for JSR 243. Please see the
> change log at http://wiki.apache.org/jdo/ChangeLog
>
> The expert group is ready to publish the updated specification
> immediately after the maintenance review is complete.
Do we have any (approximate) timescales on
[
https://issues.apache.org/jira/browse/JDO-658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12873938#action_12873938
]
Andy Jefferson commented on JDO-658:
We already have Math.abs, Math.sqrt, so why not
Components: specification, tck
Affects Versions: JDO 3
Reporter: Andy Jefferson
Consider extending JDOQL in JDO3.1 to include a series of new methods,
following the contracts of existing Java classes
String.charAt(int)
String.startsWith(String, int)
String.length
Hi Craig,
> Will this be affected by renaming all the schema files in api/src/
> schema/javax/jdo?
> There won't be a jdo_2_3.xsd or any other 2_3 artifacts, just 3.0. And
> the content will also be changed.
Good point.
I've just added "3.0" DTD/XSD local variants into the "datanucleus-core" jar
> Ok, I fixed all of these.
Seems ok for me.
PS. Since DataNucleus 2.0 is not getting much work now, and since we need a
release of DataNucleus as "RI" that refers to Maven artifact name "jdo-api",
the "RI" for JDO3 ought to be DataNucleus 2.1 (scheduled "final" release date
mid June). It pass
Hi Craig,
> I think these are pretty close to what we want to ship for the next
> release. Can others please try the two projects and see if there are
> any issues?
api builds ok for me, but creates 2.3-SNAPSHOT (from parent project.xml) not
3.0-SNAPSHOT
api/pom.xml has artifactId="jdo2-api" an
> To me, this justifies renaming the release from JDO 2.3 to JDO 3.0.
One minor issue with the rename is that the Maven repo has the artifact as
"jdo2-api". Do we go forward with this same name and just set the version to
3.0, or does it become an artifact of "jdo-api" ?
--
Andy
DataNucleus
+1 for JDO.next
+1 for JDO 3.0
--
Andy
DataNucleus (http://www.datanucleus.org)
: tck2
Reporter: Andy Jefferson
Assignee: Andy Jefferson
Fix For: JDO 2 maintenance release 3
The latest DataNucleus enhancer (2.0.2) no longer automatically enables the
annotation processor so there is no need for the -proc:none argument (and the
need to
[
https://issues.apache.org/jira/browse/JDO-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson resolved JDO-654.
Resolution: Fixed
SVN trunk has this changed
> Remove need for -proc:none using latest DataNucl
> 2. Spec updates - ready for a vote?
I think so. Have read the latest spec and don't see any problems.
--
Andy
DataNucleus (http://www.datanucleus.org)
[
https://issues.apache.org/jira/browse/JDO-651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12856036#action_12856036
]
Andy Jefferson commented on JDO-651:
Background reading relating to "problems&qu
[
https://issues.apache.org/jira/browse/JDO-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson resolved JDO-648.
Assignee: Andy Jefferson (was: Michelle Caisse)
Fix Version/s: JDO 2 maintenance release 3
Type: New Feature
Components: api2, specification, tck2
Reporter: Andy Jefferson
There are various querying capabilities of this type around. JPA2 has its
Criteria query API. Third party solutions like QueryDSL also exist, in its case
providing a JDOQL implementation (as well
[
https://issues.apache.org/jira/browse/JDO-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson updated JDO-633:
---
Fix Version/s: JDO 2 maintenance release 4
> List.get(int) support in JDOQL is miss
[
https://issues.apache.org/jira/browse/JDO-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson updated JDO-573:
---
Fix Version/s: JDO 2 maintenance release 4
> RI creates bad SQL for navigational quer
> I have no objection to this proposal. I don't think we really need a
> compatibility option, though. I can't think of a case where the user
> is *depending* on an exception to be thrown that will suddenly fail
> the application. TCK testing aside.
I have no objection to the change, BUT ...
> It
[
https://issues.apache.org/jira/browse/JDO-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12853092#action_12853092
]
Andy Jefferson commented on JDO-623:
What about pm.conf "DatastoreReadTimeout&qu
> > The parent metadata is the issue. For a TypeMetadata the parent
> > should be a PackageMetadata. But it looks like getParent() returns
> > null for a ClassMetadata.
FYI. DN SVN trunk and SVN branches/2.0 (aka 2.1.0-m1-SNAPSHOT and 2.0.3-
SNAPSHOT in nightly builds) return a valid parent.
--
[
https://issues.apache.org/jira/browse/JDO-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848828#action_12848828
]
Andy Jefferson commented on JDO-623:
Rerun test. Still fails.
SELECT AVG((
[
https://issues.apache.org/jira/browse/JDO-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson updated JDO-623:
---
Assignee: (was: Andy Jefferson)
> Query cancel and timeout supp
[
https://issues.apache.org/jira/browse/JDO-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12847486#action_12847486
]
Andy Jefferson commented on JDO-573:
For reference, DataNucleus 2.1.x passes this
Same logic applies to the DatastoreTimeout test(s). The timeout only applies
to the datastore operation, yet will be imposed against the overall call to
the JDO API (query execution). Consequently the results are currently
unreliable.
DataNucleus 2.0 passes since the JDOQL implementation in us
Hi Michael,
> I added a Thread.sleep(1000) to the main thread in order to give the
> other thread a chance to start the query before the main thread cancels
> it. Could you please give it a try?
Giving something a second to get started seems excessive, I know Derby is slow
but ... ;-)
I tried w
Hi,
Finally got around to running these tests with an implementation of JDOQL that
supports cancellation. I logged the point of calls to Query.cancel,
Query.execute etc.
11:48:59,211 (main) INFO [DataNucleus.General] - >> testCancel : creating
query
11:48:59,240 (main) DEBUG [DataNucleus.Que
> 2a. Latest DataNucleus seems to have a problem...
Actually the problem is in Derby in its inability to return a list of
indexes from a schema beyond a certain size. This was raised on Derby back
in about 2006. The issue arose its head again by enabling some additional
functionality, prior to hav
[
https://issues.apache.org/jira/browse/JDO-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson reassigned JDO-630:
--
Assignee: (was: Andy Jefferson)
DN SVN trunk now passes JDO2 TCK. Marking unassigned in case
[
https://issues.apache.org/jira/browse/JDO-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799270#action_12799270
]
Andy Jefferson commented on JDO-623:
JDO TCK SVN will look for datanucleus-
[
https://issues.apache.org/jira/browse/JDO-630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799264#action_12799264
]
Andy Jefferson commented on JDO-630:
Re: The NPE is here
Errm, no, you misunders
[
https://issues.apache.org/jira/browse/JDO-630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799130#action_12799130
]
Andy Jefferson commented on JDO-630:
No comment on any patch, but it would be nice to
[
https://issues.apache.org/jira/browse/JDO-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson reassigned JDO-623:
--
Assignee: (was: Andy Jefferson)
Unassigned since the test passes with current DN SVN. If
Just for reference, AccessPlatform 2.0.0 is now released. This builds against
current SVN trunk of Apache JDO api (and a jar of that snapshot is present in
DN Maven2 repo, entitled "jdo2-api-2.3-ec.jar").
Version 2.0.0 of AccessPlatform includes the following over version 1.1 :-
* Significantly
[
https://issues.apache.org/jira/browse/JDO-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794669#action_12794669
]
Andy Jefferson commented on JDO-623:
The patch to api2 changed the API that tck2
[
https://issues.apache.org/jira/browse/JDO-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12792403#action_12792403
]
Andy Jefferson commented on JDO-623:
I added stubs in DataNucleus several days ago
Hi Craig,
> DatanNucleus appears to be close to final release of 2.0.0.
> Is there still time to replace query timeout with datastore timeout?
Still have a JIRA left open for that, so as soon as its done in Apache JDO it
can be in DataNucleus before 2.0 release
--
Andy
Needs an update if someone has access to it. Seems to say that JDO 2.1 is in
progress. Maybe just update it to point to the entry page on Apache JDO to
avoid further maintenance ?
--
Andy
DataNucleus (http://www.datanucleus.org)
> all I could find in the docs was
> http://www.datanucleus.org/extensions/query_cache.html which is about
> caching of "query compilations". Or do you mean that it could be used to
> store query results along with a cached QueryCompilation object?
PMF prop(s)
http://www.datanucleus.org/products/a
> Our application framework caches the results of certain queries. It does
> not hand out the respective Query objects to application code, and it
> does not itself invoke any mutators on these Query objects.
DataNucleus v2.x also allows caching of query results (for non-legacy JDOQL
implementati
[
https://issues.apache.org/jira/browse/JDO-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778780#action_12778780
]
Andy Jefferson commented on JDO-649:
But will JDO 2.3 really *depend on* JPA2 ? All
[
https://issues.apache.org/jira/browse/JDO-649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson resolved JDO-649.
Resolution: Fixed
SVN trunk fixes this
> Upgrade "persistence-api.jar" for use with T
[
https://issues.apache.org/jira/browse/JDO-649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson updated JDO-649:
---
Summary: Upgrade "persistence-api.jar" for use with TCK to be JPA2 since
DataNucleus 2.x use
[
https://issues.apache.org/jira/browse/JDO-649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson updated JDO-649:
---
Description:
DataNucleus builds against JPA2 specification now so need to upgrade the
"geronimo-
se/JDO-649
Project: JDO
Issue Type: Task
Components: tck2
Reporter: Andy Jefferson
Assignee: Andy Jefferson
Fix For: JDO 2 maintenance release 3
DataNucleus builds against JPA2 specification now so need to upgrade the
"geronimo-specs"
[
https://issues.apache.org/jira/browse/JDO-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768675#action_12768675
]
Andy Jefferson commented on JDO-632:
Since the related JIRA was closed a long time
Run TCK using Maven2 for consistency
Key: JDO-647
URL: https://issues.apache.org/jira/browse/JDO-647
Project: JDO
Issue Type: Improvement
Components: tck2
Reporter: Andy Jefferson
[
https://issues.apache.org/jira/browse/JDO-606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson resolved JDO-606.
Resolution: Fixed
Fix Version/s: JDO 2 maintenance release 3
Doesn't apply to anything cu
[
https://issues.apache.org/jira/browse/JDO-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson resolved JDO-646.
Resolution: Fixed
If insisting on raising issues against work-in-progress code things will be
broken
[
https://issues.apache.org/jira/browse/JDO-645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson resolved JDO-645.
Resolution: Fixed
If insisting on raising issues against work-in-progress code things will be
broken
> If no objection from DataNucleus, Michael will update the TCK dependencies
> to version 1.1.6-SNAPSHOT for core and rdbms.
FYI 1.1.6 of core/rdbms are released. This is the final 1.1.x release. So
either switch to that or switch to 2.0.0-m2, or 2.0.0-m3-SNAPSHOT
> Discussion at last week's mee
[
https://issues.apache.org/jira/browse/JDO-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12761665#action_12761665
]
Andy Jefferson commented on JDO-623:
And does the test actually chec
> 1. TCK enhancement should make use of feature to enhance an entire
> directory: Getting NPE https://issues.apache.org/jira/browse/JDO-639
>
> Seems to be a bug in the enhancer. The version being used is
> DataNucleus Enhancer 1.1.4. Which versions should we use for the JDO
> 2.3 tck?
DataNucleu
> 1. TCK enhancement should make use of feature to enhance an entire
> directory: Getting NPE https://issues.apache.org/jira/browse/JDO-639
>
> Seems to be a bug in the enhancer. The version being used is
> DataNucleus Enhancer 1.1.4. Which versions should we use for the JDO
> 2.3 tck?
DataNucleu
> I hope this is the right list to report broken tests in the TCK testsuite,
> I'm referring to TCK 2.0, ignore my post if these issues are resolved
> meanwhile:
> The following tests are broken, because they rely on a no-args ctor
Hi Christian,
Maybe I'm missing something but if I look at spec (
[
https://issues.apache.org/jira/browse/JDO-637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736047#action_12736047
]
Andy Jefferson commented on JDO-637:
Isn't the point supposed to be that JDOQ
[
https://issues.apache.org/jira/browse/JDO-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson resolved JDO-636.
Resolution: Fixed
SVN trunk has these additions in the orm files
> TCK "models.conf&quo
URL: https://issues.apache.org/jira/browse/JDO-636
Project: JDO
Issue Type: Bug
Components: tck2
Affects Versions: JDO 2 maintenance release 2
Reporter: Andy Jefferson
Assignee: Andy Jefferson
Fix For: JDO 2 maintenance
> Attempting to build the JDO TCK with a clean maven repository, I get the
> following error:
All now point to the most recent release.
1.1 branch is not actively developed so unlikely to have many more changes.
--
Andy
DataNucleus (http://www.datanucleus.org)
[
https://issues.apache.org/jira/browse/JDO-621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12732711#action_12732711
]
Andy Jefferson commented on JDO-621:
How can somebody pass in a "filename"
[
https://issues.apache.org/jira/browse/JDO-621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12732424#action_12732424
]
Andy Jefferson commented on JDO-621:
> One oddity in the JDOEnhancer API: it only
[
https://issues.apache.org/jira/browse/JDO-615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12732419#action_12732419
]
Andy Jefferson commented on JDO-615:
DataNucleus actually does have the start of t
[
https://issues.apache.org/jira/browse/JDO-615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12732099#action_12732099
]
Andy Jefferson commented on JDO-615:
You're referring to a change some 7 months
> So I updated these dependencies to make use of the latest version:
> 1.1.5-SNAPSHOT for core and rdbms and 1.1.4-SNAPSHOT for enhancer and
> jpa. Are these the correct versions to use? If yes, I will update the
> project.xml accordingly.
Yes.
The ones with names 2.0.0-SNAPSHOT are likely to chan
> Do you have an idea how we can set the property in project.properties
> such that it is only used when running JDK 1.6?
Hi Michael,
no idea. M1 doesn't support profiles. M2 does.
Remove the enhancer from the compile CLASSPATH as Erik suggested makes more
sense to me, shouldn't be in there in t
[
https://issues.apache.org/jira/browse/JDO-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12725512#action_12725512
]
Andy Jefferson commented on JDO-633:
DataNucleus query language="JDOQL2"
[
https://issues.apache.org/jira/browse/JDO-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson resolved JDO-634.
Resolution: Fixed
I simply thought of the fact that the API2.MF was not used as the MANIFEST.MF
in
nents: api2
Reporter: Andy Jefferson
Assignee: Andy Jefferson
Fix For: JDO 2 maintenance release 3
It doesn't bother specifying the MANIFEST.MF in the pom.xml (whereas with M1 it
is defined in project.properties)
--
This message is automatically generat
> JDO doesn't define an ordering constraint, it is reasonable to assume that
> in JDO a List is an "indexed" List, hence retains the users ordering.
The only case I can think of where there is no "index" column is where the
user specified . Can easily just restrict
the use of "List.get(i)" in JD
> http://issues.apache.org/jira/browse/JDO-633 Don't know how to do this
> since the absolute order is not required to be in the database, but
> there might be a way to create the database language (e.g. SQL) to do
> an ordered subselect and choose the "nth" item from the selection?
> Database-spec
[
https://issues.apache.org/jira/browse/JDO-615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12721269#action_12721269
]
Andy Jefferson commented on JDO-615:
It's in api2, It's in the spec. Any
[
https://issues.apache.org/jira/browse/JDO-615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719548#action_12719548
]
Andy Jefferson commented on JDO-615:
Patches applied
> MetaData specificat
Hi Timo,
> The newest release of Querydsl has now support for subqueries for JDOQL.
> Is there some kind of conformance test suite to validate Querydsl as a
> JDOQL implementation?
But QueryDSL isn't a JDOQL implementation though is it ? You presumably take
your API input and convert it into a s
"QueryDSL" (documented at http://source.mysema.com/display/querydsl/Querydsl)
now provides beta support for JDOQL using type-safe syntax. Some basic docs
are found here
http://source.mysema.com/display/querydsl/JDOQL+Guide
--
Andy (DataNucleus - http://www.datanucleus.org)
> I'm asking because maven1 build support has been dropped entirely from
> datanucleus, so the jars cannot be put into the local maven1 repo by
> simply building datanucleus (with maven1).
While building using M1 has been dropped, the jars are still actually put in
the DN M1 nightly repo (from th
http://java.dzone.com/articles/whats-new-jdo-23
--
Andy (DataNucleus - http://www.datanucleus.org)
Hi,
the 2.3-ea release has happened. The api2 jar is in the IBiblio M1 repo, and
the maven-metadata.xml is in the M2 repo, but still no sign of the 2.3-ea
release jar being copied in (from the M1 repo). I think there was some
automated process that does this. Anyone know what happens ?
--
And
The vote to release the "early access" version of Apache JDO 2.3 TCK and API
with the projects that they depend on (enhancer, model, and util) passed with
4 +1 votes, 4 of them binding, and zero 0 and -1 votes.
+1 votes were from:
Michael Bouschen [pmc member]
Michelle Caisse [pmc me
501 - 600 of 1539 matches
Mail list logo
