Oh, and actually I think we can fix it in the interim per
https://issues.apache.org/jira/browse/CAY-1744 … The "hack" in the example
makes me blush :)
Andrus
On Oct 6, 2012, at 12:04 AM, Andrus Adamchik wrote:
> Hi Ramiro,
>
> Finally I have something specific for you:
> https://issues.apa
Hi Ramiro,
Finally I have something specific for you:
https://issues.apache.org/jira/browse/CAY-1743
In the source code attached to this Jira, I am simply blocking "readOnly"
status of all model relationships. The example is a completely self-conatined
project. It is built against 3.2M1-SNAPSH
I have always done my encryption at the application level.
I think there are a number of reasons why this makes the most sense.
Here are some tips from my past experience:
1) clump multiple kinds of data together, and/or randomly add data.
Encrypting a single field value by itself generally does
Now works perfectly even on cayenne 3.0.2
2012/10/5 Andrus Adamchik
> Cool. Let us know how that worked. And we are planning on some permanent
> changes to solve this problem universally:
>
> http://cayenne.markmail.org/thread/icr7seqazgsdtewc
>
> On Oct 5, 2012, at 5:29 PM, Emanuele Maiarelli <
Ok, having primary keys declared as numeric(38,0) was the source of the
problem, also i noticed that foreing key of table anagrafiche, was a
bigint,that proly lead cayenne to errors.
I'm also surprised about postgress that usually is very strong typed, that
allowed me to build a relation between n
Cool. Let us know how that worked. And we are planning on some permanent
changes to solve this problem universally:
http://cayenne.markmail.org/thread/icr7seqazgsdtewc
On Oct 5, 2012, at 5:29 PM, Emanuele Maiarelli
wrote:
> indeed i just noticed that tables having this kind of problem have PK
Hi All,
I would like to know is there any way Cayenne supports MySQL DB
encryption/decryption seamlessly. Or else is there any third party libraries
like Jasypt is available, which we can use for encryption purpose.
I know Jasypt can be integrated with Hibernate for encrypting/decrypting the
indeed i just noticed that tables having this kind of problem have PKs
declared as numeric(38,0), this is something that postgress supports as
oracle like types, but usually numeric primary keys are declared as bigint
(or int since serials and bigserials are int and bigint) , i'm gonna
declare em
El 19/09/2012 22:12, Andrus Adamchik escribió:
On Sep 19, 2012, at 11:24 AM, Ramiro Aparicio
wrote:
BTW I tried to do everything with 3.0.2 modeller and finally updated to 3.1.B1
modeller, Will the model created with 3.1.B1 modeller work with 3.0.2 runtime?
(I want to update the runtime but
I guess I need to run it in debugger with this driver version. I still suspect
some NUMERIC ambiguity issue.
Andrus
On Oct 5, 2012, at 5:04 PM, Emanuele Maiarelli
wrote:
> Problem persists after upgrading to cayenne 3.1B1.
>
> org.apache.cayenne.CayenneRuntimeException: [v.3.1B1 May 28 2012
Problem persists after upgrading to cayenne 3.1B1.
org.apache.cayenne.CayenneRuntimeException: [v.3.1B1 May 28 2012 20:59:56]
Can't find id for {; committed;
[toProvince=>?; anagraficheArray=>(..); comuniCap=>55049;
comuniComIstat=>33; comuniCfPrefix=>L833; anagraficheArraySl=>(..);
comuniDesc=>PR
Thank you!
Got it working without problems.
El 05/10/2012 8:50, Andrus Adamchik escribió:
Hi,
The entry point to Cayenne in 3.1 is ServerRuntime. If you already have
CayenneFilter elsewhere in the application, it means ServerRuntime is already
created and can be retrieved by your code outside
Hi,
> If i call the method "toComuni" via reflection it fetchs the related
> object, but puts it in Hollow state (ex: { comuni_pk=4615>; hollow; []}).
>
> I also noticed that if i fetch all "Comuni" objects with a select query,
> before calling "toComuni" method via reflection, the object state i
13 matches
Mail list logo
