From: Oliveiros Cristina <oliveiros.cristina@marktest.pt>
To: Francisco Figueiredo Jr. <fxjrlists@yahoo.com.br>
To: Oliveiros Cristina <oliveiros.cristina@gmail.com>
To: pgsql-interfaces@postgresql.org
Subject: Re: Question on NpgsqlParameter object
Date: Tue, 29 May 2007 11:26:34 +0100
Message-ID: <001101c7a1db$d51dd3c0$ec5a3d0a@marktestcr.marktest.pt> (raw)
References: <344577.28356.qm@web60715.mail.yahoo.com>
Howdy, Francisco.
Thank you for your fast reply.
I'm gonna check this out.
Actually I wasn't aware of the existence of the Npgsql mailing list, even though I use it exclusively to access the back end !
But, maybe if I am a little more specific you can tell me what I am (potentially) doing wrong.
Can I use parameters to substitute a whole condition?
For ex, is it possible to have a query like this?
SELECT *
FROM t_tabela
WHERE @condicao
?
My problems started yesterday when I started using parameters in this way.
Before I've just used it in situations like this :
SELECT *
FROM t_tabela
WHERE variacao >= @percentagem
and it always worked without the smallest problem.
I wonder if it is legal to use NpgsqlParameters in the way I do now...
Melhores cumprimentos,
Oliveiros
----- Original Message -----
From: Francisco Figueiredo Jr.
To: Oliveiros Cristina ; pgsql-interfaces@postgresql.org
Sent: Monday, May 28, 2007 11:32 PM
Subject: Res: [INTERFACES] Question on NpgsqlParameter object
Hi Oliveiros!
Unfortunately it is not possible with current state to get this text.
You will have to enable either Npgsql Log or postgresql log.
Just add those lines:
// Enable logging. NpgsqlEventLog.Level = LogLevel.Debug; NpgsqlEventLog.LogName = "NpgsqlTests.LogFile";
It will show you all the commands sent to server.
You can also get support from Npgsql mail list and forum. Check out Npgsql project page:
http://npgsql.projects.postgresql.org
I hope it helps.
--
Regards,
Francisco Figueiredo Jr.
http://fxjr.blogspot.com
Npgsql Lead Developer
http://npgsql.projects.postgresql.org
MonoBrasil Project Founder Member
http://monobrasil.softwarelivre.org
"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
- Indira Gandhi
----- Mensagem original ----
De: Oliveiros Cristina <oliveiros.cristina@gmail.com>
Para: pgsql-interfaces@postgresql.org
Enviadas: Segunda-feira, 28 de Maio de 2007 14:36:52
Assunto: [INTERFACES] Question on NpgsqlParameter object
Hi, List.
I am not 100% sure if this is the right list, if it isnt please kindly re-direct me to the proper list.
I would like to see NpgsqlCommand.CommandText value after parameter substitution. I have a query that is not behaving correctly and I suspect strongly that it has to do with parameters getting instantiated in unexpected ways.
How can I have access to query SQL text after parameter substitution ?
I try to look at CommandText Property immediately before calling ExecuteReader() method, but I get the text with all parameters unsubstituted.
Any Help/Comments/Advices deeply appreciated
Thanks in advance
Cheers,
Oliveiros
__________________________________________________
Fale com seus amigos de graça com o novo Yahoo! Messenger
http://br.messenger.yahoo.com/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: oliveiros.cristina@marktest.pt, fxjrlists@yahoo.com.br, oliveiros.cristina@gmail.com
Subject: Re: Question on NpgsqlParameter object
In-Reply-To: <001101c7a1db$d51dd3c0$ec5a3d0a@marktestcr.marktest.pt>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox