c2c-oerpscenario team mailing list archive

[Raphaël Valyi - http://www.akretion.com <667735@xxxxxxxxxxxxxxxxxx>]

Hello Raimon, you are absolutely right!

I'll apply your patch


On Wed, Jan 12, 2011 at 1:29 PM, Raimon Esteve (Zikzakmedia) <
resteve@xxxxxxxxxxxxxxx> wrote:

> OpenERP 6 rc2
>
> ProgrammingError: column stock_move.date_planned does not exist
> LINE 1: SELECT "stock_move".id FROM "stock_move" WHERE (stock_move.d..
>
> If you see psql, stock_move table don't exist date_planned field. (it's
> rename date_planned to date in OpenERP 6?)
>
> This code is necessary update in sale.py of base_sale_multichannels.
> Replace date_planned to date.
>
>            if shop.last_inventory_export_date:
>                recent_move_ids = self.pool.get('stock.move').search(cr,
> uid, [('date', '>', shop.last_inventory_export_date), ('product_id', 'in',
> product_ids), ('state', '!=', 'draft'), ('state', '!=', 'cancel')])
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/667735
>
> Title:
>   OpenERP fixed stock_move.date_planned typo on OpenERP v6, we are
>  impacted.
>
> Status in Magento Open ERP Connector:
>  New
>
> Bug description:
>  Hello,
>
>  Looks like OpenERP SA finally took care of that renaming the
>  stock_move.date_planned field into stock_move.date_expected on OpenERP
>  v6.
>
>  the magentoerpconnect module should follow that change on the v6
>  serie. A trivial sed script will do it.
>
>  We should ensure that date_expected is what stands for date_planned
>  though.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/magentoerpconnect/+bug/667735/+subscribe
>

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/667735

Title:
  OpenERP fixed stock_move.date_planned typo on OpenERP v6, we are
  impacted.

Status in Magento Open ERP Connector:
  New

Bug description:
  Hello,

  Looks like OpenERP SA finally took care of that renaming the
  stock_move.date_planned field into stock_move.date_expected on OpenERP
  v6.

  the magentoerpconnect module should follow that change on the v6
  serie. A trivial sed script will do it.

  We should ensure that date_expected is what stands for date_planned
  though.