yes.
bye
Fabio
Bruce Momjian ha scritto:
Fabio Guidi wrote:
The change to include pthread.h i done by myself when i try to build
again, no problem for ecpg i change my source to run only with libpq,
thanks a lot for help ...
Great. I figured you had made that change
The change to include pthread.h i done by myself when i try to build
again, no problem for ecpg i change my source to run only with libpq,
thanks a lot for help ...
bye
Fabio
Bruce Momjian ha scritto:
[EMAIL PROTECTED] wrote:
All OK with libpq, what can i do to work under window
Fabio Guidi wrote:
> The change to include pthread.h i done by myself when i try to build
> again, no problem for ecpg i change my source to run only with libpq,
> thanks a lot for help ...
Great. I figured you had made that change on your end.
--
Bruce Momjian| htt
On Sat, Apr 30, 2005 at 07:45:29PM -0700, David Fetter wrote:
> > Not sure what your driving at here... my point is that the \
> > escaping is incorrect in the current examples.
>
> That was pretty much my thought. It's extremely easy to turn regexes
> into unmaintainable garbage, whereas the
On Sat, Apr 30, 2005 at 10:08:32PM -0400, Robert Treat wrote:
> On Saturday 30 April 2005 21:14, Alvaro Herrera wrote:
> > On Sat, Apr 30, 2005 at 06:12:27PM -0400, Robert Treat wrote:
> > > --- 167,174
> > >
> > > CREATE DOMAIN us_postal_code AS TEXT
> > > CHECK(
> > > !VALUE ~ '^\
On Saturday 30 April 2005 21:14, Alvaro Herrera wrote:
> On Sat, Apr 30, 2005 at 06:12:27PM -0400, Robert Treat wrote:
> > --- 167,174
> >
> > CREATE DOMAIN us_postal_code AS TEXT
> > CHECK(
> > !VALUE ~ '^\\d{5}$'
> > ! OR VALUE ~ '^\\d{5}-\\d{4}$'
> > );
>
> Huh, why not
>
> VAL
On Sat, Apr 30, 2005 at 06:12:27PM -0400, Robert Treat wrote:
> --- 167,174
>
> CREATE DOMAIN us_postal_code AS TEXT
> CHECK(
> !VALUE ~ '^\\d{5}$'
> ! OR VALUE ~ '^\\d{5}-\\d{4}$'
> );
Huh, why not
VALUE ~ '^\\d{5}(-\\d{4})?$'
?
--
Alvaro Herrera (<[EMAIL PROTECTED]>)
"Cuan
The example given in create domain seems to be broken. ISTM it requires some
extra escaping to be usable (at least in my goings on today it sure was, and
I the entries in pg_constraint sure seem to indicate this as well). I
suggest that the examples should be updated as per the following patch.
Neil Conway wrote:
Barring any objections, I'll apply this to HEAD and backport it to
stable branches back to 7.2 tomorrow.
Applied and backpatched. I noticed an additional pg_dump format string
bug in 7.2 and fixed that as well (it does not occur in later branches).
I also didn't bother backpor
Tom Lane wrote:
Certainly --- particularly if the error makes it dump core, as seems
likely (haven't tried it).
Ok, backpatched to stable branches back to 7.2
-Neil
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http
10 matches
Mail list logo