Re: [mapguide-users] quick one regarding mssql
Just thought I'd touch back on this subject and show what I ended up doing. In my export process to my SQL datastore I now convert my xmlfragement from my software package (Bentley Map ... side note anyone use this in the community?) to a varchar field with 2000 characters then I note what my field is and format the xml in the selection panel !!! operation success! Would it be worthwhile chasing up adding xml as a data type to the fdo? I'm not sure on the changes required or its difference to standard text fields, just find xml fairly good way of storing these sorts of attributes. http://osgeo-org.1560.n6.nabble.com/file/n5003113/xmlFragment.png -- View this message in context: http://osgeo-org.1560.n6.nabble.com/quick-one-regarding-mssql-tp5002497p5003113.html Sent from the MapGuide Users mailing list archive at Nabble.com. ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
Re: [mapguide-users] quick one regarding mssql
Are you talking about supporting XML as a new logical data type? Or just getting the FDO provider to interpret XML columns as string properties? Supporting a new logical data type in FDO has ramifications in API design. - If FDO were to support and recognise XML data types, how does one work with such types through FDO? - There needs to be the possibility for other providers to gain such support as well. Otherwise it is a tall order to support a specialized data type in a *generic* data access layer like FDO. Do other systems like Oracle, Postgres, etc support XML columns? Getting the FDO provider to treat XML columns as strings is an easier proposition - Jackie -- View this message in context: http://osgeo-org.1560.n6.nabble.com/quick-one-regarding-mssql-tp5002497p5003117.html Sent from the MapGuide Users mailing list archive at Nabble.com. ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
Re: [mapguide-users] quick one regarding mssql
I suppose for all purposes xml is just formatted text in the end, so reading it as a text field works just fine for me, It would be great to be able to know the field I'm accessing is in fact formatted as xml therefore prompting me to do something with it... I was only thinking of this very basic example of an xml list, but in reality people would put all sorts of nasty things in there, making it hard to cater for I guess. for this exercise reading it as a string that happens to be xml has worked a treat and will probably be the path I take for further implmentation of this list style property. All be it the string has been escaped a little just run the value through a nasty decode operation to put it back together again. -- View this message in context: http://osgeo-org.1560.n6.nabble.com/quick-one-regarding-mssql-tp5002497p5003123.html Sent from the MapGuide Users mailing list archive at Nabble.com. ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
Re: [mapguide-users] quick one regarding mssql
it's simply not a supported FDO data type, you could try creating a view which returns the XML as a string? even if it was supported, you would still need to do some custom coding for it to be handled in the properties pane On Tue, Sep 18, 2012 at 11:33 AM, Jamo adam.jami...@portbris.com.au wrote: I've just managed to get an xmlfragment property type populated in my sql database but sadly it would seem it isn't supported by default in the fdo? can anyone confirm or deny this is true and any ideas on how to get it implemented on the mapguide side of things? So I now have the ability to store a xmlfragement and idealy anchor off this in the properties pane rather than my current way of having two comma seperated attributes (this becomes unstuck as the data get further populated). -- View this message in context: http://osgeo-org.1560.n6.nabble.com/quick-one-regarding-mssql-tp5002497.html Sent from the MapGuide Users mailing list archive at Nabble.com. ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users -- Zac Spitzer Solution Architect / Director Ennoble Consultancy Australia +61 405 847 168 ___ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
