tline),
you'll want to follow this outline to disable DBI's
default fascist error response:
$stmt = $dbh->prepare("INSERT ...");
$stmt->{'PrintError'}=0;
$stmt=>{'RaiseError'}=0;
if($stmt->execute(...)) { # insert failed, probably duplicate
# Try Select or update
} else {
...
}
- Tim Kientzle
ntly working on a web publishing system that stores
all content as BLOBs in a back-end MySQL database; performance
is very good so far.
I'll be giving a talk about this at BSDCon in Monterey next month
with more details...
- Tim Kientzle
ff the cache.
Start by carefully checking all of the cables. Then
try swapping out hardware until you can find the problem.
Memory, hard disk controller, hard disk, network card, CPU cache,
are all potential culprits.
- Tim Kientzle
>One of our competitors sunk well over a million bucks into Sun/Oracle
> hardware, and thought they'd be "cutting-edge" by doing all of their
> back-end programming in Java. The end result is that our $20,000 cluster
> using Linux, Postgres, and Perl out-performs their setup by a very
> signi
The mailing address in my address book (which is what I generally use):
[EMAIL PROTECTED]
The daily digests I get have the following email address at the top:
[EMAIL PROTECTED]
Both seem to work for me.
- Tim
Richard Brown wrote:
>
>
ary data
(apparently PG's parser chokes on null characters?).
I've heard about TOAST, but have no idea what it really
is, how to use it, or how well it performs. I'm leery
of database-specific APIs.
- Tim Kientzle
ons, I've been just storing full data results in
memory. You've talked about using a bean to keep a DB cursor
around; why not just store the results? This looks a lot like
a simple SortedMap from textattrib2 to textattrib1/count pairs.
That's easy to store in memory. And it's
> Of course, people really shouldn't be inserting
> objects which already exist, ...
On the contrary, the best way to test if
something already exists is to just try the
INSERT and let the database tell you if
it's already there. Both faster and more
reliable than doing SELECT then INSERT.
> Search were almost the same ... sorting and
> reading sorted entries from dba was the same.
> But insert/modify/delete [ were up to 15 times
> slower in PostgreSQL than MySQL ].
One of MySQL's big speed problems involves
multi-user situations where some users are writing
while others are readin
> ... if a query fails inside a transactions block,
> PostgreSQL "RollBack"s the whole transaction ...
In my experience, it's unusual for SELECT statements
(queries) to cause errors. If they do, the statements
themselves are likely broken. (A SELECT that returns
zero rows is not an error.) Lik
10 matches
Mail list logo
