Hello. > On Mon, Mar 29, 2010 at 12:34, sasha<trofim...@gmail.com> wrote: > I'm still not convinced. Sure you can ensure the field is de-facto PK, > but as it's more walking on thin ice than robust design I think you, > as developer, should modify your model accordingly and keep it. How to modify Model for View without pain to repeat this modifying each time when Model is updated from DB? Repeating of changes is same kind of "thin ice" because possible to miss something. > Sometimes I change SSDL parts of model manually. But as I know it's > hack, I watch carefully every my commit to SVN to ensure, it's still > there and makes sense. Thats it. After changing of DB, updating of the Model from db and correction of many views in SSDL it is possible to miss something. So does it have real sense? Using of #KEY# in db looks safer... It looks like standard thing more than like hack...
------------------------------------------------------------------------------ Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev _______________________________________________ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
