On Jun 3, 10:05 am, "[email protected]" <[email protected]> wrote:
> I meant to update http://tiddlyweb.peermore.com/ to use the sql store
> last night, but got distracted writing a thing called multistore which
> lets you write to or read from multiple stores.
This has now been done. http://tiddlyweb.peermore.com/ (now also
acting as http://tiddlyweb.com/) is running using the sql store to
talk to sqlite3. It's also using the caching-store to have a memcached
layer above the sql store. It's unlikely that performance is being
impacted to any significant degree by either of these things because
the performance blocks on that machine are going to be the same
whatever the situation (it's memory bound, this will be fixed soon).
> > Before I plunge in I just wanted to find out what the situation is
> > generally? I'd like to try using PostgreSQL instead of MySQL.
>
> According to the SQLAlchemy docs, using PostgreSQL should "just work"
> by changing the db_config part of server_store in tiddlywebconfig.py:
>
> 'server_store': ['sql', {'db_config': 'sqlite:///test.db'}],
For those following along at home, Oveek and I got his migration to
using PostgreSQL with TiddlyWeb working this evening, doing a bit of
iterative bugfixing in the #tiddlyweb IRC channel. There were issues
with how strict PostgreSQL is compared to Mysql and sqlite.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/TiddlyWikiDev?hl=en
-~----------~----~----~----~------~----~------~--~---
