[mapguide-users] text layer with Capital Letter

[James H. Murphy]

< Heh.  Another benefit to open source: you get to read the code comments :)

 

 Some comments in my vlisp routines are not appropriate to read, esp a few I wrote for a engineer that I had to work with. ;) 

 

< I know a few Map power users who would be blown away by this ability also

 

INDEED. 

 

James Murphy

Applications Engineer

ALACAD

 (205)444-3100

 

Visit us at www.alacad.com

 

 

   _____  

From: mapguide-users-bounces at lists.osgeo.org [mailto:mapguide-users-bounces at lists.osgeo.org] On Behalf Of Jason Birch
Sent: Friday, February 02, 2007 12:15 AM
To: MapGuide Users Mail List
Subject: RE: [mapguide-users] text layer with Capital Letter

 

Heh.  Another benefit to open source: you get to read the code comments :)

 

I remember a few sessions sitting with MapGuide Author on one screen and SQL Profiler on another trying to get the syntax right.  It always simple; some things (theming?, bounding boxes?) could make it pretty complex.  It's been a while though...

 

FDO has a similar concept for the database providers, and MapGuide's feature service supports this with ExecuteSQLQuery and ExecuteSQLNonQuery (or something like that).  

 

I wonder if there is any way that we could have an optional "Raw Query String" passthrough in the layer's data source definition so that power users could totally rock the system.  

 

This would allow for some really cool stuff, such as ad-hoc joins, complex conditions, groupings (with aggregate functions), unions, and more.  I know a few Map power users who would be blown away by this ability also.  It would make the results set uneditable, but I think that's a given with any kind of derived dataset.

 

Jason

 

   _____  

From: mapguide-users-bounces at lists.osgeo.org on behalf of Andy Morsell
Sent: Thu 2007-02-01 9:38 PM
To: 'MapGuide Users Mail List'
Subject: RE: [mapguide-users] text layer with Capital Letter

Back on topic, I agree, it would be nice to see support for many more standard SQL functions in MapGuide or FDO (probably the better place to handle it).  That was one nice thing about MG 6.5, as long as SQL for whatever database flavor you were hitting supported it, it generally worked.

 


--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.432 / Virus Database: 268.17.19/663 - Release Date: 2/1/2007 2:28 PM



-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.432 / Virus Database: 268.17.19/663 - Release Date: 2/1/2007 2:28 PM
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/mapguide-users/attachments/20070202/49b8a7f6/attachment.html