Hi, Steven,
I've used the formula you described in a WO application a while back
and did all the work in Java. Basically this meant, when the
application started up, caching a table of all the geographic points
in which I was interested in three Java arrays: latitude[], longitude
[] and ke
One really neat solution for doing such things is having a stored
procedure which fills in a temporary table. Can't remember the Oracle
name of those. They are private to a session and disappear when the
session is closed.
The stored procedure computes a unique ID and returns it. That same
I see! I'd wondered why those constants were getting tossed in
there. That's very fancy! Thanks guys!
Mark
On Jul 4, 2007, at 5:44 PM, Ken Anderson wrote:
Are you using EOGenerator? It creates constants for you for all
the names of your attributes. So, you would construct one like this
On 04.07.2007, at 15:28, Steven Mark McCraw wrote:
I can appreciate this, but there are times when you absolutely
cannot do your processing in Java.
That's what raw queries or your own qualifiers are for.
cug
___
Do not post admin requests to the l
You create them using instances of EOKeyValueQualifier,
EOAndQualifier, EOOrQualifier, etc. All qualifierWithQualifierFormat
does is build this structure for you... sometimes poorly.
On Jul 4, 2007, at 5:28 PM, Steven Mark McCraw wrote:
How do you create your qualifiers if not with
qualif
On Jul 4, 2007, at 5:15 PM, Pierre Bernard wrote:
I feel the urge to voice opinions about this.
- EOF is an ORM not a SQL generator. Its task is to allow you to
work in a pure OO work and make object graph management and
persistent transparent. Meaning: you want to do your processing in
I feel the urge to voice opinions about this.
- EOF is an ORM not a SQL generator. Its task is to allow you to work
in a pure OO work and make object graph management and persistent
transparent. Meaning: you want to do your processing in Java, not in
the database.
- You are free to extend E
I can appreciate that breadth of functionality indeed, but it
obviously comes at the sacrifice of relational database-specific
functionality. It would be nice if EOF (and I guess by EOF here,
what I really mean is EOQualifier or some variant) went to greater
pains to accommodate what is (I
Apparently EOF considers even subtraction to be a database specific
task, and I guess the thought is that somehow this ruins database
independence.
It's not that it "somehow" ruins it, it just "does" ruin it. EOF is
not just database vendor independent, it's literally datastore
independent
Okay, after googling for another half hour or so, I think I can
answer my own question. You absolutely cannot use EOQualifier to
fetch EOs with an expression like the one I want to write.
Apparently EOF considers even subtraction to be a database specific
task, and I guess the thought is
Hi all,
Does anyone know why I can't build an arbitrarily complex qualifier
with EOF?
The following code
CCGGregorianCalendar now = new CCGGregorianCalendar();
now.setMonth(now.getMonth() + 3);
args.addObject(now.timestamp());
a
11 matches
Mail list logo
