On Wed, Jun 18, 2008 at 1:35 PM, Fernando Hevia <[EMAIL PROTECTED]> wrote:
>
>> -Mensaje original-
>> De: [EMAIL PROTECTED]
>> [mailto:[EMAIL PROTECTED] En nombre de Patrick
>> Scharrenberg
>> Enviado el: Martes, 17 de Junio de 2008 17:46
>> Para: pgsql-sql@postgresql.org
>> Asunto: [SQL] u
> -Mensaje original-
> De: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] En nombre de Patrick
> Scharrenberg
> Enviado el: Martes, 17 de Junio de 2008 17:46
> Para: pgsql-sql@postgresql.org
> Asunto: [SQL] using calculated column in where-clause
>
> Hi!
>
> I'd like to do some calculat
Hello,
The Default method is btree, that is the commonly method used in the
indexes.
Rafael Domiciano
DBA Postgres
Senffnet
2008/6/18 Jorge Medina <[EMAIL PROTECTED]>:
> hi list,
> when I do:
> CREATE INDEX name_index ON some_table (some_col);
> what method(hash,btree,rtree,etc.) use by default
hi list,
when I do:
CREATE INDEX name_index ON some_table (some_col);
what method(hash,btree,rtree,etc.) use by default?
--
Jorge Andrés Medina Oliva.
Systems Manager and Developer.
BSDCHiLE.
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
htt
Pavel Stehule wrote:
>> it's known problem - column and variable names collision, so when you
>> use any SQL statement inside procedure you have to be carefully about
>> using variable names.
Oh, I didn't took notice of that.
Now knowing it is not a bug and how it works, it makes things much easi