tag:blogger.com,1999:blog-2015721107059280399.post862167374937002544..comments2007-05-12T16:11:53.898-07:00Shlomonoreply@blogger.comBlogger3125tag:blogger.com,1999:blog-2015721107059280399.post-46139799280331149642007-05-12T16:11:00.001-07:002007-05-12T16:11:00.001-07:00The key here was that I didn’t have to write or update the DB. Read-only, so there really weren’t any hoops. The only trick was getting the primary keys on the views right. At one point I just used the row count from my select statement to create a primary key (the key wasn’t actually being used by any other tables so I was just jumping through one of ActiveRecord’s hoops).joshhttp://www.blogger.com/profile/01165462366964097266noreply@blogger.comtag:blogger.com,1999:blog-2015721107059280399.post-63879218231901580072007-05-12T16:11:00.000-07:002007-05-12T16:11:00.000-07:00Anders Norås <BR/><BR/>Whether you can use views for persistence depends on which database you’re using. Oracle has materialized views which allows updates to some extent and Microsoft SQL Server supports “updateble views”. I did some experimentation with ORM and views a while ago (http://andersnoras.com/blogs/anoras/archive/2007/03/01/nhibernate-mapping-a-class-to-several-tables.aspx) and found that you have to jump through quick a few hoops to achieve this.<BR/><BR/>Regards,<BR/>Andersjoshhttp://www.blogger.com/profile/01165462366964097266noreply@blogger.comtag:blogger.com,1999:blog-2015721107059280399.post-43132916555600041622007-05-12T16:10:00.000-07:002007-05-12T16:10:00.000-07:00This comment has been removed by the author.joshhttp://www.blogger.com/profile/01165462366964097266noreply@blogger.com