The Android app could have (almost) real-time collaboration with teams
where team members can make word searches for all the documents in the
server. All the documents probably get downloaded to the Android devices,
so you can make word searches locally also. If I decide to allow images
also in
On Monday, 3 April 2017 18:22:40 UTC-5, John McKown wrote:
>
> On Mon, Apr 3, 2017 at 5:37 PM, Kevin Powick > wrote:
>
>> Why put the documents in a database on your server at all? Just store the
>> document in the file system with a unique ID.
>>
>
> FTS - Full Text Scan. https://en.wikipedi
On Mon, Apr 3, 2017 at 5:37 PM, Kevin Powick wrote:
> Why put the documents in a database on your server at all? Just store the
> document in the file system with a unique ID.
>
FTS - Full Text Scan. https://en.wikipedia.org/wiki/Full-text_search
Many database systems support this. Two that I
Why put the documents in a database on your server at all? Just store the
document in the file system with a unique ID.
In the database just store the ID and file location with any other relevant
meta information (user, author, title, etc.). This will certainly keep
your database less bloated
That is exactly what I was thinking. I could save the files as OpenDocument
format, DocBook format, etc. in Android but in proprietary format in the
database where no-one else is looking at except my server.
If I use a known standard, like ODT, I actually may need to study a lot of
hours to fig
Sounds like you're re-inventing a wheel that not only may be a lot of work,
but will result in a proprietary format that is incompatible with
everything.
--
Kevin Powick
On Monday, 3 April 2017 02:33:31 UTC-5, Tomi Häsä wrote:
>
> Because Go has structs and it can read for example XML and JSON,
