Second that :)
- hugi
> On 19 Mar 2025, at 20:38, Jurgen Doll wrote:
>
> +1 from Jurgen, issue has been addressed - thanks.
>
> On Mar 19 2025, at 8:22 pm, Andrus Adamchik wrote:
>> I am +1
>>
>> Though would be nice if Jurgen (and Hugi) could confirm the problem we had
>> during the orig
Hi all,
I'm helping Maik and the guys at Selbstdenker update an app from Cayenne v4.1
to 4.2.
The application is very much based on handling and responding to lifecycle
events and changes, but parts of it are failing after the update, seemingly due
to a problem in CommitLogListener.
After some
On a probably related note, I had some weirdness in a project using
5.0-SNAPSHOT after the CAY-2876 merge (objects seemingly randomly disappearing).
Didn't manage to replicate it reliably so I put it on the back burner for
looking at this week (sorry about not reporting it immediately, didn't kn
n order to function (out-of-the-box). Typically this would be
> serialization libraries, like Jackson/JSON. But could be HTML templating
> libraries too, or reporting libraries. So maybe be careful what you wish
> for?
>
>
> On Sun, Feb 2, 2025 at 9:51 AM Hugi Thordarson wrote:
>
stom
> template. And with 5.0 improvements, templates can be stored in your project
> and managed by the Modeler. So I suggest we focus on this cleanup.
>
> To quote The Matrix, when we are ready, we won't have to dodge bullets.
>
> Andrus
>
>
>> On Feb 2, 2025,
Hi all!
With 5.0 under development, I’d like to re-awaken an old proposal.
When Cayenne generates classes, you’ll by default get JavaBean style prefixes
for attribute/relationship method names (“get” and “is”). I've never used those
and really don't want class generation to affect my method nam
Story of my life, catching things too late :)
Really looking forward to the 4.2 migration, all in all it just looks awesome
> On 31 May 2022, at 15:57, Andrus Adamchik wrote:
>
> Good catch! Def something we'd like to change in 4.3/5.0
>
>> On May 31, 2022, at 11:14 AM,
Hi Nikita,
That's cool! I've unfortunately had little opportunity to check out 4.2 lately
(still stuck with a mutilated 4.1 for…reasons) but incidentally started looking
at a migration last weekend.
I absolutely love the typed properties—one quick observation is that there's a
"DateProperty" t
eover it's report
> toMany relationships only.
>
> On Sat, May 16, 2020 at 1:40 PM Hugi Thordarson wrote:
>>
>> Hi Andrus!
>>
>> The message is "Query uses both limit and joint prefetch, this most probably
>> will lead to incorrect result. Either use di
ode?
>
> Andrus
>
>> On May 16, 2020, at 11:23 AM, Hugi Thordarson wrote:
>>
>> Hi all,
>> just wondering; the warning that's logged if a query uses a joint prefetch
>> in conjunction with a limit—shouldn't that only apply to to-many
>> relationships?
>>
>> Cheers,
>> - hugi
Hi all,
just wondering; the warning that's logged if a query uses a joint prefetch in
conjunction with a limit—shouldn't that only apply to to-many relationships?
Cheers,
- hugi
This sounds very nice…
To do a little dreaming, it would be even more awesome if property lazyness was
controllable on a per-query basis, usage requirements tend to be quite
dependent on context.
A bit like a ColumnSelect that still allows you to keep all your fancy
DataObject business logic i
/me instantly starts modifying DBs.
Thanks for pointing this out John!
- hugi
> On 29 May 2019, at 15:23, John Huss wrote:
>
> Doh! Turns out Cayenne already supports this for Postgres. Who knew! :-P
>
> 2621 [main] INFO org.apache.cayenne.log.JdbcEventLogger - INSERT INTO test
> (payload)
I'd just like to add that this is pretty awesome.
> On 23 Apr 2019, at 20:29, Lon Varscsak wrote:
>
> Great feature! :P
>
> -Lon
>
> On Tue, Apr 23, 2019 at 12:16 AM Nikita Timofeev
> wrote:
>
>> Hi all,
>>
>> For a long time I've worked on this task [1] and now I'm ready to
>> merge it [
e :) Hope you are well!
>
> I've merged my pull request, so you can do yours. I don't see any
> problems with adding some flexibility to BeanAccessor while keeping it
> compatible.
> And thanks for sharing your use case.
>
> On Wed, Feb 6, 2019 at 7:15 PM Hugi Thord
Hi all.
I've been experimenting a little with Cayenne 4.2. It looks lovely and I can't
wait to start using it.
One thing I bumped into is that StringProperty does not implement
ComparableProperty. Although I'd personally never design a DB or a system that
requires this, I work with a couple of
ased
>>> on a naming convention that we can safely hardcode without causing grief
>>> for someone because they didn't expect that their method would be called
>>> when evaluating expressions. Hence my preference for a DI fix.
>>>
>>> So how
y didn't expect that their method would be called
>>> when evaluating expressions. Hence my preference for a DI fix.
>>>
>>> So how about this... Unless someone else steps in by then, let me
>>> brainstorm it with Nikita a couple of weeks from now and see
ot nearly as involved as it appears.
Sounds awesome :). I wish I could be the one to step forward given I'm the one
raising a fuss, but after looking at the changes involved and given my
knowledge, I'm a bit hesitant to start hacking away on such a core part of
Cayenne's design at
rement.
Cheers,
- hugi
> On 25 Sep 2018, at 11:15, Andrus Adamchik wrote:
>
> Hi Hugi,
>
> My vote would be to do it right. There is a positive side effect that the
> entire reflection strategy suddenly becomes customizable.
>
> Andrus
>
>
>> On Sep 25
addition to
>> the options Hugi described in his original mail in this thread, I could also
>> imagine a way to modify this to be able to inject a custom Accessor
>> implementation as an alternative. What do you think?
>>
>> And… what would happen if someone would su
"An ORM that won't make you regret your life decisions"? I believe the
Hibernate crowd might relate.
- hugi
> On 27 Dec 2017, at 16:20, Andrus Adamchik wrote:
>
> Works great on my machine. I am planning to write the text for each one of
> the features on the home page.
>
> Also anyone re
scription looks like a bug.
>
> Andrus
>
>
>> On Dec 6, 2017, at 10:48 AM, Hugi Thordarson wrote:
>>
>> Hi all,
>>
>> a little dilemma. On application startup, I need to generate a DB schema for
>> only one DataMap/DataNode in a multi DataMap/Da
Hi all,
a little dilemma. On application startup, I need to generate a DB schema for
only one DataMap/DataNode in a multi DataMap/DataNode environment.
CreateIfNoSchemaStrategy isn't quite cutting it since it will check for
existence of *all* DbEntity names in the DataDomain, including DbEntity
> provides it, this works flawlessly.
>
> * In Eclipse (and others, I'm sure) I can do anObject.get[pause or
> control-space] and see all the getters associated with that object.
> Without the get prefix, they are spread out a-z and therefore you can't get
> as conc
Hi all
Touching on an old subject that has now become more important with field-based
Data Objects.
All of my DataObjects use accessor methods without the "get"-prefix. This was
fine with Map Based data objects (where a MapAccessor would get property values
by name), but now that my objects ar
( SearchIndexListener.class )
> .addListener( PriceEventListener.class )
> .module() );
>
> Andrus
>
>> On May 29, 2017, at 6:38 PM, Hugi Thordarson wrote:
>>
>> Is this correct module loading code for the New World Order?
>>
>> b.addModule(
Is this correct module loading code for the New World Order?
b.addModule( CommitLogModule.extend().addListener( CommitListener.class
).module() );
b.addModule( CommitLogModule.extend().addListener( DictionaryListener.class
).module() );
b.addModule( CommitLogModule.extend().addListener( SearchIn
Thanks for all your hard work guys! The progress Cayenne has made in the last
few months is amazing and M5 is awesome.
- hugi
> On 6. mar. 2017, at 11:43, Nikita Timofeev wrote:
>
> And to keep everything in order, here is the final voting results.
> We have 3 PMC votes in total:
>
> Andrus
>> ObjectSelect
>> .query( Person.class )
>> .columns( Person.NAME, Person.DIVISION )
>> .select( someContext );
>>
>> …to return the same result as this EJBQL:
>>
>> new EJBQLQuery( "select p.name, p.division from Person p" );
>
> Yeah, a thing to consider as the next step. E.g.
A little feedback on the ColumnSelect API:
What little I’ve used it, I’m loving it so far. But there’s one thing that
bothers me quite a bit: If I specify a relationship property as a “column” when
fetching, the resulting values will be the primary keys of the related objects.
Wouldn’t it be mo
..
>
> To be honest, I'm not terribly familiar with the DI system (I'm still
> mainly on 3.0.2), so I'd have to dig into the code to try to figure it
> out. Perhaps someone else can give you a quicker pointer or two than I can.
>
> Thanks,
>
> mrg
>
; Thanks,
>
> mrg
>
>
> On Fri, Jan 20, 2017 at 8:03 AM, Hugi Thordarson wrote:
>
>> That would probably be ideal, since certain things like case sensitivity
>> and collations apply only to Strings. But since case sensitivity is already
>> a part of Ordering
that can
> distinguish between String and other types of properties. Perhaps the initial
> solution may be a "StringOrdering extends Ordering" that takes the collator
> and overrides comparison method?
>
> Andrus
>
>
>> On Jan 11, 2017, at 5:12 PM, Hugi Thordars
Hi all,
I’ve been using the new column select API for the past week days and I’m loving
it so far.
One thing that I find a little bothersome (and at times confusing) when using
these APIs though is how return types change based on what you’re fetching,
especially how the type will change betwe
Hi all.
It looks like Cayenne's Ordering uses String.compareTo() when sorting String
values in memory using orderList() and orderedList() — and there doesn’t seem
to be any way to change that behaviour. This means sorting of international
strings in memory is somewhat broken.
Do you think it w
Always had the same problem, this is awesome :D. There’s a workaround though,
the full paths of recent projects can be seen in the file menu.
- hugi
> On 17. nóv. 2016, at 16:53, Musall, Maik wrote:
>
> Hi folks,
>
> I always had trouble finding the right one of my recent projects on the
>
Hi all.
Chose a very simple issue to submit my first pull request to Cayenne. I would
love if you’d let me know if this issue is okay, or if it's missing something
regarding best practices / cayenne traditions.
Cheers,
- hugi
e ordering. A Collection argument on the other
>> hand will need to be cloned into a list before ordering. Otherwise open to
>> suggestions.
>>
>> Andrus
>>
>>> On Aug 3, 2016, at 1:33 AM, Hugi Thordarson wrote:
>>>
>>> Hi all,
>&
Hi all,
just wondering if Ordering.orderedList( List ) should accept a Collection
rather than a List? Looks like it can be done only by modifying the signature
of the method.
Cheers,
- hugi
Hi all.
I’d just like to chime in to mention how ridiculously useful this feature has
turned out to be. I’ve been using it since day one for audit logging, but I’ve
since used it in many other places to react to changes in the object graph.
Really, really nice.
Cheers,
- hugi
> On 9. okt.
Congratulations on the 15 years and the awesome work that’s gone into Cayenne!
Your work is making my (and my customers’) life better.
Cheers,
- hugi
> On 4. feb. 2016, at 17:35, Mike Kienenberger wrote:
>
> Yeah, that's good for making you feel old :)
> According to the archives, I switched
T made it easy/easier to do that.
>
> On Mon, Jan 11, 2016 at 10:23 AM, Hugi Thordarson wrote:
>
>> EOF’s Entity Modeler is also provided as a standalone application. That
>> seems like a winning situation, where the modeler can be run either within
>> the Eclipse env
EOF’s Entity Modeler is also provided as a standalone application. That seems
like a winning situation, where the modeler can be run either within the
Eclipse environment or as an app.
- hugi
> On 11. jan. 2016, at 13:50, Michael Gentry wrote:
>
> Well, using SWT doesn't mean it has to be a
Looks great, can't wait to try it out :)
- hugi
> On 29. sep. 2015, at 09:46, Andrus Adamchik wrote:
>
> I just sent a pull request with the first cut of the implementation. My plan
> is to try this new implementation with my audit system and if it works well,
> apply it to master (hopefull
1285381823,"by":"someotheruser","clientIP":"10.1.1.2","serverIP":"127.0.0.1","op":"DELETE","id":"MyOtherEntity:3279984:17","snapshot":{"favorite":true,"sequence":0}}
>
&
This looks really great! Would you mind sharing how the class A2PropertyChange
looks?
Cheers,
- hugi
> On 22. sep. 2015, at 19:57, Andrus Adamchik wrote:
>
> Here is the design of the audit framework for everyone's review:
>
> https://issues.apache.org/jira/browse/CAY-2030
>
> The way it
o Alex Kolonitsky is now working on a
> new SelectTranslator to include aggregates, etc., so this step will likely
> overlap with his work.
>
> Andrus
>
>
>> On Jul 24, 2015, at 7:56 PM, Hugi Thordarson wrote:
>>
>> Indeed :). I’ve been looking at the Expressi
015, at 17:01, John Huss wrote:
>
> It would be pretty easy to generate it as a static inner class using the
> entity template, then all the code is generated. Do the BeanInfo classes
> have to be registered somewhere?
>
> On Fri, Jul 24, 2015 at 11:32 AM Hugi Thordarson wro
st the get* seemed
>> annoying,
>>> but now within Eclipse it is easy to type "get" and let the
>> autocompletion
>>> popup show me my options, which you can't do without that prefix.
>> Overall,
>>> I think get* is a win because it is ea
he get* seemed annoying,
>> but now within Eclipse it is easy to type "get" and let the autocompletion
>> popup show me my options, which you can't do without that prefix. Overall,
>> I think get* is a win because it is easier to find your getters and it
>>
irely within Cayenne’s universe? (I’m sure I’m not the
only one who is not fond of using it)
I got around this particular case by implementing my own “poor man’s
KeyValueCoding” (for those of you familiar with EOF), but it would be nice not
having to do something of that ilk.
Cheers,
- hugi
//
That won't help with mutable types, since modifying them will not use the
setter method.
- hugi
On 8.9.2014, at 12:58, Mike Kienenberger wrote:
> I think it would be difficult to enforce, even if we wanted to
> disallow it, since any non-primitive could be mutable.
>
> What I might do is to
…Hugi still uses that subclass—and is still a WO guy :). The class in question
is rather simple and really just a Cayenne-ized version of ERXSortOrdering.
Quite convenient.
https://bitbucket.org/hugi/jambalaya/src/4a0b939d5a4e5d82f124cc46439a4cd6803efcd1/src/main/java/com/eplica/jambalaya/Chaina
hat's definitely desirable, so you can write, as you say expression.count(
ObjectContext ) or expression.fetch( ObjectContext ).
Cheers,
- hugi
On 18.9.2011, at 11:12, Aristedes Maniatis wrote:
> On 16/09/11 11:36 PM, Hugi Thordarson wrote:
>> We've committed the code as a Ma
Hi Andrus
> The ERXKeys were created well past my EOF days, but I saw the code based on
> it on a few projects and it looked quite impressive.
Yes, I've been using them for many years, and I really like the syntax
> Type-safe queries are very high on the Cayenne priority list. Since we
> pla
Hi Ari.
> Welcome to Cayenne. The work you have done is extremely welcome and has been
> discussed before:
Thank you :).
> I encourage you to do a couple of things to follow this through and see if we
> can get this approach into Cayenne:
>
> 1. Take this over to the dev list (I'm copying tha
57 matches
Mail list logo
