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 and more performant.

--
Kevin Powick

On Monday, 3 April 2017 16:26:45 UTC-5, Tomi Häsä wrote:
>
> 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 figure out how to create ODT documents, but if I use my own 
> format, I know what I'm doing.
>
> Also, I could use something simpler, like Markdown, CommonMark, Creole or 
> AsciiDoc.
>
> My main idea is that my Android app only knows some formatting, like 
> headings, italics and bold, so I can make the Android app easier to program 
> and less CPU and memory heavy.
>
> On Tuesday, April 4, 2017 at 12:12:07 AM UTC+3, Kevin Powick wrote:
>>
>> 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, I have 
>>> been thinking of making my own document format and save those documents to 
>>> a database. Users would save the documents in my Android app as XML 
>>> locally, but the documents will be saved in a more concise format inside an 
>>> online database server. Are there any known practices, like, is it better 
>>> to save sections of the documents as cells (paragraphs, headings, authors, 
>>> etc.) or should I just save one document in each cell? I have been thinking 
>>> of using for example Unicode character BELL instead of <P> to mark 
>>> paragraphs, and characters BELL+ETX for heading, and so on, or something 
>>> similar where I won't be saving the same word (P, BR, H1, etc.) 
>>> unnecessarily in case I want to make word searches from the database.
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to