Query with pseudoVariable fails hwne joining another table

Dear Glorp wizards,

I have three classes, say Person, Job and Profession. A Persan can have a Job and that Job references a Profession. For reasons I won't explain here, we keep a list of all Professions in memory and therefor the relationship between Job and Profession is not mapped with a OneToOneMapping. We only have a Pseude-Variable-Mapping for the Profession_ID in table JOB.

So here is the full picture:

PERSON

ID

NAME, etc.         JOB

JOB_ID      --->   ID                     PROFESSION

                   PROFESSION_ID    -->   ID       

                   ezc.                   NAME etc.  

When I try to query the database like this:

dbSession read: Person where: [:p| p job professionId = myIDGottenFromSomewhere],

Glorp throws an Exception: no mapping for Base(Person).job.professionId

The funny thing is that if I do a query on Job like this:

dbSession read: Job where: [:p| p professionId = myIDGottenFromSomewhere]

I get the expected results. The problem only occurs when I join over another table first....

This is in the Glorp version of VA Smalltalk, so maybe this is one more of these "we already fixed that in Visualworks" things...?

Joachim

--
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 view this discussion on the web visit https://groups.google.com/d/msgid/glorp-group/b6269645-836a-4704-a0db-cba61040753c%40googlegroups.com.

Hi Johan,

 

Esteban’s question made me notice that you mentioned that the job->professionId mapping is a pseudovariable mapping, which implies that there is no actual link being mapped between the profession_id and profession table (as you carefully mention). I think glorp wants to find a physical link to follow, but there is none such mapped in the descriptor, so glorp cannot get the join it wants. This seems to be what you and Esteban already suspect. Maybe an AdHocMapping would be helpful in this case.

 

	Dave Wallen  Software Engineer
		office: 513-612-2003 website: www.cincomsmalltalk.com email: [hidden email]
--- CONFIDENTIALITY STATEMENT --- This e-mail transmission contains information that is intended to be privileged and confidential. It is intended only for the addressee named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited, please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated.

 

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Esteban Maringolo
Sent: Tuesday, September 24, 2019 8:11 AM
To: GLORP Mailing List
Subject: Re: Query with pseudoVariable fails hwne joining another table

 

Johan,

 

I know this might be obvios, but do the Job class model have a #professionId attribute and is it mapped in the Job descriptor?

 

Regards,

Esteban A. Maringolo

 

 

On Mon, Sep 23, 2019 at 9:19 AM jtuchel <[hidden email]> wrote:

Dear Glorp wizards,

 

 

I have three classes, say Person, Job and Profession. A Persan can have a Job and that Job references a Profession. For reasons I won't explain here, we keep a list of all Professions in memory and therefor the relationship between Job and Profession is not mapped with a OneToOneMapping. We only have a Pseude-Variable-Mapping for the Profession_ID in table JOB.

 

So here is the full picture:

 

PERSON

ID

NAME, etc.         JOB

JOB_ID      --->   ID                     PROFESSION

                   PROFESSION_ID    -->   ID       

                   ezc.                   NAME etc.  

 

When I try to query the database like this:

 

dbSession read: Person where: [:p| p job professionId = myIDGottenFromSomewhere],

 

Glorp throws an Exception: no mapping for Base(Person).job.professionId

 

The funny thing is that if I do a query on Job like this:

dbSession read: Job where: [:p| p professionId = myIDGottenFromSomewhere]

 

I get the expected results. The problem only occurs when I join over another table first....

 

This is in the Glorp version of VA Smalltalk, so maybe this is one more of these "we already fixed that in Visualworks" things...?

 

 

Joachim

--
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 view this discussion on the web visit https://groups.google.com/d/msgid/glorp-group/b6269645-836a-4704-a0db-cba61040753c%40googlegroups.com.

--
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 view this discussion on the web visit https://groups.google.com/d/msgid/glorp-group/CAJMgPCJxj-xZFVGGje5ckwUqzT8u1QLyDhf76%3DUDbQ-J%3D0iATA%40mail.gmail.com.

--
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 view this discussion on the web visit https://groups.google.com/d/msgid/glorp-group/CH2PR13MB36546905B19A08F077B2432FC9840%40CH2PR13MB3654.namprd13.prod.outlook.com.

Dave,

Am Dienstag, 24. September 2019 22:56:50 UTC+2 schrieb Wallen, David:

Very sorry, I was completely wrong—good thing Alan stepped in!

 

Nothing to excuse for. I am really glad you're taking time to look at this and think about my issue...

 

Based on Alan’s advice, and looking at the Person->Job mapping, do the first 2 queries work? Seems like they all should.

                dbSession read: Person where: [:p| p id = aPersonID].

                dbSession read: Person where: [:p| p job id = aJobID].

                dbSession read: Job where: [:j| j professionId = aProfessionID].

These all work nicely.

 

                dbSession read: Person where: [:p| p job professionId = aProfessionID].

 

This one doesn't (in VAST 9.1)

The exception I get is 'no mapping for base(Person).job.professionId

I guess this means Alan is right and this is related to the

 

Your query is a lot like this one, which works in my image from a StoreWorkbook:

                storeSession read: StoreBundle where: [:ea| ea packages parcelID = 3].

exatly. The only difference here is that Person->Job is 1:1 in my application where StoreBundle->Package seems to be 1:n. Not sure that is related to the problem.

Seems I have two options to find out if this is an *existing* Glorp bug, or if it's just a bug in the (soon to be updated, but currently latest) VAST version of it:

• wait for Instantiations to ship a new version
• port my model and descriptor over to VW and test the same queries there

Maybe the second choice is faster, but still painful (how to get my VAST code into VW?).

Again, thanks for your time and efforts.

Joachim

 

--
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 view this discussion on the web visit https://groups.google.com/d/msgid/glorp-group/c4053819-45de-48ff-bc8e-4713a1d73e17%40googlegroups.com.