Re: [pmapper-users] Oracle connection - advice needed

[Gambin D. <Dej...@pu...>]

nquery works as you said, that was my mistake of not selecting the =
correct layer after clicking on "Select" button :-((

Since I am not familiar with json and javascript generally, do you think =
I could do something in squery.php, specifically in printFields function =
by creating a qStr for each row of  "many" data similar to qStr for any =
other row created by printResultRow? I hope you understand what I mean =
:-))

regards, dejan

> -----Original Message-----
> From: Armin Burger [mailto:arm...@gm...]=20
> Sent: Friday, November 24, 2006 9:39 AM
> To: Gambin Dejan; pma...@li...
> Subject: Re: [pmapper-users] Oracle connection - advice needed
>=20
>=20
> > Well, it is working for me but let me explain:
> >=20
> > I have a polygon shape presenting buildings. There is a=20
> building ID in=20
> > the dbf file. Oracle database has a table of locations=20
> inside the buildings.
> > This table has also a building ID and it holds many locations=20
> > attributes (area, volume, user, purpose, etc.). I have tried using=20
> > one-to-many query in pmapper by joining tha shapefile with=20
> locations=20
> > table. And it works..(by identify query). I get for example=20
> the "area"=20
> > for each location inside the building. The problem is that pmapper=20
> > incorrectly displays all the attributes for one building in=20
> one row instead of breaking the row for each location.
> > But this can be solved I think.
> >=20
>=20
> This is what I meant that 'it's not working'. The result=20
> array for one feature contains too many attributes. Ok, you=20
> could try in pmjson.js for the result display to check for=20
> this and add an additional row if the array of the result=20
> feature is longer than the one for the header. The problem is=20
> that with the current result structure in the json string all=20
> results from the join are in the same array, you do not know=20
> when one ends and the next starts.  =20
>=20
> In any case you will have to decide how to display such a=20
> result. Having one building eg. appearing multiple times with=20
> all the common attributes and the zoom button, just because=20
> of additional attributes, might not look very intuitive and=20
> logical to users and one might at first glance see them as=20
> separate buildings.=20
>=20
>=20
> > So now I am confused about what you said. I really need to do this=20
> > type of join and I will gladly contribute to make it working=20
> > correctly. For now I am planning to solve the "one row" displaying=20
> > problem and maybe support nquery (it is not working of=20
> course). Also,=20
> > I didn't try with attribute query yet.
> >=20
>=20
> I wonder why nquery or search should not work, they should be=20
> identical for the display as normal query.
>=20
> armin
> --
> Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!=20
> Ideal f=FCr Modem und ISDN: http://www.gmx.net/de/go/smartsurfer
>=20