Jeffrey Becker wrote: > ORM is always a tricky business. My experience is that unless the > entity is very very simple, it's often inappropriate to attempt to do > 1 row = 1 entity mapping. If things are collections of points, then > by all means have a points table. A lot of this type of stuff can be > made easier by 1) really understanding your object-model first and 2) > comming up with good mapping strategies for your objects. > Jeffrey,
Thanks for the input. In this case, the RAW geometry really can be defined via a series of points, though an attribute or two would be required in a few cases. For instance, I can define a basic arc with 3 points (start, center, end), but I need a direction (CW or CCW) to complete the definition. Since I already have a requirement to store other attributes, that's probably not a show-stopper. You're right though, I really need to think some more on the overall mapping strategy. Thanks again for the input. Jeff _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
