Two single quotation did the trick.
Thanks you very much.
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/Mapguide-3-0-Postgre-view-problem-tp5298765p5299227.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
solution 1: (for programers people !) note: '' is two Single quotation marks
guide_generic_search_table('CASE when owner = 1 THEN ''one'' when owner =
2 then ''TWO'' END ', 'piping.pipe', 'pipe.dp_oid=' || symg.dp_oid) AS owner
solution 2: (for normal people!)
create a view vw_pipe with the
Thank for you assistance but I cant get "CASE WHEN" things working.
What I'm doing wrong:
...
guide_generic_search_table('CASE when owner = 1 THEN one when owner = 2
then TWO END', 'piping.pipe', 'pipe.dp_oid=' || symg.dp_oid) AS owner
--
View this message in context:
Hi Kajar,
Yes for both issues.
You have to keep in mind that the function requires 3 parameters
1) return field, which can be any valid expression, with when, other
functions etc. But remember only one field (or expression) per function call
2) a table name, but can be a view for example
3) a
Seba, I have some additional question about the function.
1)Can I use CASE WHEN condition with this function
I have situation that owner values are just numbers and I want to convert
those values to some text.
Sample:
CASE WHEN owner = 1 then 'one'
ELSE 'none'
End
2) Can I have also multiple
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
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)
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.
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:
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
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
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
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
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)
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
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:
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
17 matches
Mail list logo