Persistance using attributes, reflection and inheritance

[Tilted]

As I'm not working on many c# projects at the moment I thought I'd spend
some time investigating the subject line.

Getting quite close to a conclusion, it works, it's a little slow (but still
in development), supports 1:1, 1:m, m:m relationships etc.

I've seen several "previews" of ObjectSpaces, i.e. people who've created a
cut down version of the final implementation MS will give and none of them
use this method. I can see why custom attributes, inherticance etc. may put
people off but I would be interested in discovering any other issues you
guys have with this type of implementation.

I'm looking at using my app as a prototyping tool initialy, but given time
it may be viable as a valid data tier.

Any views appreciated.

Chris.

[Scott Allen]

It certainly sounds interesting. As soon as I hear "reflection"
though, I think "slow".

--
Scott
http://www.OdeToCode.com/blogs/scott/

On Wed, 24 Nov 2004 23:25:10 -0000, "Tilted" <pu***@gvygrq.pb.hx
(ROT13)> wrote:

As I'm not working on many c# projects at the moment I thought I'd spend
some time investigating the subject line.

Getting quite close to a conclusion, it works, it's a little slow (but still
in development), supports 1:1, 1:m, m:m relationships etc.

I've seen several "previews" of ObjectSpaces, i.e. people who've created a
cut down version of the final implementation MS will give and none of them
use this method. I can see why custom attributes, inherticance etc. may put
people off but I would be interested in discovering any other issues you
guys have with this type of implementation.

I'm looking at using my app as a prototyping tool initialy, but given time
it may be viable as a valid data tier.

Any views appreciated.

Chris.

[Tilted]

True it is slow.

But how much slower is something I need to look into, I know there are
several techniques I need to use to speed it up. It's not even close to
being ready for human consumption yet as my investigations tend to get dirty
and the code suffers a little.

There are a few others who've tried this technique but I don't think they've
explored it as deeply as I have. Probably because it was too slow, we'll
see.

Thanks for the input anyway.

Chris

"Scott Allen" <bitmask@[nospam].fred.net> wrote in message
news:2g********************************@4ax.com...

It certainly sounds interesting. As soon as I hear "reflection"
though, I think "slow".

--
Scott
http://www.OdeToCode.com/blogs/scott/

On Wed, 24 Nov 2004 23:25:10 -0000, "Tilted" <pu***@gvygrq.pb.hx
(ROT13)> wrote:

As I'm not working on many c# projects at the moment I thought I'd spend
some time investigating the subject line.

Getting quite close to a conclusion, it works, it's a little slow (but
still
in development), supports 1:1, 1:m, m:m relationships etc.

I've seen several "previews" of ObjectSpaces, i.e. people who've created a
cut down version of the final implementation MS will give and none of them
use this method. I can see why custom attributes, inherticance etc. may
put
people off but I would be interested in discovering any other issues you
guys have with this type of implementation.

I'm looking at using my app as a prototyping tool initialy, but given time
it may be viable as a valid data tier.

Any views appreciated.

Chris.