Add indices to PostgreSQL tables in custom module: Is overriding _auto_init and using _execute_sql the best way?
For a module I am writing, a new model based on a SQL view performs poorly unless I add some indices to the account_invoice, account_move_line and account_voucher tables in PostgreSQL.
What is the best way for my module to add these same indices?
I know how to do this via overriding _auto_init and using _execute_sql.
Is there another way? A better way?
I have used another way for creating indices on the columns which I want into particular model.
I have just inherit that columns of a particular model and put the "select=True" into column defination like below.
'product_id':fields.many2one('product.product', 'Product', select=True),
System will automatically made an index on the product_id column of inherited model.
Please try to give a substantial answer. If you wanted to comment on the question or answer, just use the commenting tool. Please remember that you can always revise your answers - no need to answer the same question twice. Also, please don't forget to vote - it really helps to select the best questions and answers!
About This Community
|Asked: 5/9/14, 8:30 PM|
|Seen: 1827 times|
|Last updated: 3/16/15, 8:10 AM|