Subject | Re: [firebird-support] Performance Question |
---|---|
Author | Todd E. Brasseur |
Post date | 2004-05-19T18:39:46Z |
Tim Ledgerwood wrote:
would think if it was bad data, it wouldn't be able to be fixed this way.
I made an error earlier in that the assessmentyear column is a smallint
not an integer. When I cast it to an integer, the proper records are
returned.
doesn't get fixed with a backup and restore. But how does it get it
there when the primary key has been defined. The database should have
fired an exception and not allowed the data.
Todd
>If it is bad data, would it fix itself by doing a backup and restore. I
> >
> >It is strange:
> >
> >What will happen is a 'ghost' record will appear. If I do a:
> >
> >Select * from taxpassoff where Propid = 1220000000
> >
> >I will get four records (All showing that they have AssessmentYear =
> 2004)
> >
> >If I change the select to:
> >
> >Select * from taxpassoff where Propid = 1220000000 and AssessmentYear
> = 2004
> >
> >I only get 3 records. AssessmentYear and PropID are both INTEGERS.
> >
> >If I change the select to:
> >
> >Select * from taxpassoff where Propid = 1220000000 and
> >cast(AssessmentYear as INTEGER) = 2004
> >
> >I will see all four records.
> >
> >This table may have 120,000 records in it and every once in a while
> >there will be 1 to 4 records that have done this.
>
> I would suspect that you are getting bad data into the table. That is
> where
> I would look first. I have never heard of "ghost" data in
> Firebird/Interbase -
> you see what is there. You cannot see what is not yet committed. There
> is no
> such thing as "dirty read" in Interbase/Firebird.
would think if it was bad data, it wouldn't be able to be fixed this way.
I made an error earlier in that the assessmentyear column is a smallint
not an integer. When I cast it to an integer, the proper records are
returned.
>I can see that bad data is the problem with the primary key error. It
> If you were getting bad data into this table, that would also explain
> the key
> violation you are getting.
doesn't get fixed with a backup and restore. But how does it get it
there when the primary key has been defined. The database should have
fired an exception and not allowed the data.
Todd
>[Non-text portions of this message have been removed]
>
> Regards
>
> Tim
>
>
> [Non-text portions of this message have been removed]
>
>
> Yahoo! Groups Sponsor
> ADVERTISEMENT
> <http://rd.yahoo.com/SIG=1299kdoup/M=295196.4901138.6071305.3001176/D=groups/S=1705115386:HM/EXP=1085029324/A=2128215/R=0/SIG=10se96mf6/*http://companion.yahoo.com>
>
>
>
> ------------------------------------------------------------------------
> Yahoo! Groups Links
>
> * To visit your group on the web, go to:
> http://groups.yahoo.com/group/firebird-support/
>
> * To unsubscribe from this group, send an email to:
> firebird-support-unsubscribe@yahoogroups.com
> <mailto:firebird-support-unsubscribe@yahoogroups.com?subject=Unsubscribe>
>
> * Your use of Yahoo! Groups is subject to the Yahoo! Terms of
> Service <http://docs.yahoo.com/info/terms/>.
>
>