> Well, a persistence mechanism would have to store the data somewhere, > anyway. This would be either... I'm familiar with all of the solutions you outlined, with c being the most reasonable. However, I was hoping there might be some kind of global in-memory store that could be used across all requests. Again, my lack of PHP knowledge. Unfortunately the HEAP (or Memory) storage engine doesn't support TEXT > columns. Also...when the mysql server is restarted and the the > table content is wiped. Sorry, I didn't finish my thought: the memory table is loaded the first time it's needed. From then on, reads come from memory while writes go to memory and MyISAM. Oh, and just convert text to varchar(1000) or whatever. > 3) Cool. > > I implemented this in changeset 1516 > http://svn.gregarius.net/trac/changeset/1516 > let's see how it behaves! Is the trac changeset the same as SVN revision? The latest revision I see is 1505: URL: http://svn.gregarius.net/svn/trunk/gregarius Repository Root: http://svn.gregarius.net/svn Repository UUID: d826556c-87f9-0310-90b4-9554b5b11594 Revision: 1505 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://sinless.org/pipermail/gregarius-dev/attachments/20060706/8e612cde/attachment.html