Tuju, Super. Glad to hear that gDS is of help to you.
And, by the way, there is now some support for SQLAlchemy in the gDS repo. I suspect it's not what you need, but might be of interest. Thanks for the feed-back. Dave On Mon, May 27, 2019 at 04:35:40PM +0300, Juha Tuomala wrote: > > > On Sunday, 26 May 2019 08:42:01 EEST you wrote: > > Good. Glad to hear you solved that one. > > That mega-phone bill? > > I first time managed to parse that into my SQL-database. I goes in cleanly. > And even better - the same code is able to parse other invoices without > problems (even I made settings per supplier that can use different python- > implementation that is supplier specific). > > This is a huge time saver. > > Previously I tried to do this same with Suds XML-object mapper. In theory it > makes SOAP-connection and provides proper oop-interface for that remote > server. All responses are proper objects also. But when I started using them, > some elements were sometimes as is, sometimes encapsulated into lists. And > that varied invoice by invoice and always broke the parsing. > > That whole representation in python needs to be based to the XSD. Is some > value allowed to appear more than once? Yes, then put those sub-instances > into > list, ALWAYS. And that's where GDS does it correctly. The same code works > always regardless the content of invoice. > > This is good, my life just got so much better. :) > > I still need to figure out the amount of zeros when I'm writing that XML, but > that I find out later this week. > > > Thank you, > > Tuju > > > -- > t...@iki.ee | http://tuju.ee | sip:t...@iki.ee | +3726311345 | +3725025337 > Better to have one, and not need it, than to need one and not have it. > > -- Dave Kuhlman http://www.davekuhlman.org _______________________________________________ generateds-users mailing list generateds-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/generateds-users
