[mapguide-users] RE: RE: King.Oracle 0.3.3

[Haris Kurtagic]

Yes, I agree.
For metadata we can use already existing Autodesk FDO metadata, ( and
that is something I will support)
and yes I am trying to avoid metadata as long as possible.

Haris

-----Original Message-----
From: Joel Carranza [mailto:jec at gatekeeper.com] 
Sent: Wednesday, October 25, 2006 8:04 PM
To: users at mapguide.osgeo.org
Subject: [mapguide-users] RE: RE: King.Oracle 0.3.3


Both of those things are true, but PK constraints and spatial index
types may be defined on tables, and not on the views on top of the
tables. When your dealing with views, you don't really know what is
going on underneath. While it *may* be possible to do some
reverse-engineering and figure some things out automatically, i doubt
the work is worth the effort. Whatever format of metadata you use is
probably OK, as long as it can be easily accessed programatically. 

I would just point out that any metadata specified should be thought of
as 'overrides' in the sense that they are not required. People who just
wanted to use tables (with well defined PKs and what not) could just use
the provider as-is. 


haris kurtagic wrote:
> 
> 
> Hi Joel,
> Thank you for your comments.
> Regarding geometry type, basically you can do it when defining spatial

> index type in Oracle. This could also improve performance especially 
> on points Also key columns can be defined via primary key ( unique 
> wouldn't be ok because I think fdo wouldn't recognise null as a key ) 
> Yes, In principle I don't like of putting a lot of metadata inside db,

> but when is necessary
>  
> Haris
> 
> -----Original Message-----
> From: Joel Carranza [mailto:jec at gatekeeper.com]
> Sent: Wednesday, October 25, 2006 7:42 PM
> To: users at mapguide.osgeo.org
> Subject: [mapguide-users] RE: King.Oracle 0.3.3
> 
> 
> Its seems to me that eventually you will have to rely on user supplied

> metadata to solve this problem. For each table or view, a user would 
> be able to specify a key column and also maybe what type of geometry 
> (point,line, poly, mixed, etc...) is in the table. Specifying a type 
> of geometry would be nice, so that layers created from feature classes

> are correctly displayed in legend. Eventually, you will probably need 
> to allow for other types of metadata as well. This info could be 
> stored in a table within Oracle or in a config file internal to the 
> provider. I'm not sure that it matters.
> 
> Joel
> 
> 
> haris kurtagic wrote:
>> 
>> 
>> Hi Joel,
>> 
>> Regarding selecting, I tested it again and I am able to select layers

>> wich comes from tables with primary keys.
>> Right now primary key is only way to tell provider to use that column

>> as identity.
>> 
>> Any sugestions are welcome.
>> 
>> I should do something for views also.
>> 
>> Note:
>>  It seems there is an issue in viewer regarding selecting:
>> If you have a large scale layer and then zoom in much smaller and 
>> then
> 
>> you click on feature, mg will send wrong coordinates for selecting on

>> that click hence tooltip will work, it send different coordinates to 
>> provider for tooltip and click on.
>> If you take that same layer and put in the map, and give map a 
>> smaller
> 
>> extents, click on and tooltip works.
>> 
>> Haris
>> 
>> -----Original Message-----
>> From: Joel Carranza [mailto:jec at gatekeeper.com]
>> Sent: Tuesday, October 24, 2006 8:05 PM
>> To: users at mapguide.osgeo.org
>> Subject: Re: [mapguide-users] King.Oracle 0.3.3
>> 
>> 
>> Fantastic! Talk about agile development. My views showed up and are 
>> now displaying. I'm having some performance problems, but those could

>> easily be my fault. Too much data on too small a machine. Still, I 
>> have a gig of ram on my machine, and while I was browsing a map, I 
>> completely filled it up. I don't think that should happen?
>> 
>> Weirdest thing I have found is that none of my map features in DWF or

>> AJAX are selectable, even though I set them up to be in map 
>> definition
>> 
>> 
>> haris kurtagic wrote:
>>> 
>>> Hi,
>>>  
>>> newer version of King.Oracle 0.3.3 provider:
>>> 
>>> *	Support for Spatial Views
>>> 	It will display views based on spatial tables. Views needs to be
>> 
>>> added into sdo_geom_metadata for provider to find them.
>>> 	
>>> 
>>> Get it here: www.sl-king.com/fdooracle
>>>  
>>> Haris
>>>  
>>>  
>>> 
>>> 
>> 
>> --
>> View this message in context:
>> http://www.nabble.com/King.Oracle-0.3.3-tf2500627.html#a6978386
>> Sent from the OSGeo MapGuide mailing list archive at Nabble.com.
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe at mapguide.osgeo.org
>> For additional commands, e-mail: users-help at mapguide.osgeo.org
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe at mapguide.osgeo.org
>> For additional commands, e-mail: users-help at mapguide.osgeo.org
>> 
>> 
>> 
> 
> --
> View this message in context:
> http://www.nabble.com/King.Oracle-0.3.3-tf2500627.html#a6996820
> Sent from the OSGeo MapGuide mailing list archive at Nabble.com.
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe at mapguide.osgeo.org
> For additional commands, e-mail: users-help at mapguide.osgeo.org
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe at mapguide.osgeo.org
> For additional commands, e-mail: users-help at mapguide.osgeo.org
> 
> 
> 

--
View this message in context:
http://www.nabble.com/King.Oracle-0.3.3-tf2500627.html#a6997191
Sent from the OSGeo MapGuide mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe at mapguide.osgeo.org
For additional commands, e-mail: users-help at mapguide.osgeo.org