Just to get more information, I presume you are talking about the
ActiveState perl and DBD::Oracle installed via ppm from their site? I'm
also presuming you installed the Oracle Instant client along with (which
they do now, but you can skip it, if you have the full client).
Please confirm, so we
Tyler MacDonald wrote:
Tim Bunce [EMAIL PROTECTED] wrote:
PostgreSQL is non-standard (and inconvenient) in this respect.
I chatted with Mischa (my work's resident DB guru) about this, and
according to him, the error behaviour when you attempt to SELECT from a
table that does not exist
This is a pretty difficult to answer question. How heavy do we expect the
usage to be? What kind of system will it be running on?
In general, I've found that MySQL has the best GUI applications. The MySQL
Query Browser makes writing scripts and executing arbitrary SQL statements
on the
On 2005-11-29 18:13:04 -0800, Darren Duncan wrote:
At 5:02 PM -0800 11/29/05, John Armstrong wrote:
Hi - I'm soon to be doing a Perl app on the Internet, that'll need
database.
If you want something that's trivially easy to use, try SQLite.
[...]
Its also faster than anything else for some
On Tue, Nov 29, 2005 at 04:05:26PM -0800, Tyler MacDonald wrote:
Tim Bunce [EMAIL PROTECTED] wrote:
PostgreSQL is non-standard (and inconvenient) in this respect.
I chatted with Mischa (my work's resident DB guru) about this, and
according to him, the error behaviour when you attempt
I'd just like to ask anyone thinking of replying to this thread to *please*
only do so if you can add something useful that's not already been said,
and do so politely, with consideration for the validity of other peoples views.
Tim.
On Tue, Nov 29, 2005 at 05:02:23PM -0800, John Armstrong
Sorry, I know this is off (DBI) topic, but it does relate to Perl and a
database.
I'm about to start developing an app with Perl DBI with the thought that
eventually I'd like to put the app on the web - for which I plan to get a
website hosting company, like Yahoo or whatever. So I'm trying
Sorry, I know this is off (DBI) topic, but it does relate to Perl and a
database.
I'm about to start developing an app with Perl DBI with the thought that
eventually I'd like to put the app on the web - for which I plan to get a
website hosting company, like Yahoo or whatever. So I'm
Tim Bunce wrote:
[...]
Why not help save the world and help me add current_schema() to the DBI
and send implementations to the authors of drivers you're using?
I'd like to remark that SQL/CLI has a more general function
GetSessionInfo( ConnectionHandle, InfoType, ... )
general value
Hi,
I am new to DBI, and that may explain my question.
Using DBI::Proxy, I am trying to connect remotely to an Oracle
database whose datasource looks like this:
'jdbc:oracle:thin:@127.0.0.1:1521:abc'
I tried passing a string to the call DBI-connect($ds, ..):
Thanks much for your cautions, Tim, but no harm done at all. Looks like
most people endorsed MySql. SQL Lite is totaling a little weak, and
Postgres is as good as MySql, just has more of an emphasis on db internals
rather than (MySql's) GUI. MySql's freeness might be getting shakey,
except when
Wow, that's a tough one. It really depends on what you want/need from
your database. What's your recoverability liability? How scalable do
you need your app? Platform/OS requirements?
Being from primarily an Oracle background (as far as DBs go), I'd say
overall Oracle. Free? Yes! There's
You'd be remiss not to look at Firebird.
Mysql5, Firebird 1.5+ and Postgres are what you should be
comparing and testing in my opinion.
On Wed, Nov 30, 2005 at 05:50:07PM +0200, Claude wrote:
Hi,
I am new to DBI, and that may explain my question.
Using DBI::Proxy, I am trying to connect remotely to an Oracle
database whose datasource looks like this:
'jdbc:oracle:thin:@127.0.0.1:1521:abc'
I tried passing a
On Wed, Nov 30, 2005 at 04:25:41PM +0100, Steffen Goeldner wrote:
Tim Bunce wrote:
[...]
Why not help save the world and help me add current_schema() to the DBI
and send implementations to the authors of drivers you're using?
I'd like to remark that SQL/CLI has a more general
Tim Bunce [EMAIL PROTECTED] wrote:
sub execute {
my $self = shift;
my $rv = eval { DBI::st::execute($self, @_); };
I'd probably say:
my $rv = eval { $self-SUPER::execute(@_) };
Yeah, maybe... I adopted that idiom because this doesn't work:
--snip--
sub
On Tue, 2005-11-29 at 11:55 -0600, Scott T. Hildreth wrote:
Whoops, trace file was to big... attached is the first 200 lines.
On Tue, 2005-11-29 at 11:39 -0600, Scott T. Hildreth wrote:
Perl: 5.008003(i686-linux)
OS : linux (2.4.24-abi)
DBI
Andrew Sullivan [EMAIL PROTECTED] wrote:
The inconvenience I'll grant, but the non-standard claim I think
needs some justification. When the database encounters an error in a
transaction, it is supposed to report an error. An error in a
transaction causes the whole transaction to fail:
Can you tell us which version of perl you are running and wether it is 10.2
personal, enterprise or standard or is it just the client?
Marty Martindale [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
There is a problem in Oracle 10.2 that surfaces after you install the
latest
Perl,
On Wed, 30 Nov 2005 09:38:37 -0500, Randall Perry wrote:
Hi Randall
http://quadrahosting.com/hosting/unix.html
--
Cheers
Ron Savage, [EMAIL PROTECTED] on 1/12/2005
http://savage.net.au/index.html
Let the record show: Microsoft is not an Australian company
On Tue, Nov 29, 2005 at 07:44:05PM +, Tim Bunce wrote:
On Tue, Nov 29, 2005 at 10:50:01AM -0800, Tyler MacDonald wrote:
PostgreSQL, doing a SELECT on a table that doesn't exist poisons the rest of
the transaction, whereas under MySQL and SQLite2 the transaction is allowed
to continue.
On Wed, Nov 30, 2005 at 04:19:18PM -0500, Andrew Sullivan wrote:
But it's worth knowing that in Pg 8.1 and later, you can wrap such
things in a subtransaction and get out of it that way.
Shouldn't that be 8.0 and later? That's when savepoints were
introduced. Or are you referring to something
On 11/30/05, Tyler MacDonald [EMAIL PROTECTED] wrote:
Andrew Sullivan [EMAIL PROTECTED] wrote:
The inconvenience I'll grant, but the non-standard claim I think
needs some justification. When the database encounters an error in a
transaction, it is supposed to report an error. An error in
Jaime Casanova [EMAIL PROTECTED] wrote:
Either way the end result is that some database drivers poison a
transaction if there's any error, others are selective about which errors
are fatal and which are not, and still others just don't care at all.
that is a mis-conception... a
On Wed, Nov 30, 2005 at 04:19:18PM -0500, Andrew Sullivan wrote:
On Tue, Nov 29, 2005 at 07:44:05PM +, Tim Bunce wrote:
On Tue, Nov 29, 2005 at 10:50:01AM -0800, Tyler MacDonald wrote:
PostgreSQL, doing a SELECT on a table that doesn't exist poisons the rest
of
the transaction,
On Wed, Nov 30, 2005 at 10:35:17AM -0800, Tyler MacDonald wrote:
This is something I've been meaning to address for a while. I was
thinking of something like:
$schema_name = $dbh-current_schema
I really like this. I read your exchange with Steffen Goeldner and
that
Tim Bunce wrote:
No doubt someone will quote the relevant parts. (And no doubt the
relevant parts will say it depends :)
I believe, the no doubt part is showing your age, aka experience. :-)
27 matches
Mail list logo
