brewtarget-devs team mailing list archive

[Philip Lee <rocketman768@xxxxxxxxx>]

We are doing database merges for updates. This allows us absolutely
certainty when updating the ingredients and recipes that ship with
brewtarget. The XML is absolutely painful and messy as a backend. Mik found
out the BeerXML spec does not even conform to XML!

As far as I'm concerned, the XML should only be used for interoperability
with other software.


On Thu, Apr 10, 2014 at 10:13 AM, Peter Buelow <goballstate@xxxxxxxxx>wrote:

> Sorry, hashing out old questions. How good is the import and export of the
> DB content to XML right now? I'm implementing the Dropbox (and soon Google)
> storage, but I don't want to just blindly copy the sqlite database. What
> I'd like to do is improve the Database class to handle incoming XML content
> such that it can compare and update the local database where necessary. It
> would also then be able to export content out to XML on the remote storage.
>
> Thoughts? I know BeerXML isn't great, but is this the best plan? Is there
> a smarter way to handle this type of update?
>
> --
> Pete
>
> --
> Mailing list: https://launchpad.net/~brewtarget-devs
> Post to     : brewtarget-devs@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~brewtarget-devs
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
Philip G. Lee
rocketman768@xxxxxxxxx