Some updated in r3981 "TECHNICAL REQUIREMENTS" (NB: TECHNICAL !!!) have value less than none for technical specialists. Namely,
MySQL 5+ with sql_mode in standard mode (ie not in traditional or any other mode)
is just brainless. At least I, as DBA, can't see any sense in it
HTH
info@elgg.org
Security issues should be reported to security@elgg.org!
©2014 the Elgg Foundation
Elgg is a registered trademark of Thematic Networks.
Cover image by RaĆ¼l Utrera is used under Creative Commons license.
Icons by Flaticon and FontAwesome.
- Cash@costelloc
Cash - 0 likes
- Brett@brett.profitt
Brett - 0 likes
You must log in to post replies.I agree there is a better way. Right now there is a problem in the schema that is causing warnings. If you change the sql_mode, it can result in those warnings becoming errors. The better way is fixing the schema. The ticket here: http://trac.elgg.org/elgg/ticket/1562 as I'm sure you know.
By the way, I find your overreactions very tiresome.
1. the better place to post is Trac since this is where the ticket is being discussed
2. Your language is always much stronger than the situation deserves
I've changed the schema on my working copy to add a default value to the last_action column but it hasn't been committed yet because I wanted to test it more.
The addition of the requirement is because Elgg hasn't been thoroughly tested in the alternative SQL modes offered by MySQL and no guarantees can be made that it will work. This is quite similar to the situation with running Elgg on a server with PHP in CGI mode--It might work, but it's not officially supported yet.