> Making use of this seems to fix the original bug - and possibly the
> SIGINT stealing too.
>
> Patch attached to set the variable (R_SignalHandlers = 0), and remove
> the SIGINT workaround.
Cool -- thanks. Maybe that got added in a release since last I looked.
Joe
--
Joe
t (breaking each column on a
separate line) was done to improve readability but it has the side
effect of making the text unreadable if processed via a YAML utility
such as Pyrseas dbtoyaml (since YAML then quotes the entire string and
even breaks it down further with extra backslashes).
Regards,
the
documentation:
http://www.postgresql.org/docs/9.2/interactive/tablefunc.html
If you still have a problem please provide SQL that can be cut and
pasted which:
1) create your table
2) insert sample rows
Then show us what out put you are trying to acheive as output from
that data.
Joe
- --
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/22/2013 04:17 PM, Joe Conway wrote:
> If you still have a problem please provide SQL that can be cut and
> pasted which: 1) create your table 2) insert sample rows Then show
> us what out put you are trying to acheive as output from th
I know the Information Schema is a SQL standard, but it's somewhat lacking.
I was trying to write a web page that showed a db table,it's columns and
foreign keys.
All went well and I was able to get this tool working great using the
information_schema, problem is that some of the information_sche
The following bug has been logged online:
Bug reference: 5179
Logged by: Joe Marshal Mathew
Email address: joemarshalmat...@gmail.com
PostgreSQL version: 8.3
Operating system: Windows vista ultimate 64 bit
Description:Installation fails
Details:
The installation
It's looking like I can use a plpgsql function to insert data into a table
that violates a domain constraint. Is this a known problem?
Session 1:
create domain my_domain text check (length(value) > 2);
create table my_table (name my_domain);
create function f(text) returns void as $$
declare my_
101 - 107 of 107 matches
Mail list logo
