hi roger,
i can confirm this problem.
this simple testcase shows the duplicates:
/**
* test OrderBy joined column
*/
public void testOrderByJoined2()
{
Criteria crit = new Criteria();
QueryByCriteria q = QueryFactory.newQuery(Project.class, crit);
q.
Hi Maxim,
Maxim Kuleshov wrote:
Hello!
I've tried to use type-mapping feature of JDBC in apache OJB but failed.
Broker reports the following error:
...
Caused by: org.apache.ojb.broker.OJBRuntimeException: The type
JAVA_OBJECT can not be handled by OJB. Please specify only types as
defined b
Hi Richter,
Edson Carlos Ericksson Richter wrote:
Hi!
I discovered an interesting (bug?) behaviour in OJB 1.0.3.
I am using auto-commit false for every connection.
When I store an object that has an list with cascade all, but one object
in the list fail to store, then I got "Primary Key violat
No news if this is confirmed against 1.0.4?
Richter
Edson Carlos Ericksson Richter escreveu:
Hi!
I discovered an interesting (bug?) behaviour in OJB 1.0.3.
I am using auto-commit false for every connection.
When I store an object that has an list with cascade all, but one
object in the list f
Hi guys,
I have come across a bug. I included a method to be added to
org.apache.ojb.broker.QueryTest class in the OJB testsuite that
reproduces that bug, for version 1.0.4!
The test:
Create a project, create two persons, the two persons are a member of
the project, select all projects ordered by
I'm using my custom SQL paging. i have two new properties limit, offset
in AbstractQueryImpl which i use in SqlQueryStatement class. the SQL
paging is working, but there is a problem if i reuse the same
QueryByCriteria object with different values for LIMIT, OFFSET
is there a way to turn off q
