Hi Joe,
If you have a smaller dataset, you can avoid all the nasty JDBC stuff and
achieve the goal using:
public NSArray entities() {
NSArray entities =
EOUtilities.objectsForEntityNamed(session().defaultEditingContext(),
YourEntity.ENTITY_NAME);
return YourEntity.DATE_COLUMN.d
On Jun 1, 2010, at 4:18 PM, Joe Kramer wrote:
Hi Chuck,
Thanks for the response. Generally I avoid "non trivial" things as
much as possible because I'm lazy...oops... I mean keenly focused on
efficiency (that sounds better). But I think in this case the SQL
approach may be worth it. I
Now there is a bit of smart thinking! Make it a prototype and you
retain some measure of database independence.
Chuck
On Jun 1, 2010, at 4:20 PM, Johnny Miller wrote:
Could he follow your advice, about using SQL, and create a derived
column in his model and then use a standard qualifier a
Could he follow your advice, about using SQL, and create a derived column in
his model and then use a standard qualifier against the derived column?
On Jun 1, 2010, at 12:53 PM, Chuck Hill wrote:
>
> On Jun 1, 2010, at 3:30 PM, Joe Kramer wrote:
>
>> Hi all,
>>
>> I may be barking up the wron
Hi Chuck,
Thanks for the response. Generally I avoid "non trivial" things as much as
possible because I'm lazy...oops... I mean keenly focused on efficiency
(that sounds better). But I think in this case the SQL approach may be
worth it. In looking at the EOSQLQualifier docs I see that it is
de
On Jun 1, 2010, at 3:30 PM, Joe Kramer wrote:
Hi all,
I may be barking up the wrong tree here, but I wanted someone to
confirm that for me. I have a simple Person EO with a NSTimestamp
attribute for birthdate. I'm wondering if it is possible to create
a qualifier to get all the people
Hi all,
I may be barking up the wrong tree here, but I wanted someone to confirm
that for me. I have a simple Person EO with a NSTimestamp attribute for
birthdate. I'm wondering if it is possible to create a qualifier to get all
the people whose birthday is in a particular month (May, for exampl
I didn't get an answer to my focused question on how one enables D2W
queries to work against boolean attributes. I'm back to the point of
converting all my boolean's to intBoolean, but as a D2W newbie, I'm
unsure of what I need to do to have "custom d2w components" that will
just work, ie check box
Ok, so I will move back the DB to the physical server to see if the
problem goes away.
On Jun 1, 2010, at 6:34 AM, Pascal Robert wrote:
Hum... And after I started using ERXWOLongResponsePage, I still got
a deadlock, but this time, it says that it's a EODatabaseContext
lock :
Thread t..
On Jun 1, 2010, at 6:34 AM, Pascal Robert wrote:
Hum... And after I started using ERXWOLongResponsePage, I still got
a deadlock, but this time, it says that it's a EODatabaseContext
lock :
Thread t...@92163: (state = BLOCKED)
- java.lang.Object.wait(long) @bci=0 (Interpreted frame)
- java.
We have a component, OSLongResponseComponent, that was extending from
WOLongResponsePage, and now it's extending from ERXWOLongResponsePage.
The only thing we are overriding is valueForKeyPath and
appendToResponse, run() is not overriden.
Um. Just how did you switch to ERXWOLongResponsePage
Um. Just how did you switch to ERXWOLongResponsePage? If you overrode run()
than nothing's gonna happen.
Cheers, Anjo
Am 01.06.2010 um 15:34 schrieb Pascal Robert:
> ERXWOLongResponsePage
___
Do not post admin requests to the list. They will be igno
Hum... And after I started using ERXWOLongResponsePage, I still got a
deadlock, but this time, it says that it's a EODatabaseContext lock :
Thread t...@92163: (state = BLOCKED)
- java.lang.Object.wait(long) @bci=0 (Interpreted frame)
- java.lang.Object.wait() @bci=2, line=474 (Interpreted fra
13 matches
Mail list logo
