Michael Glaesemann writes:
> I'd like to be able to access individual elements of anyarray,
> treating them as type anyelement to take advantage of the
> polymorphism. Using pg_stats.histogram_bounds as a convenient example
> of an anyelement array, here's an example of the issue I'm running
On Jun 12, 2009, at 11:53 AM, Yaroslav Tykhiy wrote:
I cannot but ask the community a related question here: Can such
design, that is, storing quite large objects of varying size in a
PostgreSQL database, be a good idea in the first place? I used to
believe that what RDBMS were really good
On Jun 13, 2009, at 1:52 AM, Brad Schick wrote:
After a new pgsql installation the "postgres" maintenance database has
an encoding of SQL_ASCII. pgAdmin III gave me a warning about that,
and
I may want to create users or databases that are not restricted 7bit
ASCII.
SQL_ASCII <> 7 bit ASC
On Jun 13, 2009, at 12:35 AM, Christine Penner wrote:
Sam,
The problem with making it a numeric field is that I have seen
things like A123, #123a or 23-233. This is only here to make most
sorting work better, not perfect. It all depends on how they enter
the data. Wont the different forma
Hi all,
Is there any way, to know the name of indexes on a table, defined in
a database. I mean can I query something like
Select Index_name from pg_class where relname = "Table_name" .
Thanks in advance.
--- Thanks & Reagrds
Anirban Pal | Software Engineer
Newgen Software Tech
