D'oh. Indeed there was a typo in my model (again caused by batch renaming).
After fixing, the derived attributes in qualifiers work all right.
Thanks,
OC
On 12. 3. 2016, at 1:23, OC wrote:
> Is it normal that one can't use derived attributes in qualifier (when
> fetching
Is it normal that one can't use derived attributes in qualifier (when
fetching), or am I doing something wrong in my model? It seems to me that since
they are defined SQL-side, they should be able to limit the fetch, should they
not?
Anyway whenever I try to fetch with a qualifier
My model also has:
columnName = "";
for my derived attributes - maybe that matters?
John
On Fri, Feb 26, 2010 at 1:51 PM, Kieran Kelleher wrote:
> Hi all,
>
> I tried adding a simple derived attribute to a model, as shown here:
>
>
> http://idisk.me.com/kell
ution to this
particular problem.
On Feb 26, 2010, at 3:33 PM, John Huss wrote:
My model also has:
columnName = "";
for my derived attributes - maybe that matters?
John
On Fri, Feb 26, 2010 at 1:51 PM, Kieran Kelleher > wrote:
Hi all,
I tried adding a simple derived attri
ist
directly first - that was not the solution to this particular problem.
On Feb 26, 2010, at 3:33 PM, John Huss wrote:
> My model also has:
>
> columnName = "";
>
> for my derived attributes - maybe that matters?
>
> John
>
> On Fri, Feb 26, 2010 at 1:5
derived attributes for COUNT(*)
and aggregate functions, but is there anyone out there using model-defined
derived attributes successfully?
java.lang.IllegalStateException: sqlStringForAttribute: attempt to generate SQL
for attribute 'uniqueID' on entity 'CTMessage' with u
case I generally avoid using derived attributes altogether
and use custom business logic instead for the following reasons
documented in the EOModeler user's guild:
While it sometimes _seems_ like a guild, I don't think we have
actually formed it yet. :-P
--
Practical W
On 16.04.2007, at 15:29, Chuck Hill wrote:
Well, how about that. Learn something new everyday.
:-)
If you get a "send me a word in language XY every day to learn
that" (replace XY with whatever language you don't know), you can
claim for the rest of the day that you already learned some
On Apr 16, 2007, at 2:41 PM, Robert Walker wrote:
In any case I generally avoid using derived attributes altogether
and use custom business logic instead for the following reasons
documented in the EOModeler user's guild:
While it sometimes _seems_ like a guild, I don't thi
In any case I generally avoid using derived attributes altogether and
use custom business logic instead for the following reasons
documented in the EOModeler user's guild:
-
De
On Apr 16, 2007, at 2:25 PM, Robert Walker wrote:
Well, how about that. Learn something new everyday.
:-)
I tried this myself in a quick test. Here's the full SQL from my
test fetch specification:
Fetch Spec:
EOQualifier qual = EOQualifier.qualifierWithQualifierFormat("value3
< 50.
Well, how about that. Learn something new everyday.
I tried this myself in a quick test. Here's the full SQL from my
test fetch specification:
Fetch Spec:
EOQualifier qual = EOQualifier.qualifierWithQualifierFormat("value3 <
50.0", null);
EOFetchSpecification fs = new EOFetchSpecificatio
It resolves the attribute names to the columns names as you would
expect, so you get
Select ...
Where (inm_productTax1 + inm_productTax2 + inm_productTax3) > 0
John
On 4/16/07, Robert Walker <[EMAIL PROTECTED]> wrote:
Fetch spec qualifier = "totalTaxes > 0"
Interesting. What does the genera
Fetch spec qualifier = "totalTaxes > 0"
Interesting. What does the generated SQL look like?
On Apr 16, 2007, at 3:45 PM, John Huss wrote:
Here's an example:
Attribute name = "totalTaxes"
Attribute derived definition = "productTax1 + productTax2 +
productTax3"
(productTax* are attribute n
Here's an example:
Attribute name = "totalTaxes"
Attribute derived definition = "productTax1 + productTax2 + productTax3"
(productTax* are attribute names in the same entity, not the column names)
Fetch spec qualifier = "totalTaxes > 0"
This works for any kind of fetch spec.
John
I know you can use derived attributes in Raw Row fetches (I do this
all the time). I don't see why they wouldn't work in regular fetches
too.
The exception explains why you can't do that. It's one thing to
included derived columns in the results of a query, and quite
I know you can use derived attributes in Raw Row fetches (I do this
all the time). I don't see why they wouldn't work in regular fetches
too.
John
On 4/16/07, Ken Anderson <[EMAIL PROTECTED]> wrote:
No. Fetch specs work directly against the database, so if the column
doesn&
No. Fetch specs work directly against the database, so if the column
doesn't exist (as with derived attributes), it can't work. You would
have to do a fetch on a superset, then use an in-memory qualifier to
include your derived attribute.
Ken
On Apr 16, 2007, at 10:45 AM
Hi!
Is it possible to do a FetchSpecification over derived attributes?
I tried and I got the error:
java.lang.IllegalStateException: sqlStringForAttribute: attempt to generate
SQL for attribute 'attributeName' on entity 'EntityName' with undefined
column name. You must defi
19 matches
Mail list logo
