Hi Shane,
The bug comments suggest wrapping the subquery in "select * from (...)"
to materialize the subquery only once. I've attached a patch that does
that. Let me know whether it helps or hurts. Note that this isn't the
final form of the patch since the other supported databases don't ne
Anton Stonor wrote:
I just had a look at this and am capable of reproducing it (on Plone
3.1.1) -- but also with filestorage! So it doesn't really look like a
RelStorage issue to me.
Thanks for working on this, Anton. I think I can call this issue closed
WRT RelStorage.
Shane
Hi there,
Ben Mason wrote:
We've come across the following problem: When trying to revert to an old
version of a page, we get a unicode error:
Module Products.CMFEditions.ZVCStorageTool, line 505, in _encodeMetadata
UnicodeDecodeError: 'ascii' codec can't decode byte 0x80 in position 0:
ord
Shane,
I'm using this buildout for Plone 3:
http://svn.plone.org/svn/collective/collective.relstorage/trunk/
Which is using RelStorage from:
svn://svn.zope.org/repos/main/relstorage/trunk/relstorage
Thanks
Ben
On 23/04/2008 16:12, "Shane Hathaway" <[EMAIL PROTECTED]> wrote:
> Alan Runyan
Alan Runyan wrote:
I have a feeling its CMFEditions because he is trying to do fancy stuff with the
transaction note(s) in the ZODB. At a gut level: I feel 100x more comfortable
with Shane's code (ZODB/RelStoage) than CMFEditions. Which is notoriously
insane.
Thanks. :-) However, early vers
This appears to be a CMFEditions problem not a RelStorage problem.
The ways to escalate a bug:
Write a test case that demonstrates the bug. Do it yourself.
a. Ensure tests fail reliably
b. Email the author with failing tests cases and software versions
to allow him to reproduce
c.
We're currently benchmarking RelStorage to see if it's a viable alternative
to ZEO.
We've come across the following problem: When trying to revert to an old
version of a page, we get a unicode error:
Traceback (innermost last):
Module ZPublisher.Publish, line 119, in publish
Module ZPublishe
Shane Hathaway wrote:
http://ora-24813.ora-code.com/
That page suggests you may be running different versions of Oracle on
the client and server. I'm sure there are other possibilities, of course.
Indeed, hopefully Guy will take a look some time.
I should stress that this error was extremel
Chris Withers wrote:
Hi Shane,
First real world error from the Oracle adapter:
Module ZPublisher.Publish, line 125, in publish
Module Zope2.App.startup, line 238, in commit
Module transaction._manager, line 96, in commit
Module transaction._transaction, line 395, in commit
Module
Tres Seaver wrote:
> Shane Hathaway wrote:
>> However, I think we can still take advantage of listen and notify in a
>> slightly different way. Currently, the Postgres adapter rolls back the
>> load transaction on every connection close, but if it instead leaves the
>> session idle with a transact
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Shane Hathaway wrote:
> Tres Seaver wrote:
>> I've got a question for you on the removal of the LISTEN / NOTIFY stuff
>> in the Postgresql adapter: it looks to me as though your code was not
>> doing the async check-for-notifies as shown in the 'notif
Tres Seaver wrote:
> I've got a question for you on the removal of the LISTEN / NOTIFY stuff
> in the Postgresql adapter: it looks to me as though your code was not
> doing the async check-for-notifies as shown in the 'notify.py' in the
> psycopg2 examples:
>
> http://www.initd.org/tracker/psycop
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Shane Hathaway wrote:
> Hi all,
>
> RelStorage now exists in the Zope subversion repository here:
>
>http://svn.zope.org/relstorage/trunk/
>
> I have also created a wiki page:
>
>http://wiki.zope.org/ZODB/RelStorage
>
> Testing help and da
13 matches
Mail list logo
