Dealing with object equality and proxies

This might sound a little naive considering I'm using GLORP in production for almost a year.

But how do you deal with equality of your objects? 

Do you have any special recommendation?

I always use the default implementation inherited from Object, which relies on object identity (#==).

But I think proxies are playing with me here.

NOTE: All these examples happen in the context of the same GlorpSession.

"If I do this, it works as expected:"

(session read: MyClass) select: [ :each | each supervisor = aSupervisor].

"But if I do this it doesnt:"

(session read: MyClass) select: [ :each | aSupervisor = each supervisor ].

 

The same happens if there is a proxied reference and I use it in a where clause:

E.g. anEmployee supervisor -> aSupervisor

"This returns an empty collection."

(session read: MyClass) select: [ :each | each supervisor = anEmployee supervisor ].

"Ensuring materialization returns the proper collection."

(session read: MyClass) select: [ :each | each supervisor = anEmployee supervisor yourSelf].

You might ask why not using a GlorpExpression as a where clause, like in: 

session read: MyClass where: [ :each | each supervisor = anEmployee supervisor].

I don't because sometimes I cache the result of (session read: MyClass) to avoid roundtrips and read everything in one shot, so in-memory filtering is faster than having to pull the data from the DB each time.

Do you have any advice in favor/against this way of working?

Thank you!

--

Esteban.

--
You received this message because you are subscribed to the Google Groups "glorp-group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at http://groups.google.com/group/glorp-group.
For more options, visit https://groups.google.com/d/optout.