andi wrote
rivabem wrote
It would be interesting if the retrieving/saving process was completely modular, so one could write plugins to different storage systems or to enhance something he'd lke.
No it's not very modular in that regard, in fact it is highly optimized to use the file system in a most optimal way. Simply replacing IO functions to store stuff in a DB would be a really bad idea and possibly make things slower, not faster.
BTW. requiring to use Oracle for a tool that does not use a database is plain stupid. Do you store your text processing files in Oracle as well?
We do not require oracle for DokuWiki itself, but we need a wiki and we'd like to use DokuWiki, it´s pretty good.
The intention of the database is not making it faster, we're sure it wil not work that way. Our need is integration with other tools we have that cannot access/create a remote text file neither can access http server and use it as a service.
We may do some helping scripts, such as one to read jpg and pdf from the database to link them from the Wiki, or even a cronjob to synchronize the Oracle database to the Wiki database for searching, that's easy. But we were willing to develop something not that specific and more useful to the community.
And surprise yourself, most collaborative tools like Oracle Collaboration and Microsoft Sharepoint do save lots of files on the database. They have even a Explorer plugin for drag and drop! No, I don't like it, but...