Hi, @Robert: thanks for understanding. It’s very like you described – there is some lack of time and we are trying to focus on most important things at first. Even if the tasks with lower priority can be done in 15 mins… but when you have lot of these, you can never get back to the important ones.
And it was like Marc said – this was requested in 2009, then moved to uservoice and stuck there. Thanks for your attention to that topic, as it proved us, that this is much more important than we thought before as it would make life easier for lot of developers. So we will get back to this question. In general – this is a good idea and worth to be included in the standard. We added this task to our Backlog and hope to get it done in one of the next Major versions - maybe already in 4.6.0 (as we unlikely will do database changes in patches before). Sorry for inconveniences. Sometimes we also need to think - how to make simple things in simple way ;) …and we will think about. Best regards, Dainius Bigelis From: [email protected] [mailto:[email protected]] On Behalf Of Robert Rosendahl Sent: Thursday, August 04, 2011 11:32 AM To: [email protected] Subject: Re: [oxid-dev-general] Timestamp field in oxuser [T-YUMMCF7W6V-11] Hi, I thought about this, too, but I just tried it and it's not working. I guess that is because if the field contains "0000-00-00 00:00:00" for example, when it is loaded, the shop will explicitly set it with that value in the update query. Since it is explicitly set, it doesn't get a current timestamp... You'll also have to add the timestamp field to the _aSkipSaveFields array (see oxArticle and oxBase). I haven't tested that, but I guess that this will also cause the timestamp to change everytime the user passes the user page during checkout, because the change_user() function does an update to the oxuser table. You'd need to test that - a hash over the user data for detecting changes might be the better choice then... Also, you'd have to add a timestamp (or hash) to the oxaddress table, too, for detecting changes in a user's delivery addresses. As for the common sense: developing features for a software like OXID eShop probably has more to do with resources and deadlines than with what might be nice to have from a developer's point of view... I doubt that the feature is missing because the OXID developers (or project management) just didn't want it, but rather because they just didn't have that spare time to implement it. That's just my assumption, of course, but from my own experience I know that most people in the e-commerce business are rather working overtime already... And since this timestamp issue seems pretty easy by the first look, but then shows to be a bit more complex than that, you'll probably trip over several deadlines if you expected to get it done in half an hour (including thorough testing and consideration not to break any existing behavior or 3rd party extensions) ;-) Best regards, Robert Am 03.08.2011 um 16:48 schrieb development: Hi Andreas, Thanks for the hint and of course you’re right. With “program myself” I meant any task involved to get it working (also for the ERP interface). As this beautifully shows us what I meant with “no brainer”. So I restate my question: Why don’t we have such fields in all major tables? Why do we have to do it ourselves (even if it isn’t a hassle)? And once we would have these fields my next question would be, “why don’t we have any parameter that supports them in the ERP interface?”. Again I don’t want to flame around but ask this question which bugs my common sense. And if there is no reason AGAINST it we certainly find lots of reason FOR it. Thanks Marc ORCA Services AG Herrenmattstrasse 26 CH-4132 Muttenz Office Basel: Aeschengraben 10, CH-4051 Basel [email protected]<mailto:[email protected]> T. +41 61 205 80 80 T. +41 61 205 80 73 (direkt) F. +41 61 205 80 81 www.orca.ch<http://www.orca.ch/>, www.orca-services.ch<http://www.orca-services.ch/> "We convert your visitors into customers." ________________________________ Von: [email protected]<mailto:[email protected]> [mailto:[email protected]] Im Auftrag von anzido GmbH Gesendet: Mittwoch, 3. August 2011 10:11 An: [email protected]<mailto:[email protected]> Betreff: Re: [oxid-dev-general] Timestamp field in oxuser [T-YUMMCF7W6V-11] Hi, there's nothing to code for this. Just add the appropriate field to oxuser table and make it a timestamp field and define it as "on update CURRENT_TIMESTAMP". That's it. Beste Grüße aus Dortmund! Andreas Ziethen | Geschäftsführung -- anzido GmbH Kirchhörder Str. 12 44229 Dortmund ACHTUNG: ab 01.08.2011 neue Anschrift: Iltisweg3 44269 Dortmund Tel.: 0231 - 60 71 079 Fax.: 0231 - 60 71 081 Mobil:0176 - 8325 1488 Email: [email protected]<mailto:[email protected]> Web: http://www.anzido.com<http://www.anzido.com/> USt-ID: DE257982972 Geschäftsführung: Andreas Ziethen Amtsgericht Dortmund HRB 20883 -----Ursprüngliche Daten----- Datum: 02.08.2011 22:28:26 Von: development <[email protected]<mailto:[email protected]>> An: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> Betreff: [oxid-dev-general] Timestamp field in oxuser Vorgang: T-YUMMCF7W6V-11 Hello everybody Can anybody give me a reason why there is no timestamp field in the oxuser table? We have a oxcreate and a oxregister (which I don’t see a reason for since the ERP interface doesn’t care about it anyway). Heck someone asked for that field in 2009: https://bugs.oxid-esales.com/view.php?id=1389 And OXID was considering it in the near future back then as it seems. But I guess then they setup their Uservoice tool and since then not enough people voted for it. http://oxid.uservoice.com/forums/31940-feature-requests/suggestions/362774-add-timestamp-column-to-oxuser-table?ref=title Obviously cause there are more important “features” to implement but hey sorry - come on - such a simple thing should be a no brainer. For an ERP/OXID interface I should be able to check for any modifications in the users table and now I have to program that myself? *shakehisheadindisbelief* I really don’t want to flame around here but tiny things like that make developer’s life easier or a major P.I.T.A. Have a nice day Marc ORCA Services AG Herrenmattstrasse 26 CH-4132 Muttenz Office Basel: Aeschengraben 10, CH-4051 Basel [email protected]<mailto:[email protected]> T. +41 61 205 80 80 T. +41 61 205 80 73 (direkt) F. +41 61 205 80 81 www.orca.ch<http://www.orca.ch/>, www.orca-services.ch<http://www.orca-services.ch/> "We convert your visitors into customers." ________________________________ _______________________________________________ dev-general mailing list [email protected]<mailto:[email protected]> http://dir.gmane.org/gmane.comp.php.oxid.general _______________________________________________ dev-general mailing list [email protected]<mailto:[email protected]> http://dir.gmane.org/gmane.comp.php.oxid.general
_______________________________________________ dev-general mailing list [email protected] http://dir.gmane.org/gmane.comp.php.oxid.general
