Patrik Kudo wrote:
> [...]
>
> Is it at all possible to create an index on lower(name), and in that case,
> what type of index and using what syntax?
You'll want to look at section 7.5 "Functional Indices" in the 7.1.3 'User's Guide'.
Allan.
---(end of broadcast)---
I can confirm this now works fine in current sources. No crash.
> -- Hi Kevin, and everyone!
> --
> -- I don't think that I only found a minor bug compared to
> -- the other you wrote in your last letter: the backend crash
> -- is caused by the same CHECK constraint in the child table.
> --
>
On Thu, 11 Oct 2001, Patrik Kudo wrote:
> Hi!
>
> If I want to be able to search for stringmatches using LIKE, doing
> something like the following:
>
> select id, name from table1 where lower(name) like 'somestring%';
>
> Actually I will be joining with some other table on id too, but the joi
I have read somewhere (I believe in a review of Postgres 7? Can't find it
right now though) that having BIGINT's as indexes (or primary keys) slows the
database down, since they are 64bit and not supported that good. Is this
still true? Was this ever true?
Alexander.
-
On Thu, Oct 11, 2001 at 02:28:34PM +0200, Patrik Kudo wrote:
> Hi!
>
> If I want to be able to search for stringmatches using LIKE, doing
> something like the following:
>
> select id, name from table1 where lower(name) like 'somestring%';
>
> Actually I will be joining with some other table on
Hi!
If I want to be able to search for stringmatches using LIKE, doing
something like the following:
select id, name from table1 where lower(name) like 'somestring%';
Actually I will be joining with some other table on id too, but the join
will produce a substancial amount of data to be filtere
