the cursor/non-
cursor cases.
My vote would be for a documentation change which mentioned how to use
cursors explicitly to avoid excessive memory usage.
--
Peter Haworth [EMAIL PROTECTED]
Q: Why do ducks have flat feet? A: To stamp out forest fires.
Q: Why do elephants h
On Sat, 11 Dec 2004 10:44:59 -0600, Wes wrote:
> On 12/9/04 9:23 AM, "Peter Haworth" <[EMAIL PROTECTED]> wrote:
>
> > It runs RHEL ES v3, kernel 2.4.21-20.ELsmp
> > It's generally a very stable box which runs a number of postgresql
> > instances. But
locate to
these with the move to v7.4?
Are there other settings we should be altering?
All this is assuming that it's a postgres problem, rather than something
else. Another leading candidate is this, which we are looking into:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=132155
It wo
ature we really need immediately.
--
Peter Haworth [EMAIL PROTECTED]
"There are two ways of constructing a software design. One way is to make
it so simple that there are obviously no deficiencies and the other is to
make it so complicated that there are no obvious de
Tom Lane writes:
> It would make sense to offer a "strict" mode in which the date order
> has to be what DateStyle suggests.
Something like this?
set datestyle='iso,strict';
I could live with that.
--
Peter Haworth [EMAIL PROTECTED]
AD&D Les
; and 'f'. This
means that if you know you're always going to use Postgres (and that DBD::Pg
isn't going to change), you can simply say:
if($cust_data->{hold})
However, if you want cross-database portability (and protection from
DBD::Pg's behaviour changing), you
,?,?,?,?)
),{},@env_array{qw(User UserEmail ServiceLevel AccountManager Company)});
2.
my($uname,$email,$level,$mgr,$company)=map $dbh->quote($_),
@env_array{qw(User UserEmail ServiceLevel AccountManager Company)};
$dbh->do(qq(
insert into env_info
(username,useremail,ser
On Wed, 30 May 2001 12:54:17 -0400, [EMAIL PROTECTED] wrote:
> On Wed, May 30, 2001 at 04:02:51PM +0100, Peter Haworth wrote:
> > On Wed, 30 May 2001 08:07:11 -0400, [EMAIL PROTECTED] wrote:
> > The new behaviour is mre correct.
> >
>
> Why? The old behavior is bette
statement.
That's because previous versions of DBD::Pg had a bug which didn't remove the Active
attribute from statement handles which all rows had been fetched from.
The new behaviour is mre correct.
--
Peter Haworth [EMAIL PROTECTED]
"I'm just a mere programmer&qu
for multi-line messages */
+for(end = error_msg + len; end > error_msg && end[-1] == '\n'; --end);
+
src = error_msg;
dst = err;
/* copy error message without trailing newlines */
-while (*dst != '\0' && *dst != '\n') {
+w
On Wed, 15 Nov 2000 11:19:40 -0500, Tom Lane said:
> Peter Haworth <[EMAIL PROTECTED]> writes:
> > I'm having trouble getting Postgres 6.5.3 to do what I want. The
> > problem seems to be fixed in version 7, but I could really do with a
> > workaround for 6.5.
terminated abnormally
before or while processing the request.
We have lost the connection to the backend, so further processing is
impossible. Terminating.
That's obviously too sneaky.
--
Peter Haworth [EMAIL PROTECTED]
Anything that can go wrong, will go wr
nstead:
while($row=$sth->fetchrow_hashref){
push @taghash,{%$row};
}
Or, better yet:
$taghash=$sth->fetchall_arrayref({});
to get everything all in one go.
--
Peter Haworth [EMAIL PROTECTED]
"Master, does Emacs have the Buddha nature?" the novice asked.
T
jnl_refs_is_2)", but I can't see anything like
that in the documentation.
--
Peter Haworth [EMAIL PROTECTED]
"You're not going to watch the eclipse in yesterday's underpants?"
,
internallength=9, externallength=9,
element='char'
)
then insert a row to pg_opclass, after attempting to use the new type to find
its ID.
Surely there's an easier way?
--
Peter Haworth [EMAIL PROTECTED]
"Never tell people how to do things.
Tell them WHAT
15 matches
Mail list logo
