Subject | Re: [firebird-support] Simple SELECT statement not working Firebird-2.5.0.26083-0_Win32 |
---|---|
Author | LtColRDSChauhan |
Post date | 2010-09-16T02:38:28Z |
On Thu, Sep 16, 2010 at 1:13 AM, Helen Borrie <helebor@...> wrote:
have deployed this application on about 14 PCs in a LAN, of which one has
the FireBird server running. Since last about 8 months i did not notice any
such issue although many of my stored procedures had two date parameters
(typical from - to) with >= and <= comparisons, one thing here i must
mention that i keep moving on to the latest builds of FireBird, .NET
Provider, FlameRobin.
Anyway i will change the date literals to be without the comma.
FlameRobin] the statements generated along with the values of parameter
passed. So this is unlikely to be the cause of error.
Regards,
Lt Col (Retd) Rajiv Dular Singh Chauhan
09601704890
0265-2637655
_____________________________
[Non-text portions of this message have been removed]
>client application which executes these stored procedures is .NET 4.0. I
>
> At 06:36 AM 16/09/2010, RDS wrote:
> >1. I'm using Firebird-2.5.0.26083-0_Win32 on Windows 7 OS.
> >2. For an existing record in table a PATIENTCHARGESDUES, the under
> mentioned select statement does not returns the exisiting record when i
> uncomment the line that compares field ENTRYTIME even on copy paste the
> field value. Rest all fields work fine. I've tried removing zeros event ie
> '15.9.2010, 20:40:06.674'
> select * from PATIENTCHARGESDUES p where
> p.SERVICEID='2300094' and
> p.AMOUNT=2000 and
> p.AMOUNT_BEFORE_DISCOUNT = 2000 and
> p.HOSPSRVCDESC='OUT PATIENT' and
> p.REMARKS='1x1800. ' and
> p.DATEOFEXPENSE = '15.9.2010, 20:20:14.8230'
> *** 1 ***
>
> and
> p.ENTEREDBY = 'HISADMIN' and
> p.ENTRYPC = 'NannuPC'
>
> /*and
> p.ENTRYTIME='15.09.2010, 20:40:06.674'
> *** 2****
> *** 3 ***
>
> p.REGDID=:REGDID and
> p.RECEIPTANTID=:RECEIPTANTID;*/
> *** 4 ***
>
> 1 and 2 : comma is not valid in a date literal. Separate the date and time
> parts with a single blank. However, if you didn't get an exception from
> these literals then possibly the *parser* has been taught to ignore the
> extraneous comma....don't know....best to provide known-to-be-valid
> literals, however.
>
> I'm using FlameRobin 0.93.1924 to write and test stored procedures. My
have deployed this application on about 14 PCs in a LAN, of which one has
the FireBird server running. Since last about 8 months i did not notice any
such issue although many of my stored procedures had two date parameters
(typical from - to) with >= and <= comparisons, one thing here i must
mention that i keep moving on to the latest builds of FireBird, .NET
Provider, FlameRobin.
Anyway i will change the date literals to be without the comma.
> 3. Missing ANDSorry ma'am. That was a cut-paste error. My apologies.
>
>While debugging my client .NET application i do check [copy and run on
> 4. The query will not return any results if you don't supply values for
> parameters. Your driver interface should prepare the statement on the
> initial request and then pass one or more subsequent requests that supply
> the parameters.
>
FlameRobin] the statements generated along with the values of parameter
passed. So this is unlikely to be the cause of error.
>--
> ./heLen
>
> Thanks a lot ma'am.
>
>
Regards,
Lt Col (Retd) Rajiv Dular Singh Chauhan
09601704890
0265-2637655
_____________________________
[Non-text portions of this message have been removed]