Ohh lolzz
Try php code to store your ... 616 into mysql.
Then come back here to post the bounds error message
That my sql will give you......
A mathematician starts to count at 1 ... most computer systems are starting at 0. That's the difference!
So, if you want to be precise you can say that the range goes from 0 to 18 446 744 073 709 551 615, but the amount of numbers is 18 446 744 073 709 551 616.
Never mind, I know what you mean ... I was just kidding!
Sign bit in my sql for guid# ;oO
I did further testing and twicking every possible thing. It seems that Elgg serves the listing requests (pages/all, bookmarks/all/, etc) from the browser cache, and only a hard browser button reloading request makes it to take the new entity list values from the database. Any ideas on how to fix this?
Thanks a lot.
I'd like to see configurable cache paths in Elgg, but putting these caches in the same paths would be asking for trouble. But making sth like:
/dataroot
/different/path/cache/system_cache
/different/path/cache/simple_cache
Why not? We were working with Elgg on several instances and putting caches (system + simple) in local instance's tmp and dataroot shared via NFS is good way to save resources instead of synchronizing caches. Clearing caches was of course matter of deployment, we did it simply by calling REST API methods for each worker.
So I like idea of separating cache from data.
tasks do not involve more than 11 lines of php code that cater for data/ and cache/ locations;
some few more loc and parameterization of these can be done, quite easily..
i had presented this at Boston Elgg Conference, 2009 as part of ' Distributed Elgg, Conceptual Design & Directions ' -->
MYDOMAIN.COM:
/CONFIG.PHP:
$CONFIG->codeHost = 'http://www.CodeBase.Com/ELGG/';
$CONFIG->configHost = 'http://www.Config.Com/ELGG/';
$CONFIG->dataHost_A = 'http://www.DataHostA.com/ELGGDATA/';
$CONFIG->dataHost_B = 'http://www.DataHost.Bcom/ELGGDATA/';
...
$CONFIG->dataHost_Z = 'http://www.DataHostZ.com/ELGGDATA/';
...
$CONFIG->dataHost_9 = 'http://www.DataHost9.com/ELGGDATA/';
$CONFIG->dbHost_XXX = 'http://www.DataBaseXXX.com/MySQL/ELGG/';
BTW, I definitely see the value in separating data from temporary caches and welcome a ticket/patch to make this possible.
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.