| From: | Josh Close <narshe(at)gmail(dot)com> |
|---|---|
| To: | POSTGRES-PERFORMANCE <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: [Npgsql-general] index out of range |
| Date: | 2005-06-09 13:35:29 |
| Message-ID: | 4a0cafe2050609063557b4dcce@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 6/8/05, Francisco Figueiredo Jr. <fxjrlists(at)yahoo(dot)com(dot)br> wrote:
>
> --- Josh Close <narshe(at)gmail(dot)com> escreveu:
>
> > Well, that would make total sense. I was kinda curious how the data
> > provider differentianted between :a and casting like now()::text.
> >
>
> Hi Josh!
>
> Npgsql uses the info found in NpgsqlCommand.Parameters collection. We do check
> if a parameter in Parameters collection isn't found in query string. The other
> way around isn't done yet. So, you can safely put something like: :a::text and
> it will send the text 5::text for example.
>
> I hope it helps.
Yes, that does help. Thanks.
-Josh
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jona | 2005-06-09 13:42:24 | Re: Query plan changes after pg_dump / pg_restore |
| Previous Message | Richard Huxton | 2005-06-09 13:11:22 | Re: postgresql.conf runtime statistics default |