OK, it is definitely megrok.rdb, the last thing it does is call metadata.create_all() so, I will email the megrok folks. Thanks a bunch.
-- Jeffrey D Peterson Webmaster Crary Industries, Inc. -----Original Message----- From: sqlalchemy@googlegroups.com [mailto:sqlalch...@googlegroups.com] On Behalf Of Jeff Peterson Sent: Monday, January 11, 2010 3:14 PM To: sqlalchemy@googlegroups.com Subject: RE: [sqlalchemy] Oracle, ownership and unrecognized type warnings Hmmm, must be something megrok.rdb is doing I am not seeing, I will look into it. -- Jeffrey D Peterson Webmaster Crary Industries, Inc. -----Original Message----- From: sqlalchemy@googlegroups.com [mailto:sqlalch...@googlegroups.com] On Behalf Of Michael Bayer Sent: Monday, January 11, 2010 2:31 PM To: sqlalchemy@googlegroups.com Subject: RE: [sqlalchemy] Oracle, ownership and unrecognized type warnings Jeff Peterson wrote: >> its true that there's no built in functionality to reflect views. In >> the case of your views, just create Table instances manually, >> specifying the >> view names, column names, and column types explicitly. Set the >> "primary_key=True" flag on those columns which you'd like to consider as >> part of the primary key within your application. No database change is >> necessary. > > > So, does doing this actually create a new table in the DB? no. SQLAlchemy never creates tables unless you tell it to. By "create", i meant, "sometable = Table(...)", i.e., you are creating a Python object in your application which represents the structure of a table or view that is present in the database. *Not* calling table.create().
-- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalch...@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
