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
Thanks (to all who responded)!
I do use WOnder (is there nowadays any WO programmer who does not? Really?),
but still, self-evidently it makes sense to use Java collections primarily, and
go to NS-ones only when needed.
All the best,
OC
> On 2. 2. 2025, at 23:46, Ramsey Gurley wrote:
>
> I b
I believe the answer is highly dependent on whether you're using the NS
collections from WebObjects JavaFoundation or the ones from WOnder. If I
remember correctly, Anjo did a lot of work optimizing performance on the
ones in wonder, making those much faster than the ones found in
JavaFoundatio
Iirc the NS collections were there due to simplifying porting of apps from objc to Java. I don’t think there is any big difference in performance Sent from my iPhoneOn 2 Feb 2025, at 12:18, Jérémy DE ROYER via Webobjects-dev wrote:
Hi all,
Even if I still use EOF (due to inheritance limitat
Hi all,
Even if I still use EOF (due to inheritance limitations of Cayenne), I followed
Hugi’s precepts :
- « use 100% java native whenever possible »
One other advantage when working in a team… is that 100% java is widely
documented and exampled... and it's more attractive to newbees.
Sorry
When I made the switch to Java collections I did do some benchmarking. Haven’t
got the code anymore (this was a decade ago) but at that time, the Java
collection classes were faster, but the operations were really so fast in both
cases that the differences were negligible — at that time.
Since
Hi there,
did ever anybody tried some benchmarks to find whether it is better to use WO
collections (NSArray, NSDictionary...) as widely as possible (ie essentially
anywhere, unless one really needs to store nulls or can't do without
ConcurrentHashMap or so), or whether it's better to use stand
11 matches
Mail list logo
