Hi Ashant, well. Technically we don't access the ERP directly in this case, but a custom middleware of the customer. (That also includes intrusion detection.) In general we often access an internal ERP interface for such cases as the order history. Usually that is not so bad, because it is limited to logged-in customers and limited to a few orders at a time. But you are right of course. The ERP needs to be able to handle that additional amount of data.
Regards from Freiburg, Sven Brunk Von: dev-general-boun...@lists.oxidforge.org [mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von ash...@euroblaze.de Gesendet: Montag, 10. August 2015 18:09 An: dev-general@lists.oxidforge.org Betreff: Re: [oxid-dev-general] OXID eShop versions 4.9.5 and 5.9.5 released [T-7VCHMPB2L9-57] Hello Keywan, Dirk and everyone, unfortunately we don’t have a project with such a “good problem”:) But if we had, we would have dumped the old orders and order-articles into a NoSQL database, and purged the SQL tables. You could even do this yearly. Btw: personally, I think fetching data from ERP directly for the webshop isn’t a risk-free idea. (Downside: performance hit on ERP, performance hit on shop and risk of a tailored attack on the ERP, say to siphon customer-records out on one deep winter night..). Regards from Stuttgart! Ashant Chalasani On 10 Aug 2015, at 11:21, Keywan Ghadami wrote: Hi Dirk, in a project i am working on we do not store the orders in the database. Instead we have a custom myaccount page that fetches the orderlist from the erp (ajax). We do not have had any problems with that solution yet. Best regards keywan Keywan Ghadami Software-Entwickler Professional Services Von: dev-general-boun...@lists.oxidforge.org<mailto:dev-general-boun...@lists.oxidforge.org> [mailto:dev-general-boun...@lists.oxidforge.org<mailto:dev-general-boun...@lists.oxidforge.org>] Im Auftrag von Dirk Weimar | design3000.de Gesendet: Montag, 10. August 2015 11:17 An: dev-general@lists.oxidforge.org<mailto:dev-general@lists.oxidforge.org> Cc: dev-general@lists.oxidforge.org<mailto:dev-general@lists.oxidforge.org> Betreff: Re: [oxid-dev-general] OXID eShop versions 4.9.5 and 5.9.5 released [T-7VCHMPB2L9-57] Hi everybody, our 'order' and 'orderarticles' tables have grown quite big, which dramatically slows down database interactions with these tables. For example, it takes several minutes adding a new field to those tables when installing a module. So my question is: Is it best practise to delete old orders from oxid db? As far as I can see, the only reason to keep them is because we want to show the order history to the customer on his "account" page -- but we could instead pull them directly from the ERP (Pixi) when a customer tries to access them. So does anybody of you delete old orders in oxid? Are there any pitfalls when doing so? Reagards Dirk -- ashant chalasani | euroblaze Industriestrasse 24b, D-70565 Stuttgart, Germany t: +49-711-7947-2394 w: http://www.euroblaze.de Registergericht: Stuttgart, HRB 22736 (Fa. Wapsol GmbH) Geschäftsführer: Ashant Chalasani Umst. Str. Ident: DE215101721 ________________________________ Der Inhalt dieser E-Mail (einschliesslich etwaiger beigefuegter Dateien) ist vertraulich und nur fuer den Empfaenger bestimmt. Sollten Sie nicht der bestimmungsgemaesse Empfaenger sein, ist Ihnen jegliche Offenlegung, Vervielfaeltigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte informieren Sie in diesem Fall unverzueglich den Absender und loeschen Sie die E-Mail (einschliesslich etwaiger beigefuegter Dateien) von Ihrem System.
_______________________________________________ dev-general mailing list dev-general@lists.oxidforge.org http://dir.gmane.org/gmane.comp.php.oxid.general
