Search Postgresql Archives

Re: Composite type evaluates to Null if any element is null

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: "Merlin Moncure" <mmoncure@xxxxxxxxx>
Subject: Re: Composite type evaluates to Null if any element is null
From: "Andrew Gould" <andrewlylegould@xxxxxxxxx>
Date: Wed, 17 Dec 2008 11:23:48 -0600
Cc: "Ketema Harris" <ketema@xxxxxxxxxx>, pgsql-general@xxxxxxxxxxxxxx
In-reply-to: <b42b73150812170850w3cc2a2far2edf72bd021e5fdc@xxxxxxxxxxxxxx>

What are composite types used for? Do they allow you to search multiple fields for a value more easily?

Thanks,

Andrew

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Follow-Ups:
- Re: Composite type evaluates to Null if any element is null
  - From: Merlin Moncure

References:
- Composite type evaluates to Null if any element is null
  - From: Ketema Harris
- Re: Composite type evaluates to Null if any element is null
  - From: Merlin Moncure

Prev by Date: Re: Composite type evaluates to Null if any element is null
Next by Date: Prevent new timeline during archive recovery
Previous by thread: Re: Composite type evaluates to Null if any element is null
Next by thread: Re: Composite type evaluates to Null if any element is null
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Postgresql & PHP] [Yosemite]

Powered by Linux