Thank you Jacks.
I love you
Keep up the phenomenal passion you have. You feed a world
- sent via mobile phone
> On May 17, 2014, at 12:32 AM, Jackie Ng wrote:
>
> No identity properties = un-selectable layer
>
> FDO Providers are generally not smart enough to infer identity properties
> from
Any way to build into maestro on a layer
On May 16, 2014 11:33 PM, "Jackie Ng" wrote:
> No identity properties = un-selectable layer
>
> FDO Providers are generally not smart enough to infer identity properties
> from database views. That's why the schema override mechanism exists: To
> let
> you
No identity properties = un-selectable layer
FDO Providers are generally not smart enough to infer identity properties
from database views. That's why the schema override mechanism exists: To let
you specify these properties manually.
- Jacki
--
View this message in context:
http://osgeo-org.
Hello,
I am having following configuration:
- MGOS 2.5.1
- Postgresql 9.3/Postgis 2.1
- Windows 2008
When creating a layer on a database view which is based on one table we can
make a selection without any problems. If we make a view that is based on
multiple tables (join) it is not possible an