Hi Jocheim,
Sorry I don’t have time to look at this in detail, but you might want to examine the glorp clauses and the SQL produced in GlorpDBTests. For example,
GlorpAnySatisfyTest>>testAnySatisfyTwiceNested
There is at least some overlap with your description.
Hth,
Dave
Dave Wallen |
||
|
||
--- 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. |
--
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
glorp-group...@googlegroups.com.
To post to this group, send email to
glorp...@googlegroups.com.
Visit this group at https://groups.google.com/group/glorp-group.
To view this discussion on the web visit
https://groups.google.com/d/msgid/glorp-group/43abbfcc-13f1-41f4-91b0-5056d601f564%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Sorry, Joachim, I’m the world’s absolute worst speller!
Dave
Hi Joachim,
maybe it is a side effect of twice setting the where-block for the query? At least I cannot see anything wrong, and we also have exists-queries written that way that work.
I assume you simplified the code for testing the exists only and modified the where: assignment. Or did you want to add the exists with AND: instead of where:?
Thomas
--
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 glorp-group...@googlegroups.com.
To post to this group, send email to glorp...@googlegroups.com.
Visit this group at https://groups.google.com/group/glorp-group.
To view this discussion on the web visit https://groups.google.com/d/msgid/glorp-group/43abbfcc-13f1-41f4-91b0-5056d601f564%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
-- ----------------------------------------------------------------------- Objektfabrik Joachim Tuchel mailto:jtu...@objektfabrik.de Fliederweg 1 http://www.objektfabrik.de D-71640 Ludwigsburg http://joachimtuchel.wordpress.com Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1
To view this discussion on the web visit https://groups.google.com/d/msgid/glorp-group/a1510648-d301-0ce1-86f8-f985cca2fe7c%40objektfabrik.de.
Hi Joachim,
maybe it is a side effect of twice setting the where-block for
the query? At least I cannot see anything wrong, and we also have
exists-queries written that way that work.
I assume you simplified the code for testing the exists only and
modified the where: assignment. Or did you want to add the exists
with AND: instead of where:?
Thomas
You received this message because you are subscribed to a topic in the Google Groups "glorp-group" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/glorp-group/_HPQ7nYR4_k/unsubscribe.
To unsubscribe from this group and all its topics, send an email to glorp-group...@googlegroups.com.
To post to this group, send email to glorp...@googlegroups.com.
Visit this group at https://groups.google.com/group/glorp-group.
To view this discussion on the web visit https://groups.google.com/d/msgid/glorp-group/CAGWHZ9-GmFDLAJ1uGCg3mMvMSjjCux9RXCD%2BC9LCAOo7pW0VGg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Hi Joachim,
have you tried
(k exists: (Query read: User where: [:b | b company = k company AND: (b isActive)]))
instead of
(k exists: [Query read: User where: [:b | b company = k company AND: (b isActive)]])
giving the exists: a query in parentheses instead of a BlockClosure in square brackets?
Thomas
Alan,
I tried this:
query := SimpleQuery read: KontolinoPaketKauf.
query where: [:k |
(k paket id = 1) AND: (k kaufDatum < Date today) AND:
(k datumFrischAktiviertMail = nil)].
"Es muss auch aktivierte benutzer geben, sonst darf das nicht
versandt werden"
bExp := query baseExpression.
query AND: (
[:k | k exists: (Query read: Benutzer where: [:b | b
mandant = k kunde AND: (b aktiv)])]
asGlorpExpressionOn: bExp).
But still get the same error....
Jaochim
We had something like this:
Query
read: WBPPersonal
where: [:each |
| subQuery |
subQuery := Query
read: WBPLeistung
where: [:lei | lei datumVon = Date today AND: [lei
personal = each]].
subQuery retrieve: [:x | 'x'].
each exists: subQuery].
Maybe reducing the retrieve block to only one column and some constant for each rows helps?
Thomas
--
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 glorp-group...@googlegroups.com.
To post to this group, send email to glorp...@googlegroups.com.
Visit this group at https://groups.google.com/group/glorp-group.
To view this discussion on the web visit https://groups.google.com/d/msgid/glorp-group/6e0c6868-6b44-a53a-0ad4-8b713edc5f8b%40objektfabrik.de.
To view this discussion on the web visit https://groups.google.com/d/msgid/glorp-group/29908544-b8bc-4a11-26f0-b71a25f90695%40objektfabrik.de.
To view this discussion on the web visit https://groups.google.com/d/msgid/glorp-group/bc667e31-d216-73aa-2983-a9f9b54f9865%40porabo.ch.
To unsubscribe from this group and stop receiving emails from it, send an email to glorp...@googlegroups.com.
Hi Joachim,
It looks like your version of GlorpDatabase may be from 2012. The #initialize function and many other things have been updated since then, all available in the Cincom public repository.
Dave
Dave Wallen |
||
|
||
--- 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. |
--
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 glorp-group...@googlegroups.com.
To post to this group, send email to
glorp...@googlegroups.com.
Visit this group at https://groups.google.com/group/glorp-group.
To view this discussion on the web visit https://groups.google.com/d/msgid/glorp-group/ca5cb7da-37c5-4f77-b14d-a11d8a7f38ce%40googlegroups.com.