> No, that's the point of the sentence about the range mechanisms not
> understanding special values of the underlying type. upper_inf tests
> for a range with no upper bound, period. It would need some
> type-specific special knowledge to do what you're hoping for, and it
> has not got that.
Go
Hi,
> select upper_inf(tsrange('2013-05-01'::timestamp, 'infinity'::timestamp,
> '[]'));
upper_inf
---
f
(1 row)
As far as I understood the docs, this query should return true, as the upper
bound includes 'infinity'?
[http://www.postgresql.org/docs/9.2/interactive/functions-range.ht
Hi Adrian,
>> II) Having PostgreSQL issuing a NOTICE that "comments get stripped" if you
>> use comments somewhere where PostgreSQL accepts them, but discards them
>> silently?
>
> I think that is covered by this:
> http://www.postgresql.org/docs/9.0/interactive/sql-syntax-lexical.html#SQL-SYNTAX
Hi David,
> The fact that you can write comments in the middle of the arguments in an
> artifact of the parser and likely there is not reasonable way to get them to
> persist.
"Artifact" as in "something not normally used"?
> You either want to use "COMMENT ON" like Raymond said or you can
> sim
Hello Ray,
> You could use COMMENT ON instead:
>
> COMMENT ON function func_test(text, text)
> IS 'loads of documentation here';
>
> Would this do the job?
Thank you for your input.
I know about the COMMENT ON function, as I use it for all other purposes, like
documenting columns an
Hi,
How can I store inline comments in the argument list of a plpgsql function to
document complex overloaded functions with lots of arguments? It seems that
PostgreSQL accepts the comments, but strips them as the function gets stored.
I am using PostgreSQL 9.1.2.
+++
CREATE FUNCTION func_test
Hi David!
> Sorry for not answering the main question but you really need to avoid
> phrases like "near future". That said, new features are only released
> during major releases and so at best you would have to wait for 9.2 which is
> probably 9+ months out since 9.1 was just recently released.
Hi!
As of PostgreSQL 9.1 it is not possible to declare check constraints on
composite types, according to
http://www.postgresql.org/docs/9.1/interactive/rowtypes.html. I cannot use
domains in that particular context, because I want to have the check constraint
check for a combination of fields
Hello,
I am running PostgreSQL 8.4.2. For the testcase I have a database, a
user, and two schemas within the database. Two tables in those two
different schemas have the same name, but only on of those tables
shows up using the "\dt" command.
How-To-Repeat:
-- psql template1
CREATE ROLE
Hi Tom,
Yes, because (loosely speaking) OLD refers to the view, and once you've
done the INSERT there is now another matching row in the view. Try
doing the UPDATE first, then the INSERT.
First of all thanks alot for your input. - If I change the order of the
statement, so the UPDATE comes before
Hello,
I posted the question below to the pgsql-sql list, but did not receive any
answer yet. Therefore I repost it on pgsql-general in hope for any
information regarding that issue. Thanks alot.
Best regards
... Ralph ...
---
given is a table with a version history kind of thing I am currently
11 matches
Mail list logo
