It should definitely be read-only. There would be no meaning in trying to write a count of something.
- Sean Oleg Broytmann wrote: > On Fri, Aug 04, 2006 at 10:10:29AM -0500, Rick Flosi wrote: >> I think it might not exist b/c it isn't very SQLObjecty. >> You'd be returning an object with a new field in it, SUM(), which isn't >> part of the SQLObject and probably a subset of the SQLObject fields as >> well. This isn't very OO which is what I think SQLObject was designed for. > > Sean have promised to try to produce a patch, but I am sure it would be > very hard to create a proper sqlobjectish design for this excessive column. > Should the designer add it to sqlmeta.columns? should it be a read-only > property? > > Oleg. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ sqlobject-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
