Are the fields you are usiong varchar or char.
If they are char fields they will be getting padded if you do not have the
exact amount in the field. i.e.
char(5)
da will be padded da and 0s on the end up to the sizeof the char field.
If varchar then you will be ok.
If you do have a char then use the trim function to do the selects
HTH
Darren
On Fri, 24 Oct 2003 Lynn.Tilby@asu.edu wrote:
>
> running - (PostgreSQL) 7.1.3
>
> I have loaded a table with stock market data.
>
> -
> -
> -
> ZRAN |2003-09-29| 20030929| 731487| 20.81| 20.
> ZRAN |2003-09-30| 20030930| 731488| 19.43| 20.1
> ZRAN |2003-10-01| 20031001| 731489| 19.82| 19.9
> ZRAN |2003-10-02| 20031002| 731490| 19.56| 20.3
> ZRAN |2003-10-03| 20031003| 731491| 20.25| 21.
> (609398 rows)
>
> pma=> select count(*) from stck_dta_tbl_oprtnl;
> count
> ------
> 609398
>
> When I do a select * from stck_dta_tbl_oprtnl; I get the whole table
> just fine; but when I try and retrieve just 1 record which is out
> put when doing the select * ie:
>
> pma=> select * from stck_dta_tbl_oprtnl where stck_sym = 'ZRAN';
> stck_sym|dta_date|dta_date_num|dta_date_dys|opn|hi|lw|cls|vol|unk
> --------+--------+------------+------------+---+--+--+---+---+---
> (0 rows)
>
> I get 0 rows, and no errors from postmaster.
>
> Is there a limit to the number of rows in a table?
> I have also tried building a unique index composed of the stck_sym and
> dta_date but I still get 0 rows.
>
> I have also noticed that when setting up a cursor that the first fetch
> does NOT get the first record in the table, it also returns nothing with
> no errors from the postmaster. I am wondering if these bugs are related.
>
> Thanks all for your help!!!!
>
> Lynn
>
>
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>
--
Darren Ferguson
