Thanks for the feedback!
For James, the reference to MongoDB is very interesting. The more I looked
into MongoDB, I am thinking it is just what I need for this project, since
the db stuff is still so fluid.
There is (was?) a django interface for MongoDB, at https://django-mongodb-
engine.readthed
On Dec 16, 2017 4:46 PM, "Mark Phillips" wrote:
I am building an electronic document management system using django and
mysql. The purpose of this system is to catalog and retrieve electronic
documents. There is no inventory of the physical documents. There are about
3,000 documents (photos, pdfs
Hi,
As suggested using Postgres as a database backend would give you first
class support for JSON field with ability to query by attributes in JSON
data.
See
https://docs.djangoproject.com/en/2.0/ref/contrib/postgres/fields/#jsonfield
for more info.
17.12.2017 2.46 "Mark Phillips" kirjoitti:
I use https://github.com/dmkoch/django-jsonfield for storing metadata and
works very well, the only problem that I see in using one jsonfield for all
the metadata you have for a document is searching (which I don't need).
3k, 6k or 9k of rows is "nothing" for MySQL or Postgres, a bottleneck won't
If you switched to Postgres you could use a json data type or dictionary
data type. Django 1.11 onwards supports the storage and retrieval of both
types I believe.
Dan
On Sun, 17 Dec 2017 at 07:46, Mark Phillips
wrote:
> I am building an electronic document management system using django and
>
I am building an electronic document management system using django and
mysql. The purpose of this system is to catalog and retrieve electronic
documents. There is no inventory of the physical documents. There are about
3,000 documents (photos, pdfs, videos) now, and that number could double in
the
6 matches
Mail list logo
