tDispatchThread.pumpEvents(Unknown Source)
> at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
> at java.awt.EventDispatchThread.run(Unknown Source)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
hThread.java:173)
> at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:168)
> at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:160)
> at java.awt.EventDispatchThread.run(EventDispatchThread.java:121)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
es.
> AFAIK the only addition is special syntax for boolean property getter.
> 2. Write a few unit tests that show that ROP works ok with primitive
> attributes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
as it
> would make it easier for the ROP client to detect this situation and perhaps
> reconnect.
> My proposal is to add org/apache/cayenne/remote/MissingSessionException as a
> subclass of CRE and throw it from BaseRemoteService.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
y fields, the users always
> have to scroll because one can't simply drag a split pane to adapt the size.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
or object relationships, one
> to many - cascade, and vice versa - to nullify. I think it's the rules used
> mostly for these relationships.
> And the best thing would be to have configurable options for these, but
> that's more complex.
--
This message is automatically ge
stract' keyword
> Other changes (such as throwing runtime exception when querying abstract
> entity with no concrete subclasses) could probably wait until later since
> they need to be implemented as part of inheritance.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
is - store the rules in DataMap for possible reverse
> engineering with Ant. This should allow model synching directly against the
> database (but would of course require a special Ant task)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
To: [EMAIL PROTECTED]
> Subject: Re: Detailed log/progress view?
> Date: Fri, 2 Sep 2005 10:17:38 -0400 (16:17 CEST)
> Care to file an improvement request in Jira?
> http://objectstyle.org/cayenne/bugs-features.html
> Andrus
> On Sep 2, 2005, at 10:01 AM, Øyvind Harb
s to handle primitives. This should be easier then
> the server templates, as client objects are using real ivars for attributes.
> AFAIK the only addition is special syntax for boolean property getter.
> 2. Write a few unit tests that show that ROP works ok with primitive
> attributes.
tives. This should be easier then
> the server templates, as client objects are using real ivars for attributes.
> AFAIK the only addition is special syntax for boolean property getter.
> 2. Write a few unit tests that show that ROP works ok with primitive
> attributes.
--
This message
f
> dependencies (modeler itself, jgoodies, etc). Most uses of Cayenne Maven
> integration are for things like cgen, so it would be nice to limit the number
> of dependencies to a minimum. Therefore cayenne:modeler goal will be split in
> a separate plugin
--
This message is autom
automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
selected. We need to support
client-specific DataMap class from both Ant and CayenneModeler
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
the superclass (with noop default implementation, as there
> all DB's are different in LIMIT syntax, and most don't support it). This is
> partially motivated by CAY-1130 that will require support of optional limit
> clause turning on and off depending on other query paramete
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
; http://www.orbital-computer.de/JComboBox/
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
query uses fetch limit and to-many
relationship is prefetched. The result is trimmed as Cayenne adds a LIMIT
clause. Need to test both scenarious - select with a LIMIT SQL clause and in
memory LimitResultIterator
--
This message is automatically generated by JIRA.
-
You can reply to this email t
ed in Jira
when I opened CAY-1128)
> Joint prefetches always result in inner joins
> -
>
> Key: CAY-930
> URL: https://issues.apache.org/cayenne/browse/CAY-930
> Project: Cayenne
>
[
https://issues.apache.org/cayenne/browse/CAY-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrus Adamchik closed CAY-1125.
Resolution: Cannot Reproduce
Great. So I am closing the Jira.
> MySQL SMALLINT UNSIGNED
uld use getInteger()
> (the later is always needed when using the unsigned version of SMALLINT in
> the database, doesn't it?).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
ntext.getGraphManager().getNode(obj.getObjectId()));
> }
> }
> BTW same thing with DataContext works
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
works
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
ny class set in this way should have at least one subclass.
> 3. Changes, particularly to SelectQuery, which accomodates this change and
> returns the appropriate objEntities.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Changes, particularly to SelectQuery, which accomodates this change and
> returns the appropriate objEntities.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
least one subclass.
> 3. Changes, particularly to SelectQuery, which accomodates this change and
> returns the appropriate objEntities.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
; 3. Changes, particularly to SelectQuery, which accomodates this change and
> returns the appropriate objEntities.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
ging it to use OUTER joins suddenly makes it usable (and
> in fact even more robust than DISJOINT prefetches - see the problem described
> in CAY-1025).
> Needed code was committed as a part of CAY-1025 work, so here we'll need to
> update the docs and the UPGRADE-NOTES.txt.
--
patchEvent(EventQueue.java:463)
> at
> java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:269)
> at java.awt.EventDispatchThread.pumpE
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
and throw an exception
> 3. Detect these cases and silently drop a prefetch
> I should note that debugging these problems is very hard, as they look
> totally random until you get to the cause.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
ge is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
a Short type (that is always signed).
> Forcing the type to INTEGER in the map.xml changes anything.
> It seems that Cayenne is using a getShort() when it should use getInteger()
> (the later is always needed when using the unsigned version of SMALLINT in
> the database, doesn't it?).
sult validationResult) {
> return true;
> }
> }
> Then I register it with
> Configuration.getSharedConfiguration().getDomain().getNode("MyNode").getAdapter().getExtendedTypes().registerType(new
> UUIDType());
> Wouldn't it better to have same functionality in Cayenne core?
> Thanks,
> Artyom
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
r be used
> as a cache key.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
cache key.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
mponent.dispatchEvent(Component.java:3903)
> at java.awt.EventQueue.dispatchEvent(EventQueue.java:463)
> at
> java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:269)
> at java.awt.EventDispatchThread.pumpE
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
omatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
uld use getInteger()
> (the later is always needed when using the unsigned version of SMALLINT in
> the database, doesn't it?).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
should use getInteger()
> (the later is always needed when using the unsigned version of SMALLINT in
> the database, doesn't it?).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
ything.
> It seems that Cayenne is using a getShort() when it should use getInteger()
> (the later is always needed when using the unsigned version of SMALLINT in
> the database, doesn't it?).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
List uris = dataContext.performQuery(query);
> Code without casts looks more pretty and clean... doesn't it? :)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
rite just this:
> NamedQuery query = new NamedQuery("GetUris");
>
> query.setColumnNamesCapitalization(SQLTemplate.UPPERCASE_COLUMN_NAMES);
> List uris = dataContext.performQuery(query);
> Code without casts lo
> List uris = dataContext.performQuery(query);
> Code without casts looks more pretty and clean... doesn't it? :)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
hat Cayenne is using a getShort() when it should use getInteger()
> (the later is always needed when using the unsigned version of SMALLINT in
> the database, doesn't it?).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
er()
> (the later is always needed when using the unsigned version of SMALLINT in
> the database, doesn't it?).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
ince it
> overflows the Java Short type (that is always signed).
> Forcing the type to INTEGER in the map.xml changes anything.
> It seems that Cayenne is using a getShort() when it should use getInteger()
> (the later is always needed when using the unsigned version of SMALLINT in
> t
always needed when using the unsigned version of SMALLINT in
> the database, doesn't it?).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
= dataContext.performQuery(query);
> Code without casts looks more pretty and clean... doesn't it? :)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
.performQuery(query);
> Code without casts looks more pretty and clean... doesn't it? :)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
ing the type to INTEGER in the map.xml changes anything.
> It seems that Cayenne is using a getShort() when it should use getInteger()
> (the later is always needed when using the unsigned version of SMALLINT in
> the database, doesn't it?).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
ays signed).
Forcing the type to INTEGER in the map.xml changes anything.
It seems that Cayenne is using a getShort() when it should use getInteger()
(the later is always needed when using the unsigned version of SMALLINT in the
database, doesn't it?).
--
This message is automatically ge
> at
> org.apache.cayenne.access.DataDomainQueryAction.execute(DataDomainQueryAction.java:129)
> at org.apache.cayenne.access.DataDomain.onQuery(DataDomain.java:740)
> at
> org.apache.cayenne.util.ObjectContextQueryAction.runQuery(ObjectContextQueryAction.java:2
gt; at
> org.apache.cayenne.util.ObjectContextQueryAction.runQuery(ObjectContextQueryAction.java:296)
> at
> org.apache.cayenne.util.ObjectContextQueryAction.execute(ObjectContextQueryAction.java:84)
> at
> org.apache.cayenne.access.DataContext.onQuery(DataContext.java:1331)
> at
> org.apache.cayenne.access.DataContext.performQuery(DataContext.java:1320)
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
:261)
at
org.apache.cayenne.DataObjectUtils.objectForPK(DataObjectUtils.java:172)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
ld require that
> any class set in this way should have at least one subclass.
> 3. Changes, particularly to SelectQuery, which accomodates this change and
> returns the appropriate objEntities.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
n this way should have at least one subclass.
> 3. Changes, particularly to SelectQuery, which accomodates this change and
> returns the appropriate objEntities.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
time, so i'm closing now this issue (it
was committed long ago). Incomplete because "Sequence Generator Configuration"
was not implemented (and if should be, this must be a separate JIRA). The patch
is quite like Heiko's (but written from the clean sheet)
> Cayenne N
in DataMap for possible reverse
> engineering with Ant. This should allow model synching directly against the
> database (but would of course require a special Ant task)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
e inner result iterator (JDBCResultIterator) not the outer
> filtering iterator (DistinctResultIterator)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
e inner result iterator (JDBCResultIterator) not the outer
> filtering iterator (DistinctResultIterator)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
> }
> @Override
> public boolean validateProperty(Object source, String property,
> Object value, DbAttribute dbAttribute,
> ValidationResult validationResult) {
> return true;
> }
> }
> Then I register it with
> Configuration.getSharedConfiguration().getDomain().getNode("MyNode").getAdapter().getExtendedTypes().registerType(new
> UUIDType());
> Wouldn't it better to have same functionality in Cayenne core?
> Thanks,
> Artyom
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
code stuff? I've already
attached it. I am a bit new to JIRA, so... sorry :)
Thanks,
Artyom
> Add UUID support
>
>
> Key: CAY-1123
> URL: https://issues.apache.org/cayenne/browse/CAY-1123
> Project: Cayenne
g property,
> Object value, DbAttribute dbAttribute,
> ValidationResult validationResult) {
> return true;
> }
> }
> Then I register it with
> Configuration.getSharedConfiguration().getDomain().getNode("MyNode").getAdapter().getExtendedTypes().registerType(new
> UUIDType());
> Wouldn't it better to have same functionality in Cayenne core?
> Thanks,
> Artyom
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
ypes().registerType(new
UUIDType());
Wouldn't it better to have same functionality in Cayenne core?
Thanks,
Artyom
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
List uris = dataContext.performQuery(query);
> Code without casts looks more pretty and clean... doesn't it? :)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
().size());
> context.commitChanges(); //important line!
>
> o2.setTable1(null);
> assertEquals(0, o1.getTable2Array().size());
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
write just this:
> NamedQuery query = new NamedQuery("GetUris");
>
> query.setColumnNamesCapitalization(SQLTemplate.UPPERCASE_COLUMN_NAMES);
> List uris = dataContext.performQuery(query);
> Code without casts looks more pretty and clean... doesn't it? :)
hanges(); //important line!
>
> o2.setTable1(null);
> assertEquals(0, o1.getTable2Array().size());
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
write just this:
> NamedQuery query = new NamedQuery("GetUris");
>
> query.setColumnNamesCapitalization(SQLTemplate.UPPERCASE_COLUMN_NAMES);
> List uris = dataContext.performQuery(query);
> Code without casts looks more pretty and clean... doesn't it? :)
clean... doesn't it? :)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
jectContextQueryAction.execute(ObjectContextQueryAction.java:96)
> at org.apache.cayenne.access.DataContext.onQuery(DataContext.java:1326)
> at
> org.apache.cayenne.access.DataContext.performGenericQuery(DataContext.java:1285)
> at
> org.apache.cayenne.access.DataContextEJBQLDeleteTest.testDeleteIdVar(DataContextEJBQLDeleteTest.java:98)
> The problem is SQLTemplate #bind directive incomplete collection handling.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
ext.java:1285)
at
org.apache.cayenne.access.DataContextEJBQLDeleteTest.testDeleteIdVar(DataContextEJBQLDeleteTest.java:98)
The problem is SQLTemplate #bind directive incomplete collection handling.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
ql.SQLException: Argument data type text is invalid for argument 1 of
> upper function.
> at
> net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:364)
> at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2754)
> at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2195)
--
; http://jcp.org/aboutJava/communityprocess/final/jsr221/index.html
> This will probably involve creating a new maven build target for Java 6 and
> adding specific support there.
> http://markmail.org/message/zfdrqz6rnnjkdsrr
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
p.org/aboutJava/communityprocess/final/jsr221/index.html
> This will probably involve creating a new maven build target for Java 6 and
> adding specific support there.
> http://markmail.org/message/zfdrqz6rnnjkdsrr
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
:43 AM [0x0-0xc30c3].au.ish.com.oncourse.client[1667] --
java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
terator) not the outer
> filtering iterator (DistinctResultIterator)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Reporter: Andrey Razumovsky
Assignee: Andrey Razumovsky
Fix For: 3.0
Nested contexts should be avaliable via CayenneContext. This also leads to
moving up some methods from DataContext to BaseContext, or even ObjectContext
--
This message is automatically generated by JIRA
o2.setTable1(o1);
>
> assertEquals(1, o1.getTable2Array().size());
> context.commitChanges(); //important line!
>
> o2.setTable1(null);
> assertEquals(0, o1.getTable2Array().size());
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
e2 o2 = context.newObject(ClientMtTable2.class);
> o2.setTable1(o1);
>
> assertEquals(1, o1.getTable2Array().size());
> context.commitChanges(); //important line!
>
> o2.setTable1(null);
> assertEquals(0, o1.getTable2Array().size
context.commitChanges();
>
> assertEquals("1", o.getGlobalAttribute1());
> o.setGlobalAttribute1("2");
> assertEquals("2", o.getGlobalAttribute1());
> context.rollbackChanges();
> assertEquals("1", o.ge
);
assertEquals(0, o1.getTable2Array().size());
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
terator) not the outer
> filtering iterator (DistinctResultIterator)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
GlobalAttribute1("1");
> context.commitChanges();
>
> assertEquals("1", o.getGlobalAttribute1());
> o.setGlobalAttribute1("2");
> assertEquals("2", o.getGlobalAttribute1());
> context.rollbackChanges();
>
SQLDiagnostic.java:364)
> at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2754)
> at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2195)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
LException: Argument data type text is invalid for argument 1 of
> upper function.
> at
> net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:364)
> at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2754)
> at net.sourceforge.jtds.jdbc.TdsCore.next
Components: Cayenne Core Library
>Affects Versions: 3.0
>Reporter: Scott Anderson
>Assignee: Tore Halset
> Attachments: AutoIncrement-SQLite4.patch
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
t;Affects Versions: 3.0
>Reporter: Scott Anderson
>Assignee: Tore Halset
> Attachments: AutoIncrement-SQLite4.patch
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
t;Affects Versions: 3.0
>Reporter: Scott Anderson
>Assignee: Tore Halset
> Attachments: AutoIncrement-SQLite3.patch, AutoIncrement-SQLite4.patch
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
t;Affects Versions: 3.0
>Reporter: Scott Anderson
>Assignee: Tore Halset
> Attachments: AutoIncrement-SQLite3.patch, AutoIncrement-SQLite4.patch
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Increment-SQLite2.patch,
> AutoIncrement-SQLite3.patch
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Attachments: AutoIncrement-SQLite.patch, AutoIncrement-SQLite2.patch,
> AutoIncrement-SQLite3.patch
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
t;Affects Versions: 3.0
>Reporter: Scott Anderson
>Assignee: Tore Halset
> Attachments: AutoIncrement-SQLite.patch, AutoIncrement-SQLite2.patch,
> AutoIncrement-SQLite3.patch
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
erverAdapter) adapter; will raise
> a Class Cast Exception.
> A possible fix could be eliminating this cast as createTableAppendColumn
> method is defined in DbAdapter interface, so the cast is useless.
> See
> http://www.nabble.com/Upcast-problems-w-SQLServerMergerFactory-and-AutoAdapt
ined in DbAdapter interface, so the cast is useless.
> See
> http://www.nabble.com/Upcast-problems-w-SQLServerMergerFactory-and-AutoAdapter-td19664724.html
> (the patch is known but not implemented yet)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
d19664724.html
(the patch is known but not implemented yet)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
ne Core Library
>Affects Versions: 3.0
>Reporter: Scott Anderson
>Assignee: Andrus Adamchik
> Attachments: AutoIncrement-SQLite.patch, AutoIncrement-SQLite2.patch,
> AutoIncrement-SQLite3.patch
>
>
--
This message is automatically generate
Issue Type: Improvement
> Components: Cayenne Core Library
>Affects Versions: 3.0
>Reporter: Scott Anderson
>Assignee: Andrus Adamchik
> Attachments: AutoIncrement-SQLite.patch, AutoIncrement-SQLite2.patch,
> AutoIncrement-SQLite3.patch
>
>
ponents: Cayenne Core Library
>Affects Versions: 3.0
>Reporter: Scott Anderson
>Assignee: Andrus Adamchik
> Attachments: AutoIncrement-SQLite.patch, AutoIncrement-SQLite2.patch,
> AutoIncrement-SQLite3.patch
>
>
--
This message is automatically g
1 - 100 of 1249 matches
Mail list logo
