Hi Linas, we have some more complex customer cycles. For EE Customers, we need a different counter for each subshop or the possibility to combine single subshops for a numeration. So autoincrement is a no go.
In a different shop we use a default shop numeration, but after commiting the user to a ERP system we get a totally different number back. An oxCounter would be fitting for getting a numeration on shopside. And an overloadable function on oxuser for "getCounter" would be perfect for combining subshops in a single oxCounter. Best regards, Reinhard Von: [email protected] [mailto:[email protected]] Im Auftrag von Linas Kukulskis Gesendet: Mittwoch, 20. Februar 2013 15:08 An: [email protected] Betreff: [oxid-dev-general] about customer numeration Hi all, As you know in data base oxUser table have field oxcustnr - customer number, now it is auto_increment; we got suggestion to use oxCounter for this purpose and eliminate some drawbacks when user is created on newsletter subscription. Question: do you use some more complex numeration for customers in your custom shops? or have other needs in this case? Linas Kukulskis Developer [email protected]<mailto:[email protected]> Phone +370 37 333053 Fax +370 37 333054 www.oxid-esales.com<http://www.oxid-esales.com/?campaign=emailsignatur/lt/oxid-esales-com> OXID eSales AG Bertoldstraße 48, 79098 Freiburg, Germany Lithuanian Division K. Petrausko g. 26-316, Kaunas LT-44158, Lithuania
_______________________________________________ dev-general mailing list [email protected] http://dir.gmane.org/gmane.comp.php.oxid.general
