Hi Samuel,
Yeah, Expressions (the things actually generated by the Properties) can be used
for both querying the DB and for in-memory evaluation, i.e. what you call
"object queries”. I haven’t looked much into how much you can do “in-memory”
with the more complex Expressions though, have to do
Hi Hugi,
So those Properties can build objects queries AND more custom queries like
ERXQuery, seems very cool.
Can you create Properties for EO methods ? I have many of them for things like
"return a previously set value or compute a default one"...
I want to play with Cayenne but have not fou
Hi Samuel,
Yes, we have a very nice querying API/syntax similar to ERXKey in Cayenne
(although they’re called “Properties” in the Cayenne world).
For example, selecting all my receipts, ordering them by date and prefetching
their entries:
ObjectSelect
.query( Receipt.class )
Hi everyone,
Nobody mentioned it, but I often designed my code through interfaces.
So I would write Samuel code like this:
List etudiants = Groupe.blabla
Because I used often java libraries and I didn’t care about implementation.
All the best,
Philippe
> On 3 Feb 2025, at 13:18, Samuel Pellet
HI,
Those NS collections where essentials in the first java WO mainly because at
that time Java did not had real collections classes (they appeared in Java
1.8), and the name was probably kept to help porting. I did not switch to java
WO at that time and maintained some objective-C apps for a l
It's there, you just can't see it because it is filtered by default. In
your WOExplorer tab, click the three dots to View Menu, then select
Filters and uncheck .* resources.
On 2/3/25 2:06 PM, Theodore Petrosky wrote:
This I don’t see:
If you put it in src/main/resources, but did not incl
