From: | lbayuk(at)mindspring(dot)com (ljb) |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Re: copy to/from stdout using libpgtcl |
Date: | 2001-08-13 01:28:22 |
Message-ID: | 9l7afm$jm$2@news.tht.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-patches |
tgl(at)sss(dot)pgh(dot)pa(dot)us wrote:
>Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
>> Is this safe to put into the main code? It looks fine.
Looks fine to me too, but I suppose you want to know if it works and
doesn't break anything else...
The original poster may be able to answer this with more confidence.
>It looks to me like it'll break compatibility with all pre-8.3 Tcls.
>Need some #ifdef's in there, no?
No, I don't think so. It still uses the older "Tcl v1 channel type"
structure, not the newer one introduced in Tcl 8.3.2. Should be
OK back through 8.0, although I base this only on an eyeball-check
of the Tcl 8.0.5 include files.
From | Date | Subject | |
---|---|---|---|
Next Message | Randall Perry | 2001-08-13 03:48:12 | Re: Constraint, Rule, or Trigger? |
Previous Message | newsreader | 2001-08-13 01:21:31 | Re: Re: select distinct |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-08-13 02:06:43 | Re: [JDBC] JDBC pg_description update needed for CVS tip |
Previous Message | ljb | 2001-08-13 01:20:58 | Re: copy to/from stdout using libpgtcl |