Jason Roberts wrote:
>> I'd be careful as abstractions of abstractions can easily lead to
>> fat beasts which can do everything, but are complex as hell where
>> nobody understands what is what and how it actually works.
>
> I believe I learned this as oopaholism, a disease in which someone
> be
Jason Roberts wrote:
Ragi,
Thanks for your thoughts. I know what you are saying; no need to create a
another useless layer. But by adopting one or the other APIs, I would get
locked in to whatever that API decided to support, with no way to work
around it other than to hack on a private copy of
is pointless or not doable at this moment in
time, then I guess I am crazy.
Jason
-Original Message-
From: Mateusz Loskot [mailto:mate...@loskot.net]
Sent: Thursday, February 18, 2010 3:23 PM
To: Jason Roberts
Cc: 'gdal-dev'
Subject: Re: [gdal-dev] Nullable fields in OGR
Jason
hind a common abstraction (or will there
be a QgisLayer driver for OGR?)
Jason
-Original Message-
From: rbur...@gmail.com [mailto:rbur...@gmail.com] On Behalf Of Ragi Y.
Burhum
Sent: Thursday, February 18, 2010 2:30 PM
To: gdal-dev@lists.osgeo.org; Jason Roberts
Subject: Re: [gdal-dev] Null
Jason Roberts wrote:
> A while back, Mateusz asked this:
>> Yes. Also, most applications I've seen using OGR do define their own
>> data models and translate OGRFeature to features of their own types.
>> Perhaps it would be interesting to know why they don't use OGRFeature
>> as a part of their dat
nt to work together on finishing it.
My two cents,
- Ragi
> Date: Thu, 18 Feb 2010 12:37:04 -0500
> From: "Jason Roberts"
> Subject: [gdal-dev] Nullable fields in OGR
> To: "'gdal-dev'"
> Message-ID: <01d201cab0c0$fc6afd80$f540f8...@roberts@du
Jason Roberts wrote:
Even and Frank, thanks for your replies. I am a little confused because you
each appeared to describe different behaviors.
Frank said:
There is currently no way to test if a datastore supports the concept
of NULL fields, but if it does not it should just write a default va
ons%20for%20shapefile%20output. Does OGR do something
different?
Thanks,
Jason
-Original Message-
From: Even Rouault [mailto:even.roua...@mines-paris.org]
Sent: Thursday, February 18, 2010 1:09 PM
To: gdal-dev@lists.osgeo.org
Cc: Jason Roberts
Subject: Re: [gdal-dev] Nullable fields in OGR
Le Thursday 18 February 2010 18:37:04 Jason Roberts, vous avez écrit :
> Many relational databases allow fields to be set to NULL. Is this supported
> in OGR? How does one detect whether a field is nullable or not?
All fields in OGRFeature are nullable. I think most OGR drivers will support
writi
Jason Roberts wrote:
Many relational databases allow fields to be set to NULL. Is this
supported in OGR? How does one detect whether a field is nullable or not?
Looking at the class documentation, I see functions
OGRFeature::IsFieldSet and OGRFeature::UnsetField. Are these intended
for che
Many relational databases allow fields to be set to NULL. Is this supported
in OGR? How does one detect whether a field is nullable or not?
Looking at the class documentation, I see functions OGRFeature::IsFieldSet
and OGRFeature::UnsetField. Are these intended for checking whether a field
is N
11 matches
Mail list logo
