Dear Tom,
I think that the inability to convert nearly binary compatible standard
types one to the other is a postgresql issue. Even if it is not often
useful, the point is completeness and soundness of the type provided by
the core.
OK, can I get some feedback from others about this patch?
Dear Bruce,
I am not sure this is of general enough usefulness to be in the backend.
Hmm...
I think that the inability to convert nearly binary compatible standard
types one to the other is a postgresql issue. Even if it is not often
useful, the point is completeness and soundness of the
Dear PostgreSQL developers,
Please find attached a small patch to convert bytea to bit strings and
vice versa.
I used it in order to be able xor md5 results so as to checksum bundles of
tuples together. The MD5 result is an hexa text convertible to bytea with
decode, but then I was
Dear Stephen,
Attached please find files and patches associated with moving from the
User/Group system currently in place to Roles, as discussed
previously. The files are:
pg_authid.h
New system table, contains role information
To be placed in src/include/catalog, replacing
.
I have no mean to test that on a win32 machine. Could you do it?
I'm wondering whether the MAKE_DLL fix should also be done under cygwin.
Any opinion?
Thanks in advance,
--
Fabien Coelho - [EMAIL PROTECTED]*** ./src/include/Makefile.orig Wed Nov 3 10:32:29 2004
--- ./src/include/Makefile
,
--
Fabien Coelho - [EMAIL PROTECTED]*** ./src/include/Makefile.orig Wed Nov 3 10:32:29 2004
--- ./src/include/Makefile Sun Nov 7 11:14:52 2004
***
*** 18,24
# Subdirectories containing headers for server-side dev
SUBDIRS = access bootstrap catalog commands executor lib libpq
. (make install INSTALL=install
or similar)
That simple idea alone seems to give a 25% cpu performance gain on my
laptop for a make check...
I'll try to find time to test the multi-arg install for further
improvements anyway.
Thanks!
--
Fabien Coelho - [EMAIL PROTECTED
right now.
Have a nice day,
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 8: explain analyze is your friend
Dear Tom,
What I'd rather see is some effort spent on speeding up our install
script, maybe by allowing it to install multiple files per invocation.
The recent changes to force install-all-headers have caused a
serious degradation of make install performance,
Yes, I agree.
and I think that's where
Dear Bruce,
So, the question remains the same: is there a consensus to drop
install-all-headers/light-install targets for a simple and full install?
This is the 8.0 release --- let's remove those targets. Our logic has
usually been to remove confusing options and document their removal
rather
.
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Dear Magnus,
Oh. Hmm ... wouldn't it be easier and safer to launch psql script
as a subprocess?
I'd say no. Executing processes from the installer environment can be a
headache (we've had enough problems with initdb already..). And you have
to go through all the weirdness with the commandline
to
implement with apache example at hand.
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
packagers to have a clear list
of the use of all headers files, in order that they can figure out where
they belong to.
Opinions?
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose
are the implications. I have to investigate, and I don't have much
time right now...
Have a nice day,
--
Fabien Coelho - [EMAIL PROTECTED]*** ./GNUmakefile.in.orig Tue Aug 10 08:29:01 2004
--- ./GNUmakefile.inFri Sep 3 10:01:40 2004
***
*** 15,23
@echo All of PostgreSQL
, makefiles and libraries useful for server developpement.
I would suggest install-server-dev.
- make the contrib regressions work with pgxs. I'm not sure about what
is needed for that.
I'm available to fix any problem with this patch.
Have a nice day,
--
Fabien Coelho - [EMAIL PROTECTED
remove both light-install and install
-all-headers targets in another submission.
Have a nice day,
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
-install targets for a simple and full install?
If so, I'll make a new submission.
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
Am Dienstag, 17. August 2004 14:26 schrieb Fabien COELHO:
The patch adds missing the libpgport.a file to the installation under
install-all-headers. It is needed by some contribs. I install the
library in pkglibdir, but I was wondering whether it should be libdir?
Yes it should. Please
. it validates.
I'm available to fix any problem with this patch.
Have a nice day,
--
Fabien Coelho - [EMAIL PROTECTED]*** ./contrib/btree_gist/Makefile.orig Fri May 28 15:09:43 2004
--- ./contrib/btree_gist/Makefile Tue Aug 17 11:54:08 2004
***
*** 1,8
- subdir
for him?
Have a nice day,
--
Fabien Coelho - [EMAIL PROTECTED]*** ./doc/src/sgml/ref/pg_restore.sgml.orig Thu Jul 15 10:29:00 2004
--- ./doc/src/sgml/ref/pg_restore.sgml Thu Aug 12 10:29:09 2004
***
*** 130,135
--- 130,147
/varlistentry
varlistentry
is perfectly possible, I'm really willing
to fix them while preserving the ability to compile postgresql contribs
with an already installed postgresql.
Basically it works for me.
Thanks in advance,
--
Fabien Coelho - [EMAIL PROTECTED]*** ./contrib/btree_gist/Makefile.orig Wed Aug 11 13:38:31
we should leave the behavior alone, at least for this release
cycle.
Ok. Thanks for your comments.
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe
, not internal ones.
I really want to be able to install contribs as an afterthought and
without reconfiguring.
anyway, sorry I cannot really help as I m away from home.
Have a nice day,
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 7
be installed in the normal libdir.
Ok.
I'll submit a new patch on tomorrow to hopefully address all these issues.
Thanks a lot for all these comments,
have a nice day,
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 2: you can get off all
Dear patchers,
Please find attached version number 3 for a patch to enable extensions
such as contribs or external add-ons to be installed simply with an
already installed postgresql.
This version addresses Peter's comments about src/makefiles/Makefile.*
that do not need to be installed. It
is a symbolic link, so it may
depends whether the install.sh copies the link as a file or as a link.
Thanks for your comments,
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ
that the
submission could be forgotten, hence the reminder.
I'd expect that patches stuck in pgsql-patches are still supposed to be
in-time for feature freeze.
Gut. Danke schoen.
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 1: subscribe
, so
its status is different from others that are to be included.
Thanks again,
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
Dear Bruce,
On Wed, 9 Jun 2004, Bruce Momjian wrote:
Would you adjust based on Tom's comments and resubmit? Thanks.
Done.
! Date: Wed, 9 Jun 2004 14:31:59 +0200 (CEST)
! From: Fabien COELHO [EMAIL PROTECTED]
! To: PostgreSQL Patches [EMAIL PROTECTED]
! Subject: [PATCHES] fix schema
.
It validated for me with a make check.
Have a nice day,
--
Fabien Coelho - [EMAIL PROTECTED]*** ./doc/src/sgml/rules.sgml.orig Sun Feb 29 17:35:15 2004
--- ./doc/src/sgml/rules.sgml Sun Feb 29 17:38:45 2004
***
*** 873,879
ListItem
Para
Dear hackers,
Please find attached a patch to fix schema ownership on first
connection, so that non system schemas reflect the database owner.
This revised patch includes fixes after Tom comments on names used in the
validation. However, the validation is still there. It is easy to edit it out
Dear Tom,
Thanks for your reply.
Here is a proposed patch against 7.4.1 to check exact match
of foreign key types wrt the referenced keys, and to show
a warning if this is not the case.
I think that this concern may be obsolete in CVS tip,
I just get the current CVS and had a quick
Dear patchers,
Please find attached a patch to fix schema ownership on first connection,
so that non system schemas reflect the database owner.
(1) It adds a new datisinit attribute to pg_database, which tells
whether the database initialization was performed or not.
The documentation is
regressionuser[123], regression[123] as names in
the validation. Writing tests cases is not fun, so I tried to put some fun
by using these characters.
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 2: you can get off all lists
are not
necessary. So maybe some make big_check or the like?
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
Dear patchers,
Subject: [PATCHES] add build utilities in default install
I withdraw this submission, which was not yet considered for inclusion
anyway.
I'll send a more complete patch, which includes this one, but also provide
a working infrastructure for extensions, sometimes later. I've
.
--
Fabien COELHO _ http://www.cri.ensmp.fr/~coelho _ [EMAIL PROTECTED]
CRI-ENSMP, 35, rue Saint-Honoré, 77305 Fontainebleau cedex, France
phone: (+33|0) 1 64 69 {voice: 48 52, fax: 47 09, standard: 47 08}
All opinions expressed here are mine
tests, including the added EVERY aggregate.
It DOES NOT validate for me, as errors and rules are broken in current
head:
undefined symbol: pg_strcasecmp
However the aggregate part works fine.
Have a nice day,
--
Fabien Coelho - [EMAIL PROTECTED]*** ./doc/src/sgml/func.sgml.orig
.
It validates (make check does perform a make install).
I'm obviously ready to update the patch if necessary (missing files,
other default directories...).
Have a nice day,
--
Fabien Coelho - [EMAIL PROTECTED]*** ./GNUmakefile.in.orig Tue Apr 20 09:35:41 2004
--- ./GNUmakefile.inTue May 18 11:52:08
,
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
.
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
(1) boolean-and and boolean-or aggregates named bool_and and bool_or.
they correspond to standard sql every and some/any aggregates.
They do not, sorry. I'll resubmit.
--
Fabien Coelho
---(end of broadcast)---
TIP 7: don't forget
to look for them and being desappointed not to find them (there was a
discussion about these very functions last month on some other pg list).
Although It is very interesting to learn about how to add aggregates in
pg, maybe all users around don't have the time and the motivation for
that.
--
Fabien
version. It validates for me.
Have a nice day,
--
Fabien Coelho - [EMAIL PROTECTED]*** ./doc/src/sgml/func.sgml.orig Mon Apr 26 14:00:58 2004
--- ./doc/src/sgml/func.sgmlSat May 1 15:49:39 2004
***
*** 7544,7549
--- 7544,7617
/row
row
there is no 'light' fix, other than acknowledging the
fact... Not a big issue.
Thanks,
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
'func.sgml' next to has_*_privileges be an appropriate place?
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so
questions I received. (2) is somehow a
small bug fix. (1) adds a minor set of functions to access fields in
'aclitem'.
Thanks in advance,
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 7: don't forget to increase your free space map
that the problem is refuted or
addressed,
That's what I do, but I can only argue, not refute or address
issues. Whether it is refuted or addressed is in the head of the decider.
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 8: explain
in the psql
[...]
Oh, OK, so make it behave like pg_dump's text output piped into psql.
It is really easy to add an option to allow user change the 'ignore'
behavior, and make pg_restore exit loudly if it is desired.
Maybe it should be proposed just for backwards compatibility?
--
Fabien
columns
NO NULL CHECK
QUOTED (meaning 'as quoted')?
From a language design point of view, I think it may be better to stick
to one word versions?
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 5: Have you checked our extensive
it and it is fine with me.
BTW, maybe you could either accept/discuss/reject some other 'small'
patches I submitted earlier, if you have some time. They are not cosmetic
as this one.
Have a nice day,
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast
Dear Peter,
I needed these functions to browse aclitems from user land. I can
load them when necessary, but it seems to me that these accessors for
a backend type belong to the backend, so I submit them.
Can you explain what you want to do from the user level?
Sure.
Before developing
format, and that all syntax re-generation issues should be dealt with by
pg_restore (INSERT vs COPY, quoting, and so on). But the tool was
not resigned this way in the beginning.
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 6: Have
to the backend, so I submit them.
I wasn't sure of what oid should be given...
I attributed new numbers at the end of pg_proc.h.
It validates for me against current cvs head.
Have a nice day,
--
Fabien Coelho - [EMAIL PROTECTED]*** ./src/backend/utils/adt/acl.c.orig Sat Nov 29 20:51:57 2003
have to restore
in an older version. I can guess why it eased the implementation, but it
does not look good.
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send
goes directly
against the advice for writing translatable messages.
Ok.
Also, it might be wise to return a nonzero exit code when any errors are
ignored. I'm not sure about that, but it might be best to err on the
side of caution...
Ok.
I'll resubmit.
--
Fabien Coelho - [EMAIL PROTECTED
do. Hence from this it would be nice if pg_restore could restore
to older versions. Hence my comment it does not look good. It is just
a question of perspective.
Have a nice day,
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 2
,
--
Fabien Coelho - [EMAIL PROTECTED]*** ./src/bin/pg_dump/pg_backup.h.orig Wed Mar 24 17:19:43 2004
--- ./src/bin/pg_dump/pg_backup.h Sat Apr 10 13:04:21 2004
***
*** 57,62
--- 57,67
int remoteVersion;
int
of pg_restore is that it is only expected
to work with its own server. Indeed, it generates some new syntax, such as
$$ quoting, which is not compatible with older servers. This fact does not
seem to appear in the documentation.
Have a nice day,
--
Fabien Coelho - [EMAIL PROTECTED]*** ./src/bin
.
I think it is a small technical issue in the parser internals, and has
nothing to do with great principles and whether this or that is a keyword.
It's about what keywords need to be tokens.
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast
, or it is not there?
Out of the parser, the only information is the offending token (embedded
in the error string) and the character number in the string, that is quite
small a clue to give a hint.
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 3
Dear Tom,
In particular you can't any longer tell the difference between BOOLEAN
and boolean (with quotes), which are not the same thing --- a quoted
string is never a keyword, per spec. [...]
Ok, so you mean that on -boolean- the lexer returns a BOOLEAN_P token, but
with -boolean- it
an historical definition. Also,
I just want to divide the year by 100 or 1000, I can do that quite easily.
Have a nice day,
--
Fabien Coelho - [EMAIL PROTECTED]*** ./doc/src/sgml/func.sgml.orig Wed Mar 31 08:58:31 2004
--- ./doc/src/sgml/func.sgmlSun Apr 4 10:23:00 2004
,
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
would try to enhance emacs sql-mode.
But I don't like much lisp programming.
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 8: explain analyze is your friend
Dear Tom,
No, just redefine yyerror as a macro that passes additional parameters.
Ok! That's just the kind of the hack-hook I was looking for!!
The terminals are not available, they must be kept separatly if you
want them. This can be done in yylex().
We don't need them. Any
.
I'm investigating the internal way. Not really optimistic because
of the details, but I may find workarounds. I'll post later when I'll
have a definite opinion.
--
Fabien COELHO _ http://www.cri.ensmp.fr/~coelho _ [EMAIL PROTECTED]
CRI-ENSMP, 35, rue Saint-Honoré, 77305 Fontainebleau cedex
haven't looked into it closely.
That could be a showstopper if true, but it's all speculation at this
point.
I think the information is there.
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 9: the planner will ignore your desire
Dear Tom,
I quite agree that you shouldn't do a complete implementation when it's
not clear if we'll accept it or not. What I'd like to see is a demo,
basically. How about one example of each of several different kinds
of hints? We need to get a feeling for what can be accomplished and
statement list such as CREATE TABLE/INDEX/SEQUENCE/TRIGGER/VIEW or GRANT
or ; expected
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
that.
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
being displayed, thanks to
all added noH calls I put.
Also, As far as I remember, I put a new option to activate these hints.
Hints are disactivated by default. This is because some people do not
like advices and may want to turn them on or off.
--
Fabien Coelho - [EMAIL PROTECTED
. If you are okay then you apply, and I'll submit some
new patches later on, one command at a time, and when I have time.
Does this sound reasonnable enough?
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 5: Have you checked our
Dear patchers,
Please find my second micro-patch submission for this minor inconsistency.
I put comments about why SIMILAR TO cannot be handled simply in the code
rather that in the test, as it seemed more logical.
Have a nice day,
--
Fabien Coelho - [EMAIL PROTECTED]*** ./src/backend/parser
factorization must be changed. It can also be done.
Yes. I think we must have an all_subselect_ops or similar.
I'll do that and resubmit later.
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands
Fabien COELHO [EMAIL PROTECTED] writes:
Please find attached a patch which allows LIKE/ILIKE/NOT LIKE/NOT ILIKE
as operators for ANY/SOME/ALL constructs.
This seems to allow a whole lot of unintended and probably uncool things
as well. ORDER BY NOT LIKE, for instance.
Yes.
Well
programmers will never have syntax errors with their
SQL stuff.
Thus I really think that the parser should return the processed query,
at least in some cases.
Anyway, have a nice day!
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 1
to
update the position to get back to the initial query, as escapes may have
been processed within the string, so a simple offset would not fix the
bug.
It validates for me.
Have a nice day,
--
Fabien Coelho - [EMAIL PROTECTED]*** ./doc/src/sgml/protocol.sgml.orig Wed Mar 10 15:56:59 2004
arguments after the first.
Anyway, please consider the following patch for inclusion to current
head. It validates for me. I need it to be able to go on.
Have a nice day,
--
Fabien Coelho - [EMAIL PROTECTED]
hints_0.patch.gz
Description: Binary data
---(end
way, but other patches should
be much more narrow after this one, that's the idea...
I don't think it harms the parser code, as it validates for me.
I just hope I did not forget any file.
Thanks in advance,
--
Fabien Coelho - [EMAIL PROTECTED]
hints_0.patch.gz
Description: Binary data
discussions...
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
in a very simple way, but other patches
should be much more narrow after this one, that's the idea...
I don't think it harms the parser code, as it validates for me.
Thanks in advance,
--
Fabien Coelho - [EMAIL PROTECTED]
hints_0.patch.gz
Description: Binary data
---(end
Dear Bruce,
# [PATCHES] notice about costly ri checks (2), Fabien COELHO
This one which appears on the web page can also be removed,
It is also replaced by version 4.
Sorry again for the inconvenience, have a nice day,
--
Fabien Coelho - [EMAIL PROTECTED]
---(end
Dear Bruce,
It is in the queue because I need that narrative for the commit
messase.
Ok, I get the point.
I should have made a fully standalone version with all comments repeated.
Thanks, have a nice day,
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast
seemed to decide that a
WARNING was better, and that attributes and types should be shown, hence
version (4).
So, if you can update, it would be better!
Sorry for the inconvenience, have a nice day,
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast
for me against current cvs head.
I've also added new regression tests in errors.sql.
Although I have taken great and painful care to deal with multi-byte
encodings, I'm not sure how I can validate that, as I don't have some
japanese terminal to play with.
Have a nice day,
--
Fabien Coelho
number that I found useful.
The new version validates for me against current cvs head.
Same comment as with version one, I don't know how to test the multi-byte
part.
Have a nice day,
--
Fabien Coelho - [EMAIL PROTECTED]*** ./src/bin/psql/common.c.origThu Mar 11 15:42:17 2004
--- ./src
appended to foreign_key.sql
It validates for me against current head.
Have a nice day,
--
Fabien Coelho - [EMAIL PROTECTED]
costly_ri_notice.patch.gz
Description: Binary data
---(end of broadcast)---
TIP 9: the planner will ignore your desire
As a side question, if there are multiple cross-type conversions in one
constraint on different column pairs, what do we think the message should
be? One message with multiple column mentions in detail or multiple
notices? (I haven't looked at the patch to see if one or the other is
I thought the syntax came from Berkeley. We can add ALSO if folks like
it. I can't think of cases where we have keywords for both on and off
behavior, and allow a default if the keyword is missing.
ALTER TABLE ... DROP CONSTRAINT ... [ RESTRICT | CASCADE ]
CREATE TABLE ... [ WITH OIDS |
| WITHOUT OIDS ] ... ;
CREATE USER ... [ CREATEDB | NOCREATEDB ] ... ;
IMHO, from the language design point of view, it seems better if all
options have a name.
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 5: Have you checked
Shoot me the patch again and I will put in the the queue. Thanks.
Please find attached (again) the patch I sent. It is against 7.4.1.
If necessary, I can redo the job against current head.
Have a nice day,
--
Fabien Coelho - [EMAIL PROTECTED]*** ./doc/src/sgml/rules.sgml.orig Sun Feb
with the difforig script against the current cvs
head.
Thanks in advance for considering it, and for any comment or cheering,
--
Fabien Coelho - [EMAIL PROTECTED]*** ./src/backend/commands/tablecmds.c.orig Wed Mar 3 09:18:19 2004
--- ./src/backend/commands/tablecmds.c Wed Mar 3 09:30:57 2004
is being processed, as there is not real context information
and tell 'while processing this constraint'... However this
situation seems to be the normal case with any postgresql
messages, as far as I can tell from my use.
Have a nice day,
--
Fabien Coelho - [EMAIL PROTECTED]
fk_type_check.diff.gz
I can think of several cases where it might be reasonable for the types
to be different.
Sure. It's all about a warning, not about an error.
--
Fabien Coelho - [EMAIL PROTECTED]
---(end of broadcast)---
TIP 7: don't forget to increase your
96 matches
Mail list logo
