Declaration: I'm not a db user (never found a real use for them).
My docbook (primary) use is the accretion of files over time.
Mostly less than a few hundred.
Build tool is plain text (ant / xslt).
My logic (not wishing to call Norm a liar) is that a file system can fail
(I do take care).
Adding
This is a useful discussion.
We make extensive use of git, especially at the beginning of a project.
Do you have any tips for integrating the database approach with a vcs
like git?
Peter
On 06/04/2018 12:35, Norman Walsh wrote:
Camille Bégnis writes:
thanks for this
Camille Bégnis writes:
> thanks for this interesting discussion, what DB would you use or suggest
> for XML?
I’m strongly biased to suggest a particular commercial database, one
that you can download and use for free from developer.marklogic.com.
But I hear good things about
Hi all,
thanks for this interesting discussion, what DB would you use or suggest
for XML?
Camille.
Le 06/04/2018 à 11:43, Norman Walsh a écrit :
> Dave Pawson writes:
>> Agree with your logic. Good for thousands (hard to index)
>> Less so for hundreds (I use db
Dave Pawson writes:
> Agree with your logic. Good for thousands (hard to index)
> Less so for hundreds (I use db indexing)
Yes, but as I said, it depends on the app you’re trying to build.
drinks.nwalsh.com: ~200 small documents, easy to build in a DB, harder outside.
Thanks Norm.
It's the fear of losing it all that holds me back.
Agree with your logic. Good for thousands (hard to index)
Less so for hundreds (I use db indexing)
Also agree with the backup (in either case).
I'd hate to have the data in a corrupt database
regards
On 5 April 2018 at
Dave Pawson writes:
> What use cases are there for dropping a few hundred
> XML files into a (purpose built for XML) database?
I put XML in a database for the ability to index and search it,
primarily. Here’s a screenshot of my personal “evernote clone” that
stores a