From jinujosein@yahoo.com Thu Sep 25 03:36:23 2003 X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 9B6B9D1B525 for ; Thu, 25 Sep 2003 03:36:23 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 49212-07 for ; Thu, 25 Sep 2003 00:35:52 -0300 (ADT) Received: from web14915.mail.yahoo.com (web14915.mail.yahoo.com [216.136.225.228]) by svr1.postgresql.org (Postfix) with SMTP id 4750ED1B527 for ; Thu, 25 Sep 2003 00:35:51 -0300 (ADT) Message-ID: <20030925033550.35699.qmail@web14915.mail.yahoo.com> Received: from [202.9.168.87] by web14915.mail.yahoo.com via HTTP; Wed, 24 Sep 2003 20:35:50 PDT Date: Wed, 24 Sep 2003 20:35:50 -0700 (PDT) From: "George A.J" Subject: Case Insensitive comparison To: pgsql-sql@postgresql.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1735026683-1064460950=:34670" X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200309/290 X-Sequence-Number: 15268 --0-1735026683-1064460950=:34670 Content-Type: text/plain; charset=us-ascii hai i am using postgresql 7.3.x. I am converting a database in MS SQL server to PostgreSQL. The main problems i am facing is that in sql server the text comparisons are case insensitive. how can i compare text case insensitive in postgresql without using an upper() or lower() function in both sides (=). Is there any option to set in postgresql? Is there any problem in overriding the = operator that compare text. ie droping the current operator = and creating a new = operator(text,text). Does the existing = operator is using internally by postgres for some porpose. please help Another problem is in creating function... How can i create a function that accept and return any type. the type "any" is not allowing as parameter or return type. Is it possible? i want to create a function similar to NULLIF(). jinujose --------------------------------- Do you Yahoo!? The New Yahoo! Shopping - with improved product search --0-1735026683-1064460950=:34670 Content-Type: text/html; charset=us-ascii
hai
 
i am using postgresql 7.3.x. I am converting a database in MS SQL server to PostgreSQL.
 
The main problems i am facing is that in sql server the text comparisons are case insensitive. how can i compare text case insensitive in postgresql without using an upper() or lower() function in both sides (=). Is there any option to set in postgresql?
Is there any problem in overriding the = operator that compare text. ie droping the current operator = and creating a new = operator(text,text). Does the existing = operator is using internally by postgres for some porpose. please help
 
Another problem is in creating function...
How can i create a function that accept and return any type. the type "any" is not allowing as parameter or return type. Is it possible? i want to create a function similar to NULLIF().
 
jinujose
 
 


Do you Yahoo!?
The New Yahoo! Shopping - with improved product search --0-1735026683-1064460950=:34670-- From josh@agliodbs.com Thu Sep 25 04:45:41 2003 X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id C28C2D1B577 for ; Thu, 25 Sep 2003 04:45:41 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 55670-05 for ; Thu, 25 Sep 2003 01:45:31 -0300 (ADT) Received: from davinci.ethosmedia.com (unknown [209.128.84.228]) by svr1.postgresql.org (Postfix) with ESMTP id 944E9D1B519 for ; Thu, 25 Sep 2003 01:45:30 -0300 (ADT) Received: from [63.195.55.98] (HELO spooky) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 3678610; Wed, 24 Sep 2003 21:46:01 -0700 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Organization: Aglio Database Solutions To: "George A.J" , pgsql-sql@postgresql.org Subject: Re: Case Insensitive comparison Date: Wed, 24 Sep 2003 21:45:21 -0700 User-Agent: KMail/1.4.3 References: <20030925033550.35699.qmail@web14915.mail.yahoo.com> In-Reply-To: <20030925033550.35699.qmail@web14915.mail.yahoo.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200309242145.21087.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200309/292 X-Sequence-Number: 15270 jinujose, > i am using postgresql 7.3.x. I am converting a database in MS SQL server to > PostgreSQL. Good luck to you! > The main problems i am facing is that in sql server the text comparisons > are case insensitive. how can i compare text case insensitive in postgresql > without using an upper() or lower() function in both sides (=). Is there > any option to set in postgresql? Is there any problem in overriding the = > operator that compare text. ie droping the current operator = and creating > a new = operator(text,text). Does the existing = operator is using > internally by postgres for some porpose. please help I would *not* suggest modifying such a fundamental operator; you are very likely to break something. You can use "ILIKE" to compare text: 'Joe' ILIKE 'joE' == true You can also use the "regex" operator: 'Joe' ~* '^jOE$' == TRUE ... but that takes more adaptation. However, neither of the above approaches can be indexed. > Another problem is in creating function... > How can i create a function that accept and return any type. the type "any" > is not allowing as parameter or return type. Is it possible? i want to > create a function similar to NULLIF(). You can't, nor will you be able to -- in te future, some 7.4 functions will be able to *accept* any type, but they will still return a specific type. Instead, you need to create a seperate NULLIF() for each data type you're likely to use. -- Josh Berkus Aglio Database Solutions San Francisco From sszabo@megazone.bigpanda.com Thu Sep 25 05:19:18 2003 X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 4CE08D1B522 for ; Thu, 25 Sep 2003 05:19:18 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 62568-05 for ; Thu, 25 Sep 2003 02:19:08 -0300 (ADT) Received: from megazone.bigpanda.com (megazone.bigpanda.com [64.147.171.210]) by svr1.postgresql.org (Postfix) with ESMTP id 9A6C2D1B50E for ; Thu, 25 Sep 2003 02:19:07 -0300 (ADT) Received: by megazone.bigpanda.com (Postfix, from userid 1001) id 2B2ED35014; Wed, 24 Sep 2003 22:19:08 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by megazone.bigpanda.com (Postfix) with ESMTP id 2A14834DEF; Wed, 24 Sep 2003 22:19:08 -0700 (PDT) Date: Wed, 24 Sep 2003 22:19:08 -0700 (PDT) From: Stephan Szabo To: "George A.J" Cc: pgsql-sql@postgresql.org Subject: Re: Case Insensitive comparison In-Reply-To: <20030925033550.35699.qmail@web14915.mail.yahoo.com> Message-ID: <20030924221627.E70696@megazone.bigpanda.com> References: <20030925033550.35699.qmail@web14915.mail.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200309/294 X-Sequence-Number: 15272 On Wed, 24 Sep 2003, George A.J wrote: > The main problems i am facing is that in sql server the text comparisons > are case insensitive. how can i compare text case insensitive in > postgresql without using an upper() or lower() function in both sides > (=). Is there any option to set in postgresql? > > Is there any problem in overriding the = operator that compare text. ie > droping the current operator = and creating a new = operator(text,text). > Does the existing = operator is using internally by postgres for some > porpose. please help Well, you'd really want to change all the comparison operators because otherwise I think indexes would be screwy and I don't know off hand if this will cause problems, but I can imagine that it might, if only on queries from clients and such on the system catalogs. One other option is to find or make a case insensitive collating locale for your operating system and use that when initializing the database. I've never tried so I can't say whether that'll have its own problems. From rmello@cc.usu.edu Thu Sep 25 05:30:57 2003 X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 532F7D1B50E for ; Thu, 25 Sep 2003 05:30:57 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 64688-02 for ; Thu, 25 Sep 2003 02:30:27 -0300 (ADT) Received: from brasileiro.net (slxwy.dorms.usu.edu [129.123.227.103]) by svr1.postgresql.org (Postfix) with ESMTP id 838F9D1B52A for ; Thu, 25 Sep 2003 02:30:09 -0300 (ADT) Received: from roberto by brasileiro.net with local (Exim 3.36 #1 (Debian)) id 1A2Ohd-0001TG-00; Wed, 24 Sep 2003 23:30:09 -0600 Date: Wed, 24 Sep 2003 23:30:08 -0600 From: Roberto Mello To: "George A.J" Cc: pgsql-sql@postgresql.org Subject: Re: Case Insensitive comparison Message-ID: <20030925053008.GC4203@cc.usu.edu> References: <20030925033550.35699.qmail@web14915.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <20030925033550.35699.qmail@web14915.mail.yahoo.com> X-message-flag: Please consider using an e-mail program other than Outlook. It's insecure. User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200309/295 X-Sequence-Number: 15273 On Wed, Sep 24, 2003 at 08:35:50PM -0700, George A.J wrote: > hai > > i am using postgresql 7.3.x. I am converting a database in MS SQL server to PostgreSQL. > > The main problems i am facing is that in sql server the text comparisons are case insensitive. how can i compare text case insensitive in postgresql without using an upper() or lower() function in both sides (=). Is there any option to set in postgresql? > Is there any problem in overriding the = operator that compare text. ie droping the current operator = and creating a new = operator(text,text). Does the existing = operator is using internally by postgres for some porpose. please help Souinds like MS-SQL has broken behavior. Use ILIKE, but I can't remember if you lose indice seaches with that. Overriding the operator should be ok, but again I don't know what the impact on index usage would be. > Another problem is in creating function... > How can i create a function that accept and return any type. the type "any" is not allowing as parameter or return type. Is it possible? i want to create a function similar to NULLIF(). Use the standard coalesce(). -Roberto -- +----| Roberto Mello - http://www.brasileiro.net/ |------+ + Computer Science Graduate Student, Utah State University + + USU Free Software & GNU/Linux Club - http://fslc.usu.edu/ + MONEY TALKS ... but all mine ever says is GOODBYE! From tgl@sss.pgh.pa.us Thu Sep 25 05:50:15 2003 X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 1C497D1B561 for ; Thu, 25 Sep 2003 05:50:15 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 64651-05 for ; Thu, 25 Sep 2003 02:50:05 -0300 (ADT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 4017ED1B544 for ; Thu, 25 Sep 2003 02:50:04 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.10/8.12.10) with ESMTP id h8P5o2iP002177; Thu, 25 Sep 2003 01:50:02 -0400 (EDT) To: Josh Berkus Cc: "George A.J" , pgsql-sql@postgresql.org Subject: Re: Case Insensitive comparison In-reply-to: <200309242145.21087.josh@agliodbs.com> References: <20030925033550.35699.qmail@web14915.mail.yahoo.com> <200309242145.21087.josh@agliodbs.com> Comments: In-reply-to Josh Berkus message dated "Wed, 24 Sep 2003 21:45:21 -0700" Date: Thu, 25 Sep 2003 01:50:02 -0400 Message-ID: <2176.1064469002@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200309/296 X-Sequence-Number: 15274 Josh Berkus writes: >> How can i create a function that accept and return any type. the type "any" >> is not allowing as parameter or return type. Is it possible? i want to >> create a function similar to NULLIF(). > You can't, nor will you be able to -- in te future, some 7.4 functions will be > able to *accept* any type, but they will still return a specific type. Au contraire. The 7.4 polymorphic-function features may well solve jinujose's problem, if he can indeed write a type-independent function body. For example create function nullif(anyelement, anyelement) returns anyelement as 'select case when $1 = $2 then null else $1 end' language sql; I'm not sure we're all the way there yet, cf http://archives.postgresql.org/pgsql-general/2003-09/msg00500.php regards, tom lane From bruno@wolff.to Thu Sep 25 13:14:14 2003 X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id B2AF6D1B51A for ; Thu, 25 Sep 2003 13:14:14 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 98494-09 for ; Thu, 25 Sep 2003 10:13:47 -0300 (ADT) Received: from wolff.to (wolff.to [66.93.249.74]) by svr1.postgresql.org (Postfix) with SMTP id 48F17D1B4E1 for ; Thu, 25 Sep 2003 10:13:43 -0300 (ADT) Received: (qmail 27521 invoked by uid 500); 25 Sep 2003 13:20:46 -0000 Date: Thu, 25 Sep 2003 08:20:46 -0500 From: Bruno Wolff III To: Roberto Mello Cc: "George A.J" , pgsql-sql@postgresql.org Subject: Re: Case Insensitive comparison Message-ID: <20030925132046.GA27357@wolff.to> Mail-Followup-To: Roberto Mello , "George A.J" , pgsql-sql@postgresql.org References: <20030925033550.35699.qmail@web14915.mail.yahoo.com> <20030925053008.GC4203@cc.usu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030925053008.GC4203@cc.usu.edu> User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200309/307 X-Sequence-Number: 15285 On Wed, Sep 24, 2003 at 23:30:08 -0600, Roberto Mello wrote: > On Wed, Sep 24, 2003 at 08:35:50PM -0700, George A.J wrote: > > > Another problem is in creating function... > > How can i create a function that accept and return any type. the type "any" is not allowing as parameter or return type. Is it possible? i want to create a function similar to NULLIF(). > > Use the standard coalesce(). coalesce is used to do the inverse of nullif. Postgres also has a nullif function. I suspect that he relly doesn't want to use either of those, but instead wants to have some function that returns the same type as its argument without having to write one function for each different type. There is something along those lines coming in 7.4. From jinujosein@yahoo.com Thu Sep 25 14:04:36 2003 X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id CAD91D1B4E6 for ; Thu, 25 Sep 2003 14:04:36 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 07636-01 for ; Thu, 25 Sep 2003 11:04:08 -0300 (ADT) Received: from web14908.mail.yahoo.com (web14908.mail.yahoo.com [216.136.225.60]) by svr1.postgresql.org (Postfix) with SMTP id 30FCCD1B51A for ; Thu, 25 Sep 2003 11:04:04 -0300 (ADT) Message-ID: <20030925140407.64555.qmail@web14908.mail.yahoo.com> Received: from [202.9.168.38] by web14908.mail.yahoo.com via HTTP; Thu, 25 Sep 2003 07:04:07 PDT Date: Thu, 25 Sep 2003 07:04:07 -0700 (PDT) From: "George A.J" Subject: Re: Case Insensitive comparison To: pgsql-sql@postgresql.org In-Reply-To: <2176.1064469002@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-667277437-1064498647=:63977" X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200309/308 X-Sequence-Number: 15286 --0-667277437-1064498647=:63977 Content-Type: text/plain; charset=us-ascii Thanks to all of you for your valuable suggesstions.... does postgresql internally uses the = operator(text,text) for any other purposes. i think that overloading it solves the index problem too... Tom Lane wrote: Josh Berkus writes: >> How can i create a function that accept and return any type. the type "any" >> is not allowing as parameter or return type. Is it possible? i want to >> create a function similar to NULLIF(). > You can't, nor will you be able to -- in te future, some 7.4 functions will be > able to *accept* any type, but they will still return a specific type. Au contraire. The 7.4 polymorphic-function features may well solve jinujose's problem, if he can indeed write a type-independent function body. For example create function nullif(anyelement, anyelement) returns anyelement as 'select case when $1 = $2 then null else $1 end' language sql; I'm not sure we're all the way there yet, cf http://archives.postgresql.org/pgsql-general/2003-09/msg00500.php regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster --------------------------------- Do you Yahoo!? The New Yahoo! Shopping - with improved product search --0-667277437-1064498647=:63977 Content-Type: text/html; charset=us-ascii

Thanks to all of you for your valuable suggesstions....
does postgresql internally uses the = operator(text,text) for any other purposes.
i think that overloading it solves the index problem too...
 
 

Tom Lane <tgl@sss.pgh.pa.us> wrote:
Josh Berkus writes:
>> How can i create a function that accept and return any type. the type "any"
>> is not allowing as parameter or return type. Is it possible? i want to
>> create a function similar to NULLIF().

> You can't, nor will you be able to -- in te future, some 7.4 functions will be
> able to *accept* any type, but they will still return a specific type.

Au contraire. The 7.4 polymorphic-function features may well solve
jinujose's problem, if he can indeed write a type-independent function
body. For example

create function nullif(anyelement, anyelement) returns anyelement as
'select case when $1 = $2 then null else $1 end' language sql;

I'm not sure we're all the way there yet, cf
http://archives.postgresql.org/pgsql-general/2003-09/msg00500.php

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster


Do you Yahoo!?
The New Yahoo! Shopping - with improved product search --0-667277437-1064498647=:63977-- From josh@agliodbs.com Fri Sep 26 03:47:07 2003 X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 2D098D1B51D for ; Fri, 26 Sep 2003 03:47:07 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 08993-02 for ; Fri, 26 Sep 2003 00:46:56 -0300 (ADT) Received: from davinci.ethosmedia.com (unknown [209.128.84.228]) by svr1.postgresql.org (Postfix) with ESMTP id 27FE1D1B4F2 for ; Fri, 26 Sep 2003 00:46:56 -0300 (ADT) Received: from [63.195.55.98] (HELO spooky) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 3682380; Thu, 25 Sep 2003 20:47:27 -0700 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Organization: Aglio Database Solutions To: Roberto Mello , "George A.J" Subject: Re: Case Insensitive comparison Date: Thu, 25 Sep 2003 20:46:39 -0700 User-Agent: KMail/1.4.3 Cc: pgsql-sql@postgresql.org References: <20030925033550.35699.qmail@web14915.mail.yahoo.com> <20030925053008.GC4203@cc.usu.edu> In-Reply-To: <20030925053008.GC4203@cc.usu.edu> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200309252046.39636.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200309/321 X-Sequence-Number: 15299 Roberto, > > Another problem is in creating function... > > How can i create a function that accept and return any type. the type > > "any" is not allowing as parameter or return type. Is it possible? i want > > to create a function similar to NULLIF(). > > Use the standard coalesce(). NULLIF is the converse of COALESCE(). Any idea when you're going to overhaul the CookBook? -- Josh Berkus Aglio Database Solutions San Francisco From rmello@cc.usu.edu Fri Sep 26 17:40:17 2003 X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 4604ED1B533 for ; Fri, 26 Sep 2003 17:40:17 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 82718-06 for ; Fri, 26 Sep 2003 14:40:07 -0300 (ADT) Received: from brasileiro.net (slxwy.dorms.usu.edu [129.123.227.103]) by svr1.postgresql.org (Postfix) with ESMTP id 6B608D1B51C for ; Fri, 26 Sep 2003 14:39:51 -0300 (ADT) Received: from roberto by brasileiro.net with local (Exim 3.36 #1 (Debian)) id 1A2wZE-00083j-00; Fri, 26 Sep 2003 11:39:44 -0600 Date: Fri, 26 Sep 2003 11:39:44 -0600 From: Roberto Mello To: Josh Berkus Cc: "George A.J" , pgsql-sql@postgresql.org Subject: Re: Case Insensitive comparison Message-ID: <20030926173944.GC30772@cc.usu.edu> References: <20030925033550.35699.qmail@web14915.mail.yahoo.com> <20030925053008.GC4203@cc.usu.edu> <200309252046.39636.josh@agliodbs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <200309252046.39636.josh@agliodbs.com> X-message-flag: Please consider using an e-mail program other than Outlook. It's insecure. User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200309/334 X-Sequence-Number: 15312 On Thu, Sep 25, 2003 at 08:46:39PM -0700, Josh Berkus wrote: > > NULLIF is the converse of COALESCE(). Oh, ooops! My apologies. > Any idea when you're going to overhaul the CookBook? *sighs* The software is pretty much ready. I'll have time to install and configure it next week, after my exams. -Roberto -- +----| Roberto Mello - http://www.brasileiro.net/ |------+ + Computer Science Graduate Student, Utah State University + + USU Free Software & GNU/Linux Club - http://fslc.usu.edu/ +