On Jan 6, 2010, at 2:22 PM, Michael Bayer wrote:
its true that there's no built in functionality to reflect views.
Correction. The 0.6 release, currently in trunk, has the capacity to reflect
views fully in the same way as tables. Although constraints such as primary
and foreign keys
Subject: Re: [sqlalchemy] Oracle, ownership and unrecognized type warnings
crary_web wrote:
For production I will need to connect as user webserv who has no
ownership at all only select grants, and will only have access to
views. Currently, with what I have deciphered for myself, I can't do
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
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
] 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
crary_web wrote:
For production I will need to connect as user webserv who has no
ownership at all only select grants, and will only have access to
views. Currently, with what I have deciphered for myself, I can't do
this. I cannot reflect a view at all, it complains about primary keys
