Subject | Re: ORDER BY on large VARCHAR columns |
---|---|
Author | robert_difalco |
Post date | 2004-10-27T20:50:15Z |
--- In firebird-support@yahoogroups.com, "Ann W. Harrison"
<aharrison@i...> wrote:
frequently than they are read and they are NEVER updated. What do
you have in mind? Just beware that this is only one of the columns
we sort on. Consider a graphical paged table of these things and
that the user can click on any column to order them. I can disable
the column sortability on some fields, but not on this large one and
not on all BUT this large one.
R.
<aharrison@i...> wrote:
>Yep, that was pretty apparent.
> First...skip is about the worst thing you can possibly do,
> since it evaluates the whole record set every time. Yo
>I don't mind taking a hit on insert. They are inserted much less
> How often do you insert new data or update the long field on
> existing records?
>
frequently than they are read and they are NEVER updated. What do
you have in mind? Just beware that this is only one of the columns
we sort on. Consider a graphical paged table of these things and
that the user can click on any column to order them. I can disable
the column sortability on some fields, but not on this large one and
not on all BUT this large one.
R.