Regarding npgsql, range types have no direct mapping so they will be
treated like strings. Sorry for that.
I'll work to add support to it. Would you mind to fill a feature request
about that on our feature requests project page? http://project.npgsql.org
Thanks in advance.
Em 03/08/2012 17:01, "M
Thanks!
Em 03/08/2012 17:25, "Mike Christensen" escreveu:
> Done. Bug #1011216
>
> On Fri, Aug 3, 2012 at 1:11 PM, Francisco Figueiredo Jr.
> wrote:
> >
> > Regarding npgsql, range types have no direct mapping so they will be
> treated
> > like strings. Sorry for that.
> >
> > I'll work to add
> -Original Message-
> From: pgsql-general-ow...@postgresql.org [mailto:pgsql-general-
> ow...@postgresql.org] On Behalf Of Mike Christensen
> Sent: Friday, August 03, 2012 4:00 PM
> To: pgsql-general@postgresql.org
> Subject: [GENERAL] Another question about Range types
>
> There's anothe
Didn't feel like creating an account (or figuring out my logon info) for the
post so I'll include my thoughts here:
> Yea, I wrote a blog post on this subject recently if you're interested.
>
> http://blog.kitchenpc.com/2012/06/27/3-4-things-left-to-do/
===
>> If I do switch to RANGE types, I think [2,2] would make sense in this
> case.
>> Using unbounded ranges might make sense if I wanted to express something
>> like "Use up to 1 cup of flour" or "You'll need at least 3 cups of water".
>>
>
> In these cases:
>
> Flour: [0, 1] - "optional, but maximu
>
> If I do switch to RANGE types, I think [2,2] would make sense in this
case.
> Using unbounded ranges might make sense if I wanted to express something
> like "Use up to 1 cup of flour" or "You'll need at least 3 cups of water".
>
In these cases:
Flour: [0, 1] - "optional, but maximum of 1-c
>> There's another ongoing thread about range types, which was great because
>> I wasn't familiar with the feature (guess it's new in 9.2?).
>>
>> I run a recipe website and was looking for *exactly* this sort of feature
> a few
>> weeks ago when I was adding in support for ranges of ingredients (s
Done. Bug #1011216
On Fri, Aug 3, 2012 at 1:11 PM, Francisco Figueiredo Jr.
wrote:
>
> Regarding npgsql, range types have no direct mapping so they will be treated
> like strings. Sorry for that.
>
> I'll work to add support to it. Would you mind to fill a feature request
> about that on our fea
