I’m about to deal with XML in my postgres driver, currently it just returns as a string automatically, but I wonder if you preferred it to be structured.
Schultzer
silverdr
I am not 100% sure I understand correctly, but in the end XML being string is of little value. It’s only a string representation of some structure so at some point I always need it “structured” in the sense I wrote above some time ago:
0
Schultzer
Yeah, I think I miss understood your comment and the issue.
I understod the issue to just wanting the xml to be decoded as a string, there is not a lot of value in that if you want to do further validation in your application code, that was what was what I was trying to refer to with structured, where I’m thinking Elixir terms. It could be an XML AST.
0
silverdr
The post about “saviour” comment on github was about the fact that even if you create a custom Ecto type, you still cannot access XML data (even as string) from PostgreSQL column of XML type as you’ll get “type ‘xml’ can not be handled” errors. The solution is to add Postgrex.Extension implementation that treats it as text I presume. Not something exceptionally elegant I’d say (if I understood all of it) 
And - TBH - the quote of the author there:
I don’t grok some of the quote stuff yet or matching on the encoded binaries, so I’m not sure if this is right, but it works
applies directly to me too 
IOW - it was about getting the XML data out of the column “at all” and hence as string.
0
Schultzer
Yeah, my Postgres driver is going to support anything out of the box, as any type even custom types in the end can be decoded to their base type, for XML it would be text.
But we probably want more then just text if we’re going to do more work with it in our application code.
0