Re: [mapguide-users] impersonate mapagent to server

You can use MgHttpRequest and MgHttpResponse to wrap the real mapagent and present a mapagent-like HTTP interface to any client applications. Then in your wrapper, you can set up whatever required credentials so that Oracle knows who is connecting. There's an old .net example on my github

Re: [mapguide-users] mapguide-rest

First: Syntax error on my end. It's most likely fixed since the most recent release. Second: Certain APIs allow for anonymous access, certain APIs require authentication and some require authentication from certain classes of users (Author, Administrator). I should probably document the required

Re: [mapguide-users] Mapguide 3.0 Postgre view problem

Yeah, I got it working with other tables where PK is defined, then it works, of cause there is little peformance drop compered to regular view with join, but selection is possible. So when there is no PK field in view then view become as nonselectable when using Mapguide. I have tables without PK

Re: [mapguide-users] Mapguide 3.0 Postgre view problem

You should update the layer (recreate if need) and mapguide (if you need to stop and restart the service) Try and see if it works: 1) Try to create another view only from the main table (no join or function), remember to put the primary key in the view 2) Create a new layer for this new view 3)

Re: [mapguide-users] Mapguide 3.0 Postgre view problem

Thank you. I created view but selection is still not working. -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Mapguide-3-0-Postgre-view-problem-tp5298765p5298827.html Sent from the MapGuide Users mailing list archive at Nabble.com.

Re: [mapguide-users] Mapguide 3.0 Postgre view problem

Sorry, the previous URL was not the good one. Try this one instead : http://themapguyde.blogspot.com/2010/08/using-fdo-schema-overrides.html It is a post from Jackie's blog. -- View this message in context:

Re: [mapguide-users] Mapguide 3.0 Postgre view problem

Hi, You can also take a look at this post : http://osgeo-org.1560.x6.nabble.com/Mapguide-3-0-Postgre-view-problem-tp5298765p5298822.html Hope this helps. Georges -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Mapguide-3-0-Postgre-view-problem-tp5298765p5298825.html

Re: [mapguide-users] Mapguide 3.0 Postgre view problem

I have two tables: 1)grag 2)ditch View I want to create is : CREATE OR REPLACE VIEW public.route_lines_view AS SELECT grag.dp_oid, grag.dp_otype, grag.dp_subtype, grag.dp_ctype, grag.dp_mod, grag.dp_state, grag.shape, ditch.owner, ditch.length FROM piping.grag

Re: [mapguide-users] Mapguide 3.0 Postgre view problem

Junction of two table for mapguide is already complex (a little ;-)) First you need to create this function in your postgres, then when creating the view you will only use a table in the "from" getting the second table or how many more are needed for use in the function. View example: Create

Re: [mapguide-users] Mapguide 3.0 Postgre view problem

Mu view wasn't complex, its was just simple join between two tables. Take some data from one table and take some from another where tables having one common field for joining. Sry but my SQL knowledge specially functions is far away from perfect so how I can use this function :) -- View this

Re: [mapguide-users] Mapguide 3.0 Postgre view problem

Hi, I had the same problem here and really complex views do not work in the guide One solution is to use a function to get fields from the second table CREATE OR REPLACE FUNCTION public.guide_generic_search_table(vfield character varying, vNameTable character varying, vfilter character varying)

Re: [mapguide-users] Mapguide 3.0 Postgre view problem

Sorry... - AG-Carto - Bayonne -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Mapguide-3-0-Postgre-view-problem-tp5298765p5298778.html Sent from the MapGuide Users mailing list archive at Nabble.com.___ mapguide-users

Re: [mapguide-users] Mapguide 3.0 Postgre view problem

Primary key is not supported in Postgresql views. As I previously said using view without joined tables and primary key works just well. Just cant understand why joins ruin the selection possibility. -- View this message in context:

Re: [mapguide-users] Mapguide 3.0 Postgre view problem

Hi, Immediatly without reflexion, i ask me if you don't loose the primary key notion with your join in the view... Rémy - AG-Carto - Bayonne -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Mapguide-3-0-Postgre-view-problem-tp5298765p5298770.html Sent from the

[mapguide-users] Mapguide 3.0 Postgre view problem

HI! When I use Postgresql(9.5, postgis 2.2) views as data source for features, where data is collection from two tables(using joins) then I cant select features in the map. When just using Postgres view where no join then features are selectable, but using views where are joined data then there