Thanks for all the suggestions. I'm going to digest this and
reformulate my model. I'll let you know how it goes.
Hmmm... It's nice to be involved in WO again. Good programming. Good
folks.
Jaime Magiera
Sensory Research
http://www.sensoryresearch.net
_
On 07.05.2008, at 13:33, Tonny Staunsbrink wrote:
I too have been in trouble when working with inheritance in eof. I
think the only reason for using inheritance in the eo model is in
case you want to make sql based (datebase based) queries at the base
of the inheritance hierarchy. In all ot
In fact, Mike - since I don't have the time to participate actively
on the lists it's difficult to get gratitude across - but still,
your code is responsible for a whole lot of critical government
systems up here in Iceland. And hopefully, that will increase even
more soon, since we are ope
I haven't actually checked out ERTaggable yet. Is it good?
Is it GOOD? Come on, now :)
Lol, sorry Mike. Checking it out now :-).
It does require Wonder buy-in, though ... If you're not using the
rest of Wonder, you're on your own :)
Oh trust me, I'm using Wonder. Seriously, I don't thin
I too have been in trouble when working with inheritance in eof. I think the
only reason for using inheritance in the eo model is in case you want to
make sql based (datebase based) queries at the base of the inheritance
hierarchy. In all other circumstances i would try to avoid inheritance.
Note t
I've long since stopped trying to use inheritance since I always
seem to run into trouble. So my advice is always to stay away from
it - which is a shame since it sounds cool - and perhaps it's just
me and my lacklustre programming skills - but I never found it
worth the complexity.
FWIW,
I haven't actually checked out ERTaggable yet. Is it good?
Is it GOOD? Come on, now :)
Lol, sorry Mike. Checking it out now :-).
It does require Wonder buy-in, though ... If you're not using the rest
of Wonder, you're on your own :)
ms
___
Do n
I haven't actually checked out ERTaggable yet. Is it good?
Is it GOOD? Come on, now :)
Lol, sorry Mike. Checking it out now :-).
- h
// Hugi Thordarson
// http://hugi.karlmenn.is/
___
Do not post admin requests to the list. They will be ignored.
I haven't actually checked out ERTaggable yet. Is it good?
Naw, Mike wrote it. It's shite. :-P
LOL - yup. That guy's a real pain :-).
Anyway.
I've long since stopped trying to use inheritance since I always
seem to run into trouble. So my advice is always to stay away from
it - which
I haven't actually checked out ERTaggable yet. Is it good?
Is it GOOD? Come on, now :)
I use it in almost all of our apps, now ... It's inspired by
acts_as_taggable from Rails, and I tried to come up with the way to
make it as minimally invasive as possible (meaning -- you do the least
am
On May 7, 2008, at 11:55 AM, Hugi Þórðarson wrote:
I haven't actually checked out ERTaggable yet. Is it good?
Naw, Mike wrote it. It's shite. :-P
Anyone have good usage examples? I'm curious, since what comes out
of Wonder is usually at the very least conceptually interesting.
(and it
I haven't actually checked out ERTaggable yet. Is it good? Anyone have
good usage examples? I'm curious, since what comes out of Wonder is
usually at the very least conceptually interesting. (and it's f***-ing
discouraging to have a couple of developers pump out new features
faster than I h
Hi!
The first idea that comes to my mind is a Characteristic entity
(name might not be the best one, remember I'm not a native english
speaker) with a code or name to identify which is it (color, size,
etc) and a value. Then, relation To-Many from product to characteristic.
Yours
Mig
You could use a tagging system. Wirehose has such a thing and I think
that Wonder does too.
You could then use the tags to even drill to a set of products.
The tags could have validation logic based upon the type of product.
Just some thoughts.
James Cicenia
On May 7, 2008, at 1:21 PM, Jai
Heyya,
This is slightly off-topic, but I figure fellow WO developers might
have input: I'm rewriting the store functionality of ThoughtConduit
and need to decide on a more refined version of my EOModel. In
particular, I want Products to be able to handle things such as size
and color (for
15 matches
Mail list logo
