Re: custom type stops working - good-to-broken.diff (1/1)

In article , Andrus Adamchik wrote: > On Jul 19, 2012, at 3:24 PM, Arturo Perez wrote: > > > diff goodNewMap.xml badOldMap.xml. > > So does goodNewMap.xml exhibit the problem with custom types or > badOldMap.xml? Sorry, a bit confused here. Also in the diff could you te

Re: custom type stops working - good-to-broken.diff (1/1)

llecting clues). Finally, have you tried it with Cayenne 3.1? > > Thnaks, > Andrus > > On Jul 19, 2012, at 4:51 AM, Arturo Perez wrote: > > > Using 3.0.2 on Mac OS 10.5.8 and java6. > > > > After updating my map.xml with some new entities and some altered >

custom type stops working

Using 3.0.2 on Mac OS 10.5.8 and java6. After updating my map.xml with some new entities and some altered columns at least one of my custom types stops working. For example, I have an ObjEntity with 2 attributes of the same DB type (bigint) that should be converted to an object essentially using

suggestions for integrating PostgreSQL Listen/Notify

Hi all, The PostgreSQL database has a notification system built-in so that one database-connected app can signal another. The mechanism is called Listen/Notify. Some JDBC-centric docs here: http://jdbc.postgresql.org/documentation/81/listennotify.html How would I go about integrating that in

faulting exception after schema update

Hi all, Using cayenne 3.0.2, postgresql 9.0 here. Everything was working fine but I needed to do some schema redesign. I had CayenneModeler completely regenerate the model via the reengineer button. Now I'm getting a org.apache.cayenne.FaultFailureException: [v.3.0.2 Jun 19 2011 09:29:50]

Re: case insensitive =?

ot like. Besides the wildcard issue, am I wrong in thinking that like is slower? > > > On Thu, Sep 15, 2011 at 8:10 AM, Arturo Perez wrote: > > Hi all, > > > > Using Postgresql 9.0 and Cayenne 3.0.2. > > > > I've googled and googled but can't find

case insensitive =?

Hi all, Using Postgresql 9.0 and Cayenne 3.0.2. I've googled and googled but can't find the right search to answer this question. I would like to perform a query that has the equivalent of a case insensitive search. Outside of configuring collation etc I've always done it by doing something

1.2.2 fetchFinished broken?

Hi all, I just upgraded my jars from 1.2 to 1.2.2. I now find that a fetchFinished that used to work is no longer called. Is this a known bug? -arturo

create a fault like EOF?

How does one go about making a fault the way that EOF does? tia, arturo

Java5: the expression of type list needs unchecked conversion

Hi all, I'm using Eclipse and Java6 now. Whenever I do anything with performQuery() the IDE complains that the expression of type list needs unchecked conversion. I'm sure I could turn that off in the IDE but is there a way to write it so that the warning goes away? I tried casting. -ar