Database views fail silently on function fields
Bug #839915 reported by
Martin Collins
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Odoo Server (MOVED TO GITHUB) |
Confirmed
|
Wishlist
|
OpenERP's Framework R&D |
Bug Description
I am creating database views as a basis for reports. I've done three that work fine. The fourth does not. When I click on its menu item I get this error:
ProgrammingError: relation "citrus_
LINE 1: SELECT "citrus_
Sure enough, the view is not in the database.
Now I've gone through my code, the query works fine in pgadmin, if I make _auto=True I get a working object, the field names and types all match.
Stepping through in the debugger I see that the view is created in the database but then it gets dropped again. I cannot see why, or how. What could cause this?
Changed in openobject-server: | |
assignee: | nobody → OpenERP's Framework R&D (openerp-dev-framework) |
importance: | Undecided → Wishlist |
status: | New → Confirmed |
To post a comment you must log in.
I have discovered that it is a function field in my query that causes this problem, even though it is stored and PostgreSQL has no problem making a view with it.
I think this should be allowed, and furthermore a meaningful message should be given if a (non-stored) function field is used in a view query.
I'm running 6.0.3 BTW.