<font size="2">Steve,<br><br>Currently each field to be retrieved is converted to varchar within the sql query statement in case if the mssql 2008 driver is used. If these fields are not required, you could probably define a view which doesn't contain such columns to be retrieved along with that layer.<br>
<br>Best regards,<br><br>Tamas<br><br><br></font><br><div class="gmail_quote">2010/9/9 Lehr, Steven <span dir="ltr"><<a href="mailto:lehrs@erau.edu">lehrs@erau.edu</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div>
<p><font size="2">Group:<br>
<br>
I have a client that is thinking of using 2 blob type fields in their primary table using Microsoft SQL Server. <br>
<br>
I was wondering to get some insights on any issues you have experienced dealing with joining tables to GIS that have Blob type fields in a table being joined too. Again this is a primary table, and will likely be used in almost all Joins from GIS to SQL Server.<br>
<br>
Thank you<br>
Steve Lehr</font>
</p>
</div>
<br>_______________________________________________<br>
mapserver-users mailing list<br>
<a href="mailto:mapserver-users@lists.osgeo.org">mapserver-users@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/mapserver-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/mapserver-users</a><br>
<br></blockquote></div><br>