It is with great pleasure that the Bricolage development team
announces
the release of Bricolage 1.10. The culmination of over 19 months of
development, version 1.10 represents a significant advance for the
celebrated open-source content management and publishing system.
Here
On May 2, 2005, at 11:51 , Vlad wrote:
in our web application similar SQL queries (like load an object)
executed over and over again with high frequency. So it's very
desirable to use prepare_cached. I think we are going to adjust our
ORM (object relation mapper) to always use full path to referenc
On May 2, 2005, at 09:34 , Tom Lane wrote:
I think you could demonstrate that if the spec is "make it look
like the
original query was retyped as source each time", then *every* DDL
change
in the database potentially requires invalidating every cached plan.
I don't find that a desirable spec.
I
On May 1, 2005, at 23:16 , Steve Atkins wrote:
Isn't this behaving as documented? prepare_cached() is supposed to
return the original statement handle when you pass it the same string
a second time.
Yes.
The docs for prepare_cached() are littered with "Don't do this unless
you understand the implic
On May 1, 2005, at 21:30 , Neil Conway wrote:
An alternative would be to flush dependent plans when the schema
search path is changed. In effect this would mean flushing *all*
prepared plans whenever the search path changes: we could perhaps
keep plans that only contain explicit namespace ref
On May 2, 2005, at 06:40 , Andrew Dunstan wrote:
I am not sure this is reasonably fixable. Invalidating the cache is
not a pleasant solution - the query might not be affected by the
change in search path at all. I'd be inclined to say that this is
just a limitation of prepare_cached() which s
On May 2, 2005, at 06:36 , Vlad wrote:
as I understood Tom's message, he's not advising dbd::pg driver to
rely on the fact that earlier prepared query is still valid.
That's not going to change. It's your responsibility, as the
programmer, to know when you need to expire the cache:
$dbh->do("SET
On May 2, 2005, at 06:14 , Neil Conway wrote:
I'm not sure I quite follow you -- in some future version of the
backend in which prepared queries are invalidated, this would be
invisible to the client. The client wouldn't need to explicitly
check for the "liveness" of the prepared query, they
On May 1, 2005, at 22:44 , Tom Lane wrote:
I am not claiming that the backend handles all these cases nicely
today: it certainly doesn't. But we understand in principle how
to fix these problems by invalidating plans inside the backend.
I don't see how the DBD::Pg driver can hope to deal with any
On Apr 22, 2005, at 2:09 AM, Sebastian Böck wrote:
Multiple rules on the same table and same event type are
applied in alphabetical name order.
Ah, I'd missed that. Curious that it worked for me, then, since my
rules were named insert_one, promote_one, and nothing_one, as
nothing_one comes after
Hi All,
I recently had a need to have conditional update rules on a view. This
didn't work too well:
CREATE RULE insert_one AS
ON INSERT TO one WHERE NEW.id IS NULL
DO INSTEAD (
INSERT INTO _simple (id, guid, state, name, description)
VALUES (NEXTVAL('seq_kinetic'), NEW.guid, NEW.state, NEW.n
On Apr 21, 2005, at 11:16 PM, Tom Lane wrote:
The only real solution I know of is to sleep for a little before
trying to issue the DROP DATABASE. Certainly, adding more database
traffic as you suggest isn't going to improve matters.
I think just sleeping is all I'm doing. The extra database traffi
Hi All,
I have some tests that create a database, run a bunch of tests against
it, and then drop it. But I was running into an issue where I'd get
this error even after I disconnected from the test database:
ERROR: source database "foo" is being accessed by other users
And no, no other users
The Bricolage development team is pleased to announce the release of
Bricolage 1.8.5. This maintenance release addresses a number of
issues in
Bricolage 1.8.3 and adds a number of improvements (there was no
announcement for the short-lived 1.8.4 release). The SOAP server in
par
The Bricolage development team is pleased to announce the release of
Bricolage 1.8.3. This maintenance release addresses quite a large
number of issues in Bricolage 1.8.2. The most important changes
were to
enhance Unicode support in Bricolage. Bricolage now internally
handles
The Bricolage development team is pleased to announce the release of
Bricolage 1.8.2. This maintenance release addresses quite a large
number of issues in Bricolage 1.8.1. The most important changes
were to
enhance Unicode support in Bricolage. Bricolage now internally
handles
On Aug 24, 2004, at 12:20 PM, Peter Eisentraut wrote:
broken, and that they're useless for multilingual use.
I don't agree with that, but perhaps we differ in our interpretation of
"multilingual use". If you have special requirements, you can always
turn the locales off.
Well, we're getting beyond
On Aug 23, 2004, at 10:25 PM, Joel wrote:
If the locale machinery iw functioning correctly (and if I understand
correctly), there ought to be a setting that would allow those to
collate to the same point.
Bleh. There must be some distinction between them. It sounds like
querying for synonyms.
I'm
On Aug 23, 2004, at 6:49 PM, Tim Allen wrote:
One possible clue: your original post in this thread was using
encoding euc-kr, not unicode (utf-8). If your mailer was set to use
that encoding, perhaps your other client software is/was also?
Bah! Stupid Mail.app was trying to be too smart!
Thanks,
On Aug 23, 2004, at 5:22 PM, Tatsuo Ishii wrote:
Locales for multibyte encodings are often broken on many platforms. I
see identical things with Japanese on Red Hat. This is one of the
reason why I tell Japanese PostgreSQL users not to enable locale while
initdb...
Yep, and exporting my data, delet
On Aug 23, 2004, at 5:07 PM, Ian Barwick wrote:
Does this go away if you change your locale to C?
Yes.
Hallelujah! I'm running initdb again now.
Cheers,
David
smime.p7s
Description: S/MIME cryptographic signature
On Aug 23, 2004, at 4:49 PM, David Wheeler wrote:
Hmm. I tried putting your string into a UNICODE database and I got
ERROR: invalid byte sequence for encoding "UNICODE": 0xc7
Really? Curious.
Oh, are you sure that you got my UTF-8 data? Because it came back in
your reply all mangle
On Aug 23, 2004, at 4:34 PM, Ian Barwick wrote:
wild speculation in need of a Korean speaker, but:
[EMAIL PROTECTED]:~/tmp> cat j.txt
テスト
환경설
전검색
웹문서
국방비
북한의
てすと
[EMAIL PROTECTED]:~/tmp> uniq j.txt
テスト
환경설
てすと
All but the first and last lines are random Korean (Hangul)
characters. Evidently our re
On Aug 23, 2004, at 4:35 PM, Tom Lane wrote:
Hmm. I tried putting your string into a UNICODE database and I got
ERROR: invalid byte sequence for encoding "UNICODE": 0xc7
Really? Curious.
So there's something funny happening here. What is your
client_encoding
setting?
It's not set. I've had it c
On Aug 23, 2004, at 4:08 PM, Tom Lane wrote:
[ looks back at discussion... ] Actually I misremembered --- the
discussion was about how we would *reject* legal UTF-8 codes that are
more than 2 bytes long. So the code is broken, but not in the
direction
that would cause your problem. Time for ano
On Aug 23, 2004, at 3:59 PM, Tom Lane wrote:
But is it possible to store non-UTF-8 data in a UNICODE database?
In theory not ... but I think there was a discussion earlier that
concluded that our check for encoding validity is not airtight ...
Well, it it was mostly right, I wouldn't expect it to b
On Aug 23, 2004, at 3:46 PM, Markus Bertheau wrote:
The collation rules of your (and my) locale say that these strings are
the same:
[EMAIL PROTECTED] markus]$ cat > t
국방비
북한의
[EMAIL PROTECTED] markus]$ uniq t
국방비
[EMAIL PROTECTED] markus]$
Interesting.
Make sure that you have initdb'd the database
eWeek has reviewed Bricolage, the Perl-powered, PostgreSQL-backed
open-source content management system. The article was published
yesterday. An excerpt:
Bricolage is quite possibly the most capable enterprise-class
open-source application available. The Web content management
application feat
The Bricolage development team is pleased to announce the release of
Bricolage 1.8.1. This maintenance release address a number of
issues in
Bricolage 1.8.0. Here are the highlights:
Improvements
* More complete Traditional Chinese and Simplified Chinese
localizations. Al
ks,
David
--
David Wheeler AIM: dwTheory
[EMAIL PROTECTED] ICQ: 15726394
http://www.kineticode.com/ Yahoo!: dew7e
Jabber: [EMAIL PROTECTED]
Kineticode. Setting knowledge in
a
full-fledged templating system with complete HTML::Mason,
HTML::Template,
and Template Toolkit support for flexibility, and many other features.
It
operates in an Apache/mod_perl environment and uses the PostgreSQL RDBMS
for its repository. A comprehensive, actively-developed open source CMS,
Bricolag
ailed as "Most Impressive" in 2002 by
eWeek.
Learn more about Bricolage and download it from the Bricolage home page,
http://bricolage.cc/.
Enjoy!
David
--
David Wheeler AIM: dwTheory
[EMAIL PROTECTED] ICQ: 1572
ailed as "Most Impressive" in 2002 by
eWeek.
Learn more about Bricolage and download it from the Bricolage home page,
http://bricolage.cc/.
Enjoy!
David
--
David Wheeler AIM: dwTheory
[EMAIL PROTECTED] ICQ: 1572
ent, and uses the PostgreSQL
RDBMS for its repository. A comprehensive, actively-developed open
source CMS, Bricolage has been hailed as "Most Impressive" in 2002 by
eWeek.
Learn more about Bricolage and download it from the Bricolage home page,
http://bricolage.cc/.
Enjoy!
David
--
and object
database design. Anything with a PostgreSQL emphasis is an added bonus ;-)
TIA!
David
--
David Wheeler AIM: dwTheory
[EMAIL PROTECTED] ICQ: 15726394
Yah
On Thu, 10 May 2001, David Wheeler wrote:
> Hi All,
>
> I need to create a custom constraint (or a trigger?) on a table, and could
> use some help.
To answer my own question, this is what I've come up with. To anyone who
happens to decide to entertain him/herself by looking
On Wed, 14 Mar 2001, Oliver Elphick wrote:
> You could write a rule for each table/column that would substitute
> NULL for ''.
>
> However, the concept is all wrong. NULL means "I don't know what
> this value is". '' means "I know that this value is an empty string".
> Furthermore, having NULLs
Hi All,
Apologies for cross-posting.
I've ported a mod_perl application from Oracle to PosgreSQL, but have run
into a difference that's significant for web work. When I get a form field
submitted, if it's empty, mod_perl assumes it to be an empty string ('').
When I inserted empty strings into O
On Fri, 2 Mar 2001, John Madden wrote:
> What are the consequences of not calling ->finish()? I have several apps
> using DBD::Pg, and I don't think I've used it at all...
It just means that the statement handle is marked finished, and if you use
it again, it won't issue a warning saying that
On Thu, 1 Mar 2001, David Lynn wrote:
>
> Hello -
>
> When using DBD::Pg through DBI, can somebody tell me if it is necessary
> to be calling the $sth->finish routine? The DBI.pm documentation states
> that there is no need to call it if you call $sth->fetchrow_xxxref until
> the rows are exha
On Sun, 18 Feb 2001, Martijn van Oosterhout wrote:
> Tom Lane wrote:
>
> [snip]
> >
> > Then why are you bothering to maintain a case-sensitive index?
> >
> > There's no free lunch available here; if you think there is, then you
> > are misunderstanding what an index is. Either the index is i
On Thu, 15 Feb 2001, Michael Fork wrote:
> Indexes *can* and *will* be used if you create the appropiate
> functional indexes, i.e:
>
> CREATE INDEX idx_table_field_upper ON table(upper(field));
>
> SELECT field FROM table WHERE upper(field) LIKE upper('some string');
Hmmm...I'd hate to have t
Forgot to mention, I'm using 7.03.
Thanks,
David
On Thu, 15 Feb 2001, David Wheeler wrote:
> Hmmm... I'm trying to create an index,
>
> CREATE INDEX idx_server__host_name ON server(LOWER(host_name));
>
> But it won't create. Here's the error:
>
Hmmm... I'm trying to create an index,
CREATE INDEX idx_server__host_name ON server(LOWER(host_name));
But it won't create. Here's the error:
ERROR: DefineIndex: function 'upper(varchar)' does not exist
Anyone know what's up with that? The table does have the host_name column
of type VARCHAR.
On Thu, 15 Feb 2001, Tom Lane wrote:
> Not then either; you'd need to write
>
> SELECT *
> FROM mime_type
> WHERE LOWER(name) = LOWER('text/HTML');
>
> or equivalently
>
> SELECT *
> FROM mime_type
> WHERE LOWER(name) = 'text/html';
>
> which is what will result from constant-fold
Greetings All,
I've seem some references to TOAST in 7.1. Can anyone tell me what it is
and/or where I can read all about it and how it will solve all my problems
using BLOBs with PostgreSQL?
Thanks!
David
46 matches
Mail list logo
