I have been using a datamodel with
reservation<-> voucher for some time.
Most of the time a reservation has to be created, sometimes a voucher.
Most of the vouchers are already in the database.
The way I save the data is to create a reservation, select a voucher,
and then add the voucher to t
Well, I did a defaults read com.apple.safari and then searched for
timeout and nothing. I also read through all the setting and I can't
find anything that seems relevant.
I'm currently searching in google.
On May 30, 2008, at 9:32 PM, Art Isbell wrote:
On May 30, 2008, at 2:07 PM, Ric
On May 30, 2008, at 2:07 PM, Ricardo Parada wrote:
I connect to my WO application using Safari. My WO application is
connected to a remote database. So my app runs slow.
As a result of this Safari is giving me a timeout error saying that
the server is not responding.
I had set a preferenc
Direct connect
On May 30, 2008, at 5:14 PM, Chuck Hill wrote:
Direct connect or through Apache?
On May 30, 2008, at 5:07 PM, Ricardo Parada wrote:
I connect to my WO application using Safari. My WO application is
connected to a remote database. So my app runs slow.
As a result of thi
Am I simply doing something wrong, or have I discovered a bug?I have
a localized project. In the Application constructor, I set
Survey says "doing something wrong". You're only setting one of the
values that matters. Instead set the property:
er.extensions.ERXApplication.DefaultEncoding=UT
Hi everyone,
Am I simply doing something wrong, or have I discovered a bug?I have a
localized project. In the Application constructor, I set
WOMessage.setDefaultEncoding("UTF8");
Which works fine up to where
-takeValuesFromRequest
gets called on the session object. At that point, the
f
Now I'm just going to have to go look into fixing this in Wonder.
How much effort is expended being scared of inverse faulting (which
is a problem that seems like it really shouldn't be all THAT hard to
fix with a little elbow grease)?
It will definitely take a little more magic to pull of
It's VERY rare that I have the relationship modeled but don't want
the graph in sync.
We actually do it a lot. If you think about our system there are
some apps that spend 99% of their time
inserting data (think of when something is sold) and there are
others that spend 99% of their time r
Direct connect or through Apache?
On May 30, 2008, at 5:07 PM, Ricardo Parada wrote:
I connect to my WO application using Safari. My WO application is
connected to a remote database. So my app runs slow.
As a result of this Safari is giving me a timeout error saying that
the server is not
I connect to my WO application using Safari. My WO application is
connected to a remote database. So my app runs slow.
As a result of this Safari is giving me a timeout error saying that
the server is not responding.
I had set a preference in Terminal using defaults write
com.apple.safari
On May 30, 2008, at 5:19 PM, Mike Schrag wrote:
So, my memory is still not 100% clear on this one but I think
we're honing in on why I don't flatten
If the relationship is not flattened then I have the option of not
using addObjectToBothSides if I know
I am doing an insert and then disca
On May 30, 2008, at 4:06 PM, Alan Ward wrote:
On May 30, 2008, at 4:54 PM, Mike Schrag wrote:
OK, so it sounds like the update is fine but how many SQL
statements occur when you try to insert a new Person?
I would expect an insert to fire the faults in this case, but that
should be the sa
So, my memory is still not 100% clear on this one but I think we're
honing in on why I don't flatten
If the relationship is not flattened then I have the option of not
using addObjectToBothSides if I know
I am doing an insert and then discarding the EO (i.e. I don't care
about keeping my
On May 30, 2008, at 4:54 PM, Mike Schrag wrote:
OK, so it sounds like the update is fine but how many SQL
statements occur when you try to insert a new Person?
I would expect an insert to fire the faults in this case, but that
should be the same for a many-to-many with a join entity as long
On May 30, 2008, at 3:35 PM, Alan Ward wrote:
OK, so it sounds like the update is fine but how many SQL statements
occur when you try to insert a new Person?
Should be the same, flattened or not flattened:
1. Fetch the Person
2. Fetch the PK for each company to create an array of company
OK, so it sounds like the update is fine but how many SQL statements
occur when you try to insert a new Person?
I would expect an insert to fire the faults in this case, but that
should be the same for a many-to-many with a join entity as long as
you are calling addObjectToBothSideBlah on bot
On May 30, 2008, at 3:14 PM, Alan Ward wrote:
On May 30, 2008, at 3:43 PM, Mike Schrag wrote:
I'm sure Chuck will correct me if I'm wrong but my recollection
is that a flattened to-many will always trip on an insert or
update.
Hmm. What you mean by "trip on"?
Pretty sure Alan is saying
OK, so it sounds like the update is fine but how many SQL statements
occur when you try to insert a new Person?
Alan
On May 30, 2008, at 4:28 PM, Mike Schrag wrote:
No, I meant an insert or update that didn't modify the
relationship. It sounds like your test shows my recollection to
be
No, I meant an insert or update that didn't modify the
relationship. It sounds like your test shows my recollection to be
wrong
with recent WO versions. I'm pretty sure it was true at some point
in the past though.
Hang on a minute what was flattened in your model?
Company
id
On May 30, 2008, at 4:14 PM, Alan Ward wrote:
On May 30, 2008, at 3:43 PM, Mike Schrag wrote:
I'm sure Chuck will correct me if I'm wrong but my
recollection is that a flattened to-many will always trip on
an insert or update.
Hmm. What you mean by "trip on"?
Pretty sure Alan is saying
On May 30, 2008, at 3:43 PM, Mike Schrag wrote:
I'm sure Chuck will correct me if I'm wrong but my recollection
is that a flattened to-many will always trip on an insert or
update.
Hmm. What you mean by "trip on"?
Pretty sure Alan is saying that updating or inserting an EO with
a flatten
Now it _would_ be nice if EOF could just add / remove and mark the
snapshot as partial or something to avoid this overhead.
Once every 6 months I think that I should try to fix this in Wonder,
but at this point I think Pierre would physically attack me at WWDC if
I try to do this :)
ms
___
On May 30, 2008, at 1:59 PM, Alan Ward wrote:
I'm sure Chuck will correct me if I'm wrong but my recollection is
that a flattened to-many will always trip on an
insert or update.
Any to many, flattened or not, will fire the array fault (but not fire
the faults in the array) when an elem
I'm sure Chuck will correct me if I'm wrong but my recollection
is that a flattened to-many will always trip on an insert or
update.
Hmm. What you mean by "trip on"?
Pretty sure Alan is saying that updating or inserting an EO with a
flattened to-many fires the fault of the to-many. This wo
I'm sure Chuck will correct me if I'm wrong but my recollection is
that a flattened to-many will always trip on an insert or update.
Hmm. What you mean by "trip on"?
Pretty sure Alan is saying that updating or inserting an EO with a
flattened to-many fires the fault of the to-many. This woul
I'm sure Chuck will correct me if I'm wrong but my recollection is
that a flattened to-many will always trip on an insert or update.
Hmm. What you mean by "trip on"?
Pretty sure Alan is saying that updating or inserting an EO with a
flattened to-many fires the fault of the to-many. This woul
On 30.05.2008, at 14:59, Alan Ward wrote:
I'm sure Chuck will correct me if I'm wrong but my recollection is
that a flattened to-many will always trip on an insert or update.
Hmm. What you mean by "trip on"?
Guido
--
http://www.event-s.net
___
Do
I'm sure Chuck will correct me if I'm wrong but my recollection is
that a flattened to-many will always trip on an
insert or update.
Alan
On May 30, 2008, at 2:48 PM, Guido Neitzer wrote:
On 30.05.2008, at 14:31, Alan Ward wrote:
I actually omit joins from the model in certain situations
On 30.05.2008, at 14:31, Alan Ward wrote:
I actually omit joins from the model in certain situations to avoid
unwanted fetches and flattening is more of a recipe for disaster
than a simple join is.
But it actually doesn't matter how big your datasets are. The
interesting question is how
Like I was saying to Mike, it's simply a guard against performance
issues. It's like omitting inverse relationships
when you know that it would be suicide if anyone tried to traverse
(or inadvertently tripped) them.
e.g. transaction -> user_agent is a fine relationship to model but
would you
On May 30, 2008, at 2:32 PM, Chuck Hill wrote:
On May 30, 2008, at 1:19 PM, Mike Schrag wrote:
IMHO you should never flatten a many-to-many (especially across
models).
So this is interesting ... I held this same belief for years until
about 6 months ago when Chuck convinced me that I was
On May 30, 2008, at 1:19 PM, Mike Schrag wrote:
IMHO you should never flatten a many-to-many (especially across
models).
So this is interesting ... I held this same belief for years until
about 6 months ago when Chuck convinced me that I was missing
out :) I had some silly misunderstandin
I'm actually somewhat opposed to flattening in any situation but when
it comes to M-to-M
my justification is more performance related than anything else. I
actually omit joins from
the model in certain situations to avoid unwanted fetches and
flattening is more of a recipe
for disaster tha
IMHO you should never flatten a many-to-many (especially across
models).
So this is interesting ... I held this same belief for years until
about 6 months ago when Chuck convinced me that I was missing out :)
I had some silly misunderstanding of EOF caching with respect to
flattened relati
IMHO you should never flatten a many-to-many (especially across models).
Alan
On May 30, 2008, at 1:47 PM, Gennady Kushnir wrote:
Flattening relationshops (consequently - many-to-many relations) does
not work across database (consequently - EOModel) boundaries
Unfortunately.
It is mentioned i
Flattening relationshops (consequently - many-to-many relations) does
not work across database (consequently - EOModel) boundaries
Unfortunately.
It is mentioned in Using EOModeler manual. So you have to traverse
relationships programmatically I assume.
Gennady
2008/5/29 Juergen Lorenz Simon <[EM
The other possibility is that the model with the subclasses is not
getting loaded. Maybe not under Resources/ in the Eclipse built
framework?
On May 30, 2008, at 12:44 PM, Jean-François Veillette wrote:
I have never needed the qualifier before.
This is a project freshly switched from xcod
On May 30, 2008, at 12:35 PM, Jean-François Veillette wrote:
More details ...
single table inheritance,
no restricting qualifiers, there is only one concrete entity for one
abstract entity.
I have never used it like that. I expected that you would still need
the restricting qualifier.
On May 30, 2008, at 11:17 AM, Jean-François Veillette wrote:
I have 2 models, one which contain a set of abstract eoentity,
another one which contain a set of concret eoentity (subclasses of
the abstract set).
It was working just right, but suddently after reinstalling one of
the framewo
I have 2 models, one which contain a set of abstract eoentity,
another one which contain a set of concret eoentity (subclasses of
the abstract set).
It was working just right, but suddently after reinstalling one of
the framework, it just stopped working. I can't make it work again.
Whenev
This maybe an easy question, but I could not think of the answer right
now. The constants for EOQualifier (i.e. QualifierOperatorEquals) are
of type NSSelector. However, NSSelector is defined as NSSelector so
the compiler wants me to give it a type when I reference it. So that I
can get rid
My guess is that you are doing the insert twice in the same
transaction. The transaction is then rolled back and consequently you
can manually insert the same values with no violation of the
uniqueness constraint. Turn on EOAdaptorDebugEnabled and
watch the SQL that's generated to get a be
It's a SQL error so the complaint is from your DB.
I would try dropping the contents of your EO PK table and see if it
goes away.
Simon
On 30 May 2008, at 17:38, Amedeo Mantica wrote:
I got this error:
[2008-5-30 18:31:43 CEST]
com.webobjects.eoaccess.EOGeneralAdaptorException:
Eval
I got this error:
[2008-5-30 18:31:43 CEST]
com.webobjects.eoaccess.EOGeneralAdaptorException: EvaluateExpression
failed: "INSERT INTO INDBLocalizedString(it, de, id, en) VALUES (?, ?, ?, ?)"
withBindings: 1:"write ITghgf"(it), 2:"write DE"(de), 3:128(id),
4:"write EN"(en)>:
Next ex
44 matches
Mail list logo
