Hello, I'd like to be able to "seemlessly" use sqlobjects that maps to SQL views. As views are very close to tables I manage to just reuse the code of createTable and redefine createTableSQL in my "view object" in order to have the correct "CREATE VIEW ...".
The problem is that SQLObject.createTableSQL seems to never be used: in fact, SQLObject.createTable calls DBAPI.createTable that calls DBAPI.createTableSQL. So in order to create the view I have to call something like this "conn.query(MyViewObject.createTableSQL())" but I cannot simply call "MyViewObject.createTableSQL()". Well, this is no big deal but I would find it cleaner to call the latter. So my question : what is the purpose of SLQObject.createTableSQL? Shouldn't SQLObject.createTable call SQLObject.createTableSQL (which already calls DBAPI.createTableSQL by the way) then make the conn.query(sql) by itself rather than "delegating" it to DBAPI.createTable? I'm using rev 2030 with python 2.5 and sqlite3. -- jt ------------------------------------------------------------------------- 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&kid=120709&bid=263057&dat=121642 _______________________________________________ sqlobject-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
