On 21/09/11 21:52, Greg Sabino Mullane wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
...
And maybe that's the default. But I should be able to tell it to be pedantic
when the
data is known to be bad (see, for example data from an SQL_ASCII-encoded
PostgreSQL database).
...
David, I forgot to answer your post first and ended up putting most of my
comments in a reply to Greg's posting - sorry, it was a long night last night.
Some further comments below:
On 21/09/11 19:44, David E. Wheeler wrote:
On Sep 10, 2011, at 3:08 AM, Martin J. Evans wrote:
I'm not sure
Okay, this is a big blue sky idea, but like all things open-source, it comes
out of a need. I'm trying to merge together Excel (or CSV), Oracle, Fusion
Tables, JSON, and SNMP for various data points and outputs. DBIC seems to
work great for a large database with a bunch of tables, but what about
On Sep 21, 2011, at 7:53 PM, Brendan Byrd wrote:
Okay, this is a big blue sky idea, but like all things open-source, it comes
out of a need. I'm trying to merge together Excel (or CSV), Oracle, Fusion
Tables, JSON, and SNMP for various data points and outputs. DBIC seems to
work great for a
On 22/09/2011 17:36, David E. Wheeler wrote:
On Sep 22, 2011, at 2:26 AM, Martin J. Evans wrote:
There is more than one way to encode unicode - not everyone uses UTF-8;
although some encodings don't support all of unicode.
Yeah, maybe should be utf8_flag instead.
see below.
unicode is not
On Sep 22, 2011, at 11:14 AM, Martin J. Evans wrote:
Right. There needs to be a way to tell the DBI what encoding the server
sends and expects to be sent. If it's not UTF-8, then the utf8_flag option
is kind of useless.
I think this was my point above, i.e., why utf8? databases accept and
On Sep 22, 2011, at 11:57 AM, Martin J. Evans wrote:
ok except what the oracle client libraries accept does not match with Encode
accepted strings so someone would have to come up with some sort of mapping
between the two.
Yes. That's one of the consequences of providing a single interface
Brendan,
Taking into account David's response ...
I have several answers for you:
1. The functionality you are talking about is often referred to as a federated
database, where you have one database engine that the client talks to which
turns around and farms some of the work off to various