| From: | "Rommel the iCeMAn" <icecrew(at)gmail(dot)com> |
|---|---|
| To: | "PostgreSQL SQL Mailing List" <pgsql-sql(at)postgresql(dot)org> |
| Subject: | Re: Error with "limit" clause |
| Date: | 2006-06-14 02:37:40 |
| Message-ID: | 006801c68f5b$82a03090$1264a8c0@theport.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
> Could VB be rewriting the query behind your back? Turn on log_statement
logging, and look in the postmaster log to see what's really being sent to
the > backend ...
Exactly!
This was an oversight on my part tho. I had used the following command:
MyDataReader = MyCommand.ExecuteReader(CommandBehavior.SingleRow)
By passing the "CommandBehavior.SingleRow" parameter VB inserted the "limit
1" clause unknown to me. The solution was easy, either explicitly state
"limit 1" in my SQL query OR use the CommandBehavior.SingleRow parameter -
NOT BOTH :-)
Thanks for the input,
Rommel Edwards.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-06-14 03:27:11 | Re: Good examples of calling slony stored procedures |
| Previous Message | Mark Adan | 2006-06-14 02:30:02 | Good examples of calling slony stored procedures |