I second all the suggestions here. My rules of thumb are:
* Don't try to sync individual objects. You can't cluster that well (whatever
Terracotta might claim, there are issues beyond transferring object state).
* Turn off object cache syncing completely, even within a single VM, to get
consiste
I have found using Caching Groups with relatively short timeouts 15
seconds, can have a huge performance benefit while still keeping most data
quite fresh.
On Thu, May 30, 2013 at 11:21 AM, Mike Kienenberger wrote:
> And be careful not to overdo it. I made that mistake in my first
> ecommerce
And be careful not to overdo it. I made that mistake in my first
ecommerce app.
In hindsight, it was sufficient to make sure the data was refreshed at
the beginning of each request, rather than "as soon as possible".
On Wed, May 29, 2013 at 7:39 PM, Aristedes Maniatis wrote:
> On 29/05/13 8:1
On 29/05/13 8:14pm, Christian Grobmeier wrote:
My concern is the Cayenne caching mostly. What if
App1 is doing an update and the next requests select from App2?
No one can answer this other than you. What does happen?
Are you writing an ecommerce system where data has to be fresh to the
milli
Hi all,
my app runs well with Cayenne and gets good feedback. With growing
data, I need to start thinking about my scaling options. I know about
ROP, but I would like to use some kind of "shared caching" or so.
Like:
DB SERVER --> App + Cayenne 1
+> App + Cayenne 2
No
Usually JDBC driver is responsible for messed up capitalization. #result(..)
would restore it back on Cayenne side to whatever you want it to be and
preserve your capitalization.
A.
On May 29, 2013, at 1:09 PM, giulio.ces...@gmail.com wrote:
> Andrus,
>
> the weird thing is that, even if the
Andrus,
the weird thing is that, even if the SQL query had the column with the
correct identifier (id_saleSummary), ObjectResolver.createObjectId would
get a lowercase only value (id_salesummary). Even with no explicit
setColumnNamesCapitalization
option.
I suppose that non PK field keys (to be m
Cool. Yeah, we need better diagnostics here. We can't tell people to use all
lowercase column names (as we do support mixed case column names), but maybe we
can have some intelligence detecting that we are not dealing with an outer join
here, and throwing instead of returning null.
BTW a usual
Andrus,
I have managed to sort out what was the problem: in my model I have Primary
Keys of DBEntities defined using camelCase (eg: "id_saleSummary").
With this setup, SelectQuery works fine, but I have found no combination of
the different settings to have SQLTemplate work right; the problem spr
