| 2010-09-27 10:10:59 |
Guewen Baconnier @ Camptocamp |
bug |
|
|
added bug |
| 2010-09-27 10:11:57 |
Guewen Baconnier @ Camptocamp |
description |
Hello,
As the attributes are managed today (one column per attribute in the product_product table), if the number of Magento's attributes is over 1600, the synchronisation won't work because the number of columns in PostgreSQL is limited to 1600 columns per table.
1600 attributes may seem incredible, but we have a client which is near this limit with ~1300 attributes.
I don't have a solution, but I guess that a reflexion should be done.
Thank you
Guewen |
Hello,
As the attributes are managed today (one column per attribute in the product_product table), if the number of Magento's attributes is over 1600, the synchronisation won't work because the number of columns in PostgreSQL is limited to 1600 columns per table.
1600 attributes may seem incredible, but we have a client which is near this limit with ~1300 attributes.
I don't have any solution, but I guess that a reflexion should be done.
Thank you
Guewen
|
|
| 2010-09-27 10:12:30 |
Guewen Baconnier @ Camptocamp |
description |
Hello,
As the attributes are managed today (one column per attribute in the product_product table), if the number of Magento's attributes is over 1600, the synchronisation won't work because the number of columns in PostgreSQL is limited to 1600 columns per table.
1600 attributes may seem incredible, but we have a client which is near this limit with ~1300 attributes.
I don't have any solution, but I guess that a reflexion should be done.
Thank you
Guewen
|
Hello,
As the attributes are managed today (one column per attribute in the product_product table), if the number of Magento's attributes is over 1600, the synchronisation won't work because the number of columns in PostgreSQL is limited to 1600 columns per table.
1600 attributes may seem incredible, but we have a client which is near this limit with ~1300 attributes.
I don't have any solution yet, but I guess that a reflexion should be done.
Thank you
Guewen
|
|
| 2010-09-27 10:40:10 |
Guewen Baconnier @ Camptocamp |
description |
Hello,
As the attributes are managed today (one column per attribute in the product_product table), if the number of Magento's attributes is over 1600, the synchronisation won't work because the number of columns in PostgreSQL is limited to 1600 columns per table.
1600 attributes may seem incredible, but we have a client which is near this limit with ~1300 attributes.
I don't have any solution yet, but I guess that a reflexion should be done.
Thank you
Guewen
|
Hello,
As the attributes are managed today (one column per attribute in the product_product table), if the number of Magento's attributes is over 1600, the synchronisation won't work because the number of columns in PostgreSQL is limited to 1600 columns per table.
1600 attributes may seem incredible, but we have a client which is near this limit with ~1400 attributes.
I don't have any solution yet, but I guess that a reflexion should be done.
Thank you
Guewen
|
|
| 2010-09-30 01:33:16 |
Raphaël Valyi - http://www.akretion.com |
magentoerpconnect: importance |
Undecided |
Medium |
|
| 2010-10-08 06:25:06 |
Guewen Baconnier @ Camptocamp |
summary |
1600 attributes limitation |
1600 attributes limitation + performance issue |
|
| 2010-11-08 22:57:16 |
Raphaël Valyi - http://www.akretion.com |
magentoerpconnect: status |
New |
Confirmed |
|
| 2010-11-10 09:47:45 |
Guewen Baconnier @ Camptocamp |
branch linked |
|
lp:~jgrandguillaume-c2c/magentoerpconnect/magentoerpconnect_optimized |
|
| 2011-09-26 07:42:41 |
Sébastien BEAU - http://www.akretion.com |
magentoerpconnect: status |
Confirmed |
Fix Released |
|
