Hi, Have spent all morning working on this problem I feel a need to add to what I said earlier.
I spent most of the morning trying to get SQLObject to work with a MS-SQL Server view and essentially moving from one error after another. I think adding support for updateable views is a good Idea but it seems somewhat involved. as an alternative I have exposed part of the underlying table as a seperate class (just enough to create instances). at the moment I have defined an explicit method for creating new items. so instead of calling Document(**kw) I need to call Document.new(**kw) if anyone has any ideas on how to hide this difference I would appriciate it. On 4/27/06, konrad Zielinski <[EMAIL PROTECTED]> wrote: > Hi, > > In the application I am working on the base tables did not have the desired > structure, so I created updatable views which have the structure I want to > expose via SQLObject and have taken some pains to ensure that the views > support Inserts and Updates. (The databse is in a SQL Server) > > The problem I have is that the Primary ID's exposed to SQLObject are integers > which are indrectly based on an autoval column. The problem is that the > _hasIdentity function is returning false. > > Temporarily I plan to hack around the prolem by adding soem explicit > tests to the > function to return true for certain tables. > > Would it be a valiable enhancement to add a flag to the sqlmeta class > which can be > used to selectivly avoid the test for soem tables? > > regards > > Konrad > ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642 _______________________________________________ sqlobject-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
