Odoo:修改 Hanyu 資料庫

You are here:
< All Topics
Main_Company 設定消失了

於 ir_model_data 中重新加入 main_company 設定即可修復

刪除過的主倉庫於更新後又跑出來了

需更新 ir_model_data 中 warehouse 的相關設定(假定新生成的為 11,實際使用的為 2)

update ir_model_data set res_id = 2 where name like '%warehouse%' and res_id = 11
大量修改

不過不會成功

do $$
declare
arow record;
begin
for arow in
select
'update '||c.table_name||' set '||c.column_name||' = ''1'' where '||c.column_name||' = ''4'';'
as my_update_query
from (
SELECT *
FROM information_schema.columns
WHERE column_name = 'company_id') c
loop
execute arow.my_update_query;
end loop;
end;
$$;
Select all Tables contain column name = company_id
select
'update '||c.table_name||' set '||c.column_name||' = ''1'' where '||c.column_name||' = ''4'';'
as my_update_query
from (
SELECT *
FROM information_schema.columns
WHERE column_name = 'company_id') c 

 

修改 Company_id

會報錯的語法,但是實際查過並沒有存在 company_id = 4 的 record

#update account_entries_report set company_id = '1' where company_id = '4';
#update account_invoice_report set company_id = '1' where company_id = '4';
#update account_treasury_report set company_id = '1' where company_id = '4';
#update analytic_entries_report set company_id = '1' where company_id = '4';
#update hr_expense_report set company_id = '1' where company_id = '4';
#update hr_timesheet_report set company_id = '1' where company_id = '4';
#update purchase_report set company_id = '1' where company_id = '4';
#update report_mrp_inout set company_id = '1' where company_id = '4';
#update sale_report set company_id = '1' where company_id = '4';
#update stock_history set company_id = '1' where company_id = '4';
#update report_project_task_user set company_id = '1' where company_id = '4';

可以正常執行的語法

update res_currency_rate set company_id = '1' where company_id = '4';
update company_html_rel set company_id = '1' where company_id = '4';
update company_img_rel set company_id = '1' where company_id = '4';
update openupgrade_legacy_9_0_account_account set company_id = '1' where company_id = '4';
update stock_quant set company_id = '1' where company_id = '4';
update resource_calendar_leaves set company_id = '1' where company_id = '4';
update sale_order set company_id = '1' where company_id = '4';
update stock_config_settings set company_id = '1' where company_id = '4';
update sale_shop set company_id = '1' where company_id = '4';
update stock_production_lot_revision set company_id = '1' where company_id = '4';
update stock_warehouse_orderpoint set company_id = '1' where company_id = '4';
update account_aged_trial_balance set company_id = '1' where company_id = '4';
update account_analytic_line set company_id = '1' where company_id = '4';
update hr_timesheet_sheet_sheet set company_id = '1' where company_id = '4';
update sale_order_line set company_id = '1' where company_id = '4';
update wizard_multi_charts_accounts set company_id = '1' where company_id = '4';
update account_balance_report set company_id = '1' where company_id = '4';
update account_common_account_report set company_id = '1' where company_id = '4';
update account_common_partner_report set company_id = '1' where company_id = '4';
update account_common_report set company_id = '1' where company_id = '4';
update account_config_settings set company_id = '1' where company_id = '4';
update account_installer set company_id = '1' where company_id = '4';
update account_fiscal_position set company_id = '1' where company_id = '4';
update account_invoice_line set company_id = '1' where company_id = '4';
update crm_team set company_id = '1' where company_id = '4';
update account_invoice_tax set company_id = '1' where company_id = '4';
update account_analytic_journal set company_id = '1' where company_id = '4';
update res_partner_bank set company_id = '1' where company_id = '4';
update account_journal_period set company_id = '1' where company_id = '4';
update account_invoice set company_id = '1' where company_id = '4';
update account_move_line_reconcile set company_id = '1' where company_id = '4';
update account_bank_statement set company_id = '1' where company_id = '4';
update account_bank_statement_line set company_id = '1' where company_id = '4';
update account_partial_reconcile set company_id = '1' where company_id = '4';
update account_payment_term set company_id = '1' where company_id = '4';
update account_payment set company_id = '1' where company_id = '4';
update account_report_general_ledger set company_id = '1' where company_id = '4';
update ir_sequence set company_id = '1' where company_id = '4';
update account_operation_template set company_id = '1' where company_id = '4';
update account_chart_template set company_id = '1' where company_id = '4';
update account_tax_template set company_id = '1' where company_id = '4';
update account_tax_group set company_id = '1' where company_id = '4';
update account_model set company_id = '1' where company_id = '4';
update account_analytic_account set company_id = '1' where company_id = '4';
update account_journal set company_id = '1' where company_id = '4';
update account_move_line set company_id = '1' where company_id = '4';
update account_voucher_line set company_id = '1' where company_id = '4';
update account_move set company_id = '1' where company_id = '4';
update account_voucher set company_id = '1' where company_id = '4';
update account_fiscalyear set company_id = '1' where company_id = '4';
update account_period set company_id = '1' where company_id = '4';
update accounting_report set company_id = '1' where company_id = '4';
update res_partner set company_id = '1' where company_id = '4';
update resource_calendar set company_id = '1' where company_id = '4';
update ir_values set company_id = '1' where company_id = '4';
update resource_resource set company_id = '1' where company_id = '4';
update openupgrade_legacy_9_0_hr_expense_expense set company_id = '1' where company_id = '4';
update hr_expense set company_id = '1' where company_id = '4';
update hr_holidays_status set company_id = '1' where company_id = '4';
update hr_department set company_id = '1' where company_id = '4';
update hr_job set company_id = '1' where company_id = '4';
update hr_payslip_line set company_id = '1' where company_id = '4';
update hr_payroll_structure set company_id = '1' where company_id = '4';
update hr_payslip set company_id = '1' where company_id = '4';
update hr_salary_rule set company_id = '1' where company_id = '4';
update hr_salary_rule_category set company_id = '1' where company_id = '4';
update hr_contribution_register set company_id = '1' where company_id = '4';
update ir_attachment set company_id = '1' where company_id = '4';
update ir_default set company_id = '1' where company_id = '4';
update ir_header_img set company_id = '1' where company_id = '4';
update ir_header_webkit set company_id = '1' where company_id = '4';
update ir_property set company_id = '1' where company_id = '4';
update stock_warehouse set company_id = '1' where company_id = '4';
update stock_location_route set company_id = '1' where company_id = '4';
update mrp_bom set company_id = '1' where company_id = '4';
update mrp_production set company_id = '1' where company_id = '4';
update stock_picking set company_id = '1' where company_id = '4';
update mrp_routing_workcenter set company_id = '1' where company_id = '4';
update mrp_routing set company_id = '1' where company_id = '4';
update multi_company_default set company_id = '1' where company_id = '4';
update payment_acquirer set company_id = '1' where company_id = '4';
update procurement_rule set company_id = '1' where company_id = '4';
update product_price_history set company_id = '1' where company_id = '4';
update product_pricelist_item set company_id = '1' where company_id = '4';
update product_pricelist_version set company_id = '1' where company_id = '4';
update product_supplierinfo set company_id = '1' where company_id = '4';
update product_template set company_id = '1' where company_id = '4';
update procurement_order set company_id = '1' where company_id = '4';
update project_task_work set company_id = '1' where company_id = '4';
update project_task set company_id = '1' where company_id = '4';
update account_tax set company_id = '1' where company_id = '4';
update product_pricelist set company_id = '1' where company_id = '4';
update stock_move set company_id = '1' where company_id = '4';
update purchase_order_line set company_id = '1' where company_id = '4';
update purchase_order set company_id = '1' where company_id = '4';
update res_users set company_id = '1' where company_id = '4';
update stock_location set company_id = '1' where company_id = '4';
update res_currency set company_id = '1' where company_id = '4';
update stock_inventory set company_id = '1' where company_id = '4';
update stock_location_path set company_id = '1' where company_id = '4';
update stock_inventory_line set company_id = '1' where company_id = '4';
update account_account set company_id = '1' where company_id = '4';
update stock_quant_package set company_id = '1' where company_id = '4';

Dump 有錯誤

[root@postgresql done]# pg_dump –data-only –inserts -U odoo erp > a.tmp
Password:
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: account_account
pg_dump: res_users
pg_dump: res_partner
pg_dump: res_country_state
pg_dump: res_country
pg_dump: res_currency
pg_dump: res_company
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints on this table:
pg_dump: account_account_template
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints on this table:
pg_dump: account_analytic_account
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: account_bank_statement_line
pg_dump: account_voucher
pg_dump: account_move
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints on this table:
pg_dump: account_chart_template
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: account_move_line
pg_dump: account_full_reconcile
pg_dump: account_partial_reconcile
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: account_period
pg_dump: account_fiscalyear
pg_dump: account_journal_period
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints on this table:
pg_dump: account_financial_report
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints on this table:
pg_dump: account_invoice
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: account_journal
pg_dump: res_partner_bank
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints on this table:
pg_dump: account_tax
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints on this table:
pg_dump: account_tax_code_template
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints on this table:
pg_dump: account_tax_group
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints on this table:
pg_dump: account_tax_template
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints on this table:
pg_dump: crm_team
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints on this table:
pg_dump: hr_department
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints on this table:
pg_dump: hr_employee
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints on this table:
pg_dump: hr_employee_category
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints on this table:
pg_dump: hr_holidays
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints on this table:
pg_dump: hr_payroll_structure
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints on this table:
pg_dump: hr_salary_rule
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints on this table:
pg_dump: hr_salary_rule_category
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints on this table:
pg_dump: ir_act_server
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints on this table:
pg_dump: ir_model_fields
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints on this table:
pg_dump: ir_module_category
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints on this table:
pg_dump: ir_ui_menu
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints on this table:
pg_dump: ir_ui_view
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints on this table:
pg_dump: mail_message
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints on this table:
pg_dump: mail_message_subtype
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: mrp_production
pg_dump: stock_move
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints on this table:
pg_dump: mrp_workorder
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: procurement_order
pg_dump: project_task
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: procurement_rule
pg_dump: stock_warehouse
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints on this table:
pg_dump: product_category
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints on this table:
pg_dump: project_project
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints on this table:
pg_dump: stock_picking_type
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints on this table:
pg_dump: stock_location
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints on this table:
pg_dump: stock_quant
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints on this table:
pg_dump: res_partner_category
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints on this table:
pg_dump: stock_picking
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints on this table:
pg_dump: stock_quant_package
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints on this table:
pg_dump: mis_report_instance_period
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: account_account_template
pg_dump: res_currency
pg_dump: res_company
pg_dump: account_chart_template
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: account_bank_statement_line
pg_dump: account_move
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: account_full_reconcile
pg_dump: account_partial_reconcile
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints on this table:
pg_dump: res_partner
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: hr_department
pg_dump: hr_employee
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: ir_act_server
pg_dump: wkf_transition
pg_dump: wkf_activity
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: ir_ui_menu
pg_dump: mail_channel
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: procurement_order
pg_dump: sale_order_line
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: procurement_rule
pg_dump: stock_location_route
pg_dump: stock_warehouse
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints on this table:
pg_dump: project_task
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: purchase_order_line
pg_dump: stock_move
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: account_account_template
pg_dump: account_chart_template
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: account_analytic_journal
pg_dump: res_company
pg_dump: account_journal
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: account_move
pg_dump: account_partial_reconcile
pg_dump: account_full_reconcile
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: procurement_order
pg_dump: stock_warehouse_orderpoint
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: procurement_rule
pg_dump: stock_picking_type
pg_dump: stock_warehouse
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints on this table:
pg_dump: stock_move
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: account_chart_template
pg_dump: res_currency
pg_dump: res_company
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: procurement_order
pg_dump: stock_move
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: stock_picking_type
pg_dump: stock_warehouse
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: account_account
pg_dump: account_account_type
pg_dump: res_users
pg_dump: res_partner
pg_dump: res_country_state
pg_dump: res_country
pg_dump: res_currency
pg_dump: res_company
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: stock_location_route
pg_dump: stock_warehouse
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: account_account
pg_dump: res_currency
pg_dump: res_users
pg_dump: res_partner
pg_dump: crm_team
pg_dump: res_company
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints on this table:
pg_dump: stock_warehouse
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: account_account
pg_dump: res_company
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: res_partner
pg_dump: res_users
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: account_account_template
pg_dump: res_users
pg_dump: res_partner
pg_dump: res_country_state
pg_dump: res_country
pg_dump: res_currency
pg_dump: res_company
pg_dump: account_chart_template
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: account_account_template
pg_dump: account_account_type
pg_dump: res_users
pg_dump: res_partner
pg_dump: res_country_state
pg_dump: res_country
pg_dump: res_currency
pg_dump: res_company
pg_dump: account_chart_template
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: account_analytic_journal
pg_dump: res_users
pg_dump: res_partner
pg_dump: res_country_state
pg_dump: res_country
pg_dump: res_currency
pg_dump: res_company
pg_dump: account_journal
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: account_chart_template
pg_dump: res_users
pg_dump: res_partner
pg_dump: res_country_state
pg_dump: res_country
pg_dump: res_currency
pg_dump: res_company
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: account_chart_template
pg_dump: account_tax_code_template
pg_dump: res_users
pg_dump: res_partner
pg_dump: res_country_state
pg_dump: res_country
pg_dump: res_currency
pg_dump: res_company
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: account_chart_template
pg_dump: res_company
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: res_partner
pg_dump: res_partner_title
pg_dump: res_users
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: product_uom
pg_dump: res_users
pg_dump: res_partner
pg_dump: res_country_state
pg_dump: res_country
pg_dump: res_currency
pg_dump: res_company
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: product_uom
pg_dump: product_uom_categ
pg_dump: res_users
pg_dump: res_partner
pg_dump: res_country_state
pg_dump: res_country
pg_dump: res_currency
pg_dump: res_company
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints on this table:
pg_dump: res_company
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: res_partner
pg_dump: res_country_state
pg_dump: res_users
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: res_company
pg_dump: res_users
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: res_company
pg_dump: res_partner
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: crm_team
pg_dump: res_users
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: res_company
pg_dump: report_paperformat
pg_dump: res_users
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: res_company
pg_dump: stock_location
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: res_partner
pg_dump: res_country
pg_dump: res_users
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: res_company
pg_dump: res_font
pg_dump: res_users
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: res_company
pg_dump: res_currency
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints on this table:
pg_dump: res_users
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: res_company
pg_dump: account_journal
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.
pg_dump: NOTICE: there are circular foreign-key constraints among these tables:
pg_dump: res_users
pg_dump: mail_alias
pg_dump: You might not be able to restore the dump without using –disable-triggers or temporarily dropping the constraints.
pg_dump: Consider using a full dump instead of a –data-only dump to avoid this problem.

Previous Odoo OpenUpgrade 會用到的 SQL 語法紀錄
Next 使用 Openupgrade 升級 Odoo 8.0
Table of Contents