ut this seems like a good
opportunity to,
like Perl 6, keep the good stuff and replace the cruft.
That's a tall order, of course, which makes me wish we had started this thread
about 10 years ago. You know, that time when Perl 6 was just about to be
released. :)
- --
Greg Sabino Mullane g.
');
$oldexpand or $dbh-STORE('pg_expand_array', 1);
my $info = $sth-fetchall_arrayref({});
$oldexpand or $dbh-STORE('pg_expand_array', 0);
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 20132213
http://biglumber.com/x/web?pk
somewhere? I thought the link above
would be a good place, but it doesn't mention it. I ask as I'd like
to add a link about the deprecation inside the existing DBD::Pg bundle.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8
derive the first from the second?
- --
Greg Sabino Mullane g...@turnstep.com
PGP Key: 0x14964AC8 201311091154
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iEYEAREDAAYFAlJ+aSIACgkQvJuQZxSWSsgavACfXMw2kJgrSPhWAGLFWT8sTNU4
lNkAmwWXagapl4yDFmBHz40n
is a struct that is initialized in perpare). Any ideas
on how to do this? In Perl, it's as easy as:
if ('sponge' eq $sth-{Database}{Driver}{Name})
but getting that information inside of dbdimp.c is the bit
I cannot figure out.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation
in your docs so you can simply point them there.
(MySQL 4.x? I know places still running 3.x!)
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201309262247
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
if there is a match.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201307012133
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE
-bind_col (1, undef, {TYPE = SQL_INTEGER, DiscardString = 1});
Why doesn't the driver simply do sv_setiv unconditionally if the
column is an integer?
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201306031030
http://biglumber.com/x
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Thanks John. This solves the problem of closing idle ones. How do I
re-establish a connection on subsequent calls to $dbh?
Take a look at:
http://search.cpan.org/~syber/DBIx-RetryOverDisconnects-0.08/
- --
Greg Sabino Mullane g
definitions than others. :)
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201212312210
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE
withdraw my previous statement.
However it is not possible to select from any table.
SELECT 1 FROM DUAL will fail.
Ah, so Oracle still requires an actual table? Thought they might
have joined the rest of us by now in allowing things like
'SELECT 2+2;' :)
- --
Greg Sabino Mullane g...@turnstep.com
'mysql_ping' the same sort of thing as OCIPing except it can
reconnect.
Does it automatically reconnect? That certainly seems like the wrong thing
to do, especially in light of the docs for connect_cached.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
1. Columns described as SQL_INTEGER will be bound as SQL_C_LONG and
hence retrieved as a C long and the bound scalar will be set using
sv_setiv
..
2. You cannot override the bound column type.
+1, sounds sensible.
- --
Greg Sabino
to be fairly standard.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201205151324
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iEYEAREDAAYFAk+ykUcACgkQvJuQZxSWSshqjACgxhBrO
to connect.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201205071256
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iEYEAREDAAYFAk+n/toACgkQvJuQZxSWSshCgQCguTHlAoqzxca8NfhGTbeqdDWb
and then deprecate it later.
- --
Greg Sabino Mullane g...@turnstep.com
PGP Key: 0x14964AC8 201110130902
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iEYEAREDAAYFAk6W4ZQACgkQvJuQZxSWSsiqUQCgo/icUz0enqn0BWSygNSeNJGW
lDsAoMbjgZrsGJyS7kS60RgNNkpXMIjG
=43Q3
at this. My short term goal is to get this finalized
enough that I can release the next version of DBD::Pg without a 'pg_' prefix
to control the encoding items.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201110061151
http
basically ask the DBD to make any returned
data into that encoding, by hook or by crook.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201110022345
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP
*, just become ordinary DBD
methods that are beyond what is defined by the DBI spec.
Seems a sure recipe for namespace collisions. Also makes it much harder to
spot any DBMS-specific hacks in your Perl code.
- --
Greg Sabino Mullane g...@turnstep.com
PGP Key: 0x14964AC8 201109211632
http
force SQL_ASCII text to have utf8 flipped on. Perhaps we simply never, ever
allow that.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201109211651
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP
, or need the data to come back in the current, undecoded,
un-utf8-flagged way.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201109092305
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE
,
such a statement fails like this on DBD::Pg:
DBD::Pg::db selectall_arrayref failed: no statement executing
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201106091607
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201105161229
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iEYEAREDAAYFAk3RUPsACgkQvJuQZxSWSsjPjwCg/vTUsZxdnHOfXWm73vDZ12l
on disconnected handle);
Which seems like the Right Thing To Do, but I don't know
how standard that is.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201105150850
http://biglumber.com/x/web?pk
.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201103161205
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iEYEAREDAAYFAk2A4C8ACgkQvJuQZxSWSshIhACg2mIiZs8MX1WePcoSMDIXzPzm
a mistake (and almost
definitely a mistake if your code could use multiple DBDs).
With multiple, yes, but with a single one that does something sane
(in other words, a rollback) I think it's a valid shortcut. But
I would certainly be okay with adding a warning.
- --
Greg Sabino Mullane g
the DBD's are expected to debug/trace.
Sounds good, and I think the ENC, CON, and DBD go a long way
towards that.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201102101713
http://biglumber.com/x/web?pk
there, as well as all the others I
did not quote here.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201102101726
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE
a message showing the connection string right before a new
database connection is attempted, a message when the connection
was successful, and a message right after the database has been
disconnected. Also output if trace level is 5 or greater.
- --
Greg Sabino Mullane g...@turnstep.com
End
and three
dot versions on the same check was treated as a severe
error and caused an automatic FAIL report.
I can't see a case where using both forms would ever be desired.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201007081302
::Pg). Version 1.49 (the last of the two dot
versions for those playing at home) is *severely* deprecated. One of the
reasons DBD::Pg jumped to 2.0.0 was to prevent any version comparison
confusion, as even Perl's wacky versioning tools cannot deny that 2 1. :)
- --
Greg Sabino Mullane g
Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201006091218
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iEYEAREDAAYFAkwPvtgACgkQvJuQZxSWSsgElACg4MVXbCfC02ngwEbBRotoM5DW
and stay awhile. :)
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201004161004
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE
, which is way too busy. Of course, people also get
DBI/DBD help on the friendly database channels such as #mysql and #postgresql.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201004131638
http://biglumber.com/x/web?pk
know how a handful deal with ints internally.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation
PGP Key: 0x14964AC8 200911271301
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE
never get a Perl integer (IV) to match Oracle's integer:
NUMBER(38). But sounds like y'all have found a good enough solution.
- --
Greg Sabino Mullane g...@turnstep.com
PGP Key: 0x14964AC8 200910281253
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE
pegs into
round holes to make JSON::XS happy: maybe it's better to look for a solution
on that end at this point?
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation
PGP Key: 0x14964AC8 200910261039
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP
::XS as well. For the relevant code, see:
http://svn.perl.org/modules/DBD-Pg/trunk/dbdimp.c
and grep for cast
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation
PGP Key: 0x14964AC8 200910231020
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP
/vendor_perl
/usr/lib/perl5/5.10.0/i386-linux-thread-multi
/usr/lib/perl5/5.10.0
/usr/lib/perl5/site_perl
.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation
PGP Key: 0x14964AC8 200909150949
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN
?) database systems).
- --
Greg Sabino Mullane g...@endpoint.com g...@turnstep.com
End Point Corporation
PGP Key: 0x14964AC8 200607261743
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iEYEAREDAAYFAkodV9kACgkQvJuQZxSWSsgAgACg08w+JwQ5CDn
learn from your experiences,
and we can contribute back in turn. If it gets high traffic and extraordinarily
sqlite-specific, then, yes, use another list, but I'd lean towards keeping it
here if possible.
Thanks for all your work in driving this forward.
- --
Greg Sabino Mullane g...@turnstep.com
End
the parameters. But then again, I rarely
use bind_param, and prefer to explicitly pass items to execute(), even
if I have to occasionally bind_param to get the type correct.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
End Point Corporation
PGP Key: 0x14964AC8 200812091403
http://biglumber.com/x/web?pk
= { pg_type = 1024 } }
and
{ ':foo' = { pg_type = 23 }, ':foo2' = { pg_type = 1024 } }
The just-released 2.11.0 version of DBD::Pg has this behavior.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200810130752
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
' with the value passed to bind_param.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200810140024
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iEYEAREDAAYFAkj0Hx0ACgkQvJuQZxSWSshLwgCg3IyJ194QMYpIg6lQTtqZsuMj
is already covered, DBD::Pg does not bother
to output, in the expectation that level 3 is level 3. That assumption would
need to change across all drivers.
Okay, enough rambling and speculation for now... :)
- --
Greg Sabino Mullane [EMAIL PROTECTED]
End Point Corporation
PGP Key: 0x14964AC8
.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200808211532
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iEYEAREDAAYFAkitwt4ACgkQvJuQZxSWSsgxWQCfS2TpUj3w0oivBd3dcSqDrkvw
m1cAoKGfB+vS4jDFOFHhjcCWrHbbuPaY
=dQwg
-END PGP SIGNATURE-
wants to write 0x0200 instead of 'pgstart'. :)
- --
Greg Sabino Mullane [EMAIL PROTECTED]
End Point Corporation
PGP Key: 0x14964AC8 200808211638
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iEYEAREDAAYFAkit0jAACgkQvJuQZxSWSsiMQACdFjArMN
).
Sure, but why is NAME_lc cached and NAME not? And why the differing behavior
depending on the DBD? I admit this is fairly corner case but it smells
like there is some subtle bug here.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
End Point Corporation
PGP Key: 0x14964AC8 200808181740
http
/t/02attribs.t
- --
Greg Sabino Mullane [EMAIL PROTECTED]
End Point Corporation
PGP Key: 0x14964AC8 200808071224
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iEYEAREDAAYFAkibIqkACgkQvJuQZxSWSsgNsACg3VoEuo0AffJo8hHOC5xizqA1
H10AoIAi7UzE++v+7
Looks like a minor cut-n-paste error. Patch inlined:
Index: lib/DBI/Const/GetInfo/ODBC.pm
===
--- lib/DBI/Const/GetInfo/ODBC.pm (revision 11363)
+++ lib/DBI/Const/GetInfo/ODBC.pm (working copy)
@@ -543,9 +543,6 @@
Sabino Mullane [EMAIL PROTECTED]
End Point Corporation
PGP Key: 0x14964AC8 200805141108
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iEYEAREDAAYFAkgrAk4ACgkQvJuQZxSWSsgK7QCfaJQV1+Sue1dxJXrY8g2UuWKl
p/cAoOs3Zm5/ZRHVsKTxaWderwHbulZj
=j+jV
fetchall_arrayref hash\n;
ok($csr_b-execute());
$r = $csr_b-fetchall_arrayref({});
- --
Greg Sabino Mullane [EMAIL PROTECTED]
End Point Corporation
PGP Key: 0x14964AC8 200803231157
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE
non-connecting but passed test:
http://www.nntp.perl.org/group/perl.cpan.testers/2008/01/msg967763.html
- --
Greg Sabino Mullane [EMAIL PROTECTED]
End Point Corporation
PGP Key: 0x14964AC8 200801180014
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE
ended up using a
require/eval block and doing the exit 0 you mentioned elsewhere if it fails.
Thanks for your work on this, I've implemented the rest of your suggestions
for DBD::Pg and hope to see less false test failures in the next release! :)
- --
Greg Sabino Mullane [EMAIL PROTECTED]
End Point
of MakeMaker are you using?
6.36
- --
Greg Sabino Mullane [EMAIL PROTECTED]
End Point Corporation
PGP Key: 0x14964AC8 200712061011
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iD8DBQFHWBGnvJuQZxSWSsgRAzWtAKCn37T6YLQCVNWAN8SK9jBtTRJBmgCfSdw7
Qiw7WSXO
+217,7 @@
/* Replace: 0 */
#endif
+#ifndef PERL_UNUSED_DECL
#ifdef HASATTRIBUTE
# if defined(__GNUC__) defined(__cplusplus)
#define PERL_UNUSED_DECL
@@ -226,6 +227,7 @@
#else
# define PERL_UNUSED_DECL
#endif
+#endif
#ifndef dNOOP
# define NOOP (void)0
--
Greg Sabino Mullane
-execute($foo, $bar, undef, $DBI::DEFAULT_VARIABLE);
would send this to the backend:
INSERT INTO mytables(a,b,c,d) VALUES ('yin','yang',NULL,DEFAULT);
And likewise for bind_param, etc.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200602111455
http://biglumber.com/x/web?pk
, even if it is possible (which seems unlikely), DBI is not the
place for it.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200507141317
https://www.biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE
is found.
Any rollback or commit will clear the array, and the dbh destructor calls
av_undef.
The DBD::Pg implementation uses savepoint, rollback_to, and release for
those trying to find them in the source.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200507131007
http
ce7bf07a17b5ad51a72f31160627f277 DBD-Pg-1.41_1.tar.gz
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200505090625
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iD8DBQFCfzr2vJuQZxSWSsgRAveYAKDllt2TWyvcbWyNmtkDC8/foH+8uACg5Xpr
P/R2Dx1SXUr+ARuBAHvNydI=
=yBTW
, but maybe this will help someone else
in my situation.
Thank you, patch applied.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200504151919
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE
for transaction handling\n;
}
The actual code is in C and a lot uglier than that, but that's the gist
of it. Makes it very hard for the users to get around using the DBI
methods for transaction control. We'd do the same for SAVEPOINT of course.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key
the added perk of
being able to push the list of savepoints into the database handle. It
also may have implications for the disconnect() method.
It's late. I will try and write up an API and a dbi-users proposal soon.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200503092341
http
, but wanted to see if
there was any input or objections before I did.
Thanks,
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200503060449
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iD8DBQFCKtJXvJuQZxSWSsgRAu0YAKDF
://gborg.postgresql.org/mailman/listinfo/dbdpg-general
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200502242303
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iD8DBQFCHqOCvJuQZxSWSsgRAglSAKC4UsZdRbt1iFWyc6DNKw+U14f6BQCfRf4Q
);
Thanks, good ideas and applied.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200501011042
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iD8DBQFB1sTTvJuQZxSWSsgRAgfJAJ9dJ9iuHRz6ppVxmme1g8gm3ZLofgCg9ASE
it into a normal INSERT.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200407062117
-BEGIN PGP SIGNATURE-
iD8DBQFA61B1vJuQZxSWSsgRAkPWAJ9tZPuCT6KPq1aVDrEv41JqfgrEzgCgp+R9
eCxGCJAJyles/9kJfz2YRJE=
=X06+
-END PGP SIGNATURE-
.
Has anyone else run into this? Does the above sound like a good
solution? (The 'local' prepare for DBD::Pg just means that we
build the complete SQL statement ourselves and send that off
to the server).
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200402221153
-BEGIN PGP
68 matches
Mail list logo
