On 22 Jun 2009, at 17:20, Oleg Broytmann wrote:
> On Thu, Jun 11, 2009 at 11:50:09AM +0300, Dan Pascu wrote:
>> On 11 Jun 2009, at 11:23, jonhattan wrote:
>>> Sam's Lists escribi?:
>>>> Is there a way to force SQLObject to quote it properly?
>>>>
On 11 Jun 2009, at 11:23, jonhattan wrote:
> Sam's Lists escribió:
>> So I keep humming along on this upgrade of someone else's code from
>> old versions of SQLObject and Mysql to the current SQLObject and
>> MySQL
>> 5...
>>
>> The current problem is that I have a table with the column name
>>
On Tuesday 03 February 2009, Oleg Broytmann wrote:
> On Tue, Feb 03, 2009 at 02:37:16PM -0500, Stef Telford wrote:
> > Oleg Broytmann wrote:
> > > Because SQLObject needs to generate unique alias names and a global
> > > counter is the simplest way to do it. Think about joining a table
> > > with
On Tuesday 02 December 2008, Oleg Broytmann wrote:
> > >No problem, I can release 0.10.4 with just one bugfix.
> >
> > Are you saying that you may release 0.10.4 now with only 1 bugfix, or
> > that when it will be released a few months later it will be done even
> > if it has 1 bugfix?
>
>I
On Tuesday 02 December 2008, Markus Gritsch wrote:
> On Tue, Dec 2, 2008 at 12:55 PM, Dan Pascu <[EMAIL PROTECTED]> wrote:
> >>Did you update and commit docs/News.txt with the bugfix?
> >> News.html is generated from News.txt.
> >
> > No I didn't. B
On Monday 01 December 2008, Oleg Broytmann wrote:
> On Mon, Dec 01, 2008 at 04:55:53PM +0200, Dan Pascu wrote:
> > It would be nice to announce the intention of making a new release on
> > the mailing list a few days before actually doing it. I had a pending
> > bugfix on
On Monday 01 December 2008, Oleg Broytmann wrote:
> Hello!
>
> I'm pleased to announce version 0.10.3, a minor bugfix release of 0.10
> branch of SQLObject.
> News since 0.10.2
> -
>
> * Changed interpretation of strings in the DB URI for boolean
> parameters: '0', 'no', 'off' and '
On Monday 01 December 2008, Oleg Broytmann wrote:
> Hello!
>
> I'm pleased to announce version 0.10.3, a minor bugfix release of 0.10
> branch of SQLObject.
It would be nice to announce the intention of making a new release on the
mailing list a few days before actually doing it. I had a pending
On Thursday 27 November 2008, Oleg Broytmann wrote:
> > Or maybe some parameter to the dburi (like backend) would be simpler
> > and cleaner.
>
>Either sqlite2://, sqlite3:// - or sqlite://...?backend=sqlite2.
My preference would be towards the last example using a backend parameter,
because
On Thursday 27 November 2008, Oleg Broytmann wrote:
> On Thu, Nov 27, 2008 at 04:35:43PM +0100, Markus Gritsch wrote:
> > currently the sqlite3 module is, if present, preferred over a
> > manually installed pysqlite2 module. Therefore it is not possible to
> > use a newer version of pysqlite than
On Thursday 13 November 2008, Darren Govoni wrote:
> Hi,
> I need to use a Large BLOB (the 'L' in blob), but SQLObject creates
> only a 'tinyblob' for BLOBCol in MySQL. Is there a way to tell
> SQLObject to make it a large blob?
Specify length=NNN to the column. Based on the size you specify it
On Friday 07 November 2008, Brian Long wrote:
> I'll admit I'm a newbie to SQLObject. I understand MySQL only
> supports cascade on delete using the InnoDB engine. When I define a
> class foreign key and specify "cascade=True", MySQL does not store
> this because the default engine is MyISAM.
>
>
I just committed a fix in handling unicode values. The StringCol had an
asymmetric behavior. When it read values from the database, it would use
the database encoding to get a string if the db drivers returned an
unicode value. However when an unicode value was given from python it
would use a
On Wednesday 10 September 2008, Oleg Broytmann wrote:
> On Wed, Sep 10, 2008 at 03:57:45PM +0300, Dan Pascu wrote:
> > On Wednesday 10 September 2008, Oleg Broytmann wrote:
> > > > The second fix is for incorrectly interpretted boolean values
> > > > passed via arg
On Wednesday 10 September 2008, Oleg Broytmann wrote:
> > The second fix is for incorrectly interpretted boolean values passed
> > via arguments to connectionForURI or via dburi parameters.
>
>Why Boolean is a class and not just a function? It never creates any
> instance of the class.
No part
I just commited some fixes regarding how the dburi parameters are handled.
The first fix is for incorrect handling of calls like
connectionForURI(dburi, cache=False)
when dburi already contains some parameters encoded in the URI, like
mysql://user:[EMAIL PROTECTED]/db?debug=1
The second fix
On Wednesday 18 June 2008, Petr Jakeš wrote:
> Hi,
> I am diging data from the Firebird database using quite complex SQL
> select command.
>
> Now I am using self._connection.queryAll(sql) method, but I would like
> to obtain data including the headers (column names) on the first row as
> well. Doe
On Sunday 17 February 2008, Nathan Edwards wrote:
> Oleg Broytmann wrote:
> > On Sat, Feb 16, 2008 at 10:46:41PM -0500, Nathan Edwards wrote:
> >> I still get the occasional "Commands out of sync..." exception from
> >> MySQLdb.
> >
> >Does the proposed patch help?
>
> Segfault, twice.
>
> Inte
On Sunday 17 February 2008, Nathan Edwards wrote:
> >Shouldn't that be
> > sqlhub.threadConnection = connectionForURI(connuri)
> >
> > for i in range(1000):
> > try:
> > a = AAA(value=1)
> > except dberrors.DuplicateEntryError:
> > a = AAA.byValu
On Sunday 17 February 2008, Oleg Broytmann wrote:
> On Sun, Feb 17, 2008 at 12:20:54AM +0200, Dan Pascu wrote:
> > If I'm for a change, then I'm for removing this limitation from
> > sqlite as well rather than putting it in other backends too.
>
>Thank you for st
On Saturday 16 February 2008, Oleg Broytmann wrote:
> On Sat, Feb 16, 2008 at 03:53:19PM +0200, Neil Muller wrote:
> > I've added a quick patch to do this, based of the logic in
> > sqliteconnection, to the sourceforge issue tracker (# 1894909), which
> > fixes the issue for me.
>
>Thank you!
>
On Monday 07 January 2008, Oleg Broytmann wrote:
> On Mon, Jan 07, 2008 at 12:56:04PM -0500, Glenn MacGregor wrote:
> > Maybe I need to backup at bit. I am somewhat confused at this point.
> > I need to insert a string which contains a non-ascii character into
> > my database table, that character
On Tuesday 27 November 2007, Oleg Broytmann wrote:
> On Tue, Nov 27, 2007 at 10:02:24PM +0200, Dan Pascu wrote:
> > Ok, makes sense not to set it everytime a new connection object is
> > created. But then how about the other things that get set below in
> > the if using_sqli
On Tuesday 27 November 2007, Oleg Broytmann wrote:
> On Tue, Nov 27, 2007 at 09:34:31PM +0200, Dan Pascu wrote:
> > I think the extra if using_sqlite2 test you added is not necessary.
> > There is already such a test a bit below that could accommodate the 2
> > lines:
On Tuesday 27 November 2007, Oleg Broytmann wrote:
> On Fri, Nov 09, 2007 at 09:13:30AM +0200, Dan Pascu wrote:
> > IMO if we use pysqlite2 or sqlite3 we shouldn't import
> > encoders/decoders from the old sqlite module, but instead use base64
> > always.
>
>
On Tuesday 27 November 2007, Oleg Broytmann wrote:
> On Tue, Nov 27, 2007 at 03:17:23PM +0100, Markus Gritsch wrote:
> > Having this try/except
> > here unconditionally for all cases
>
>Let's satisfy all (to possible extent) - let's make a parameter for
> MySQLConnection (and SQLObject DB URI)
On Friday 23 November 2007, Oleg Broytmann wrote:
>Currently BLOBCol on sqlite uses sqlite.encode() and sqlite.decode()
> if the very module sqlite (PySQLite version 1) is found, and uses
> base64 if the sqlite module is not available. This is problematic, so
> in the future BLOBCol will use on
There is an issue in the sqlite backend regarding encoding/decoding. Below
is the relevant code from the __init__ method:
class SQLiteConnection(DBAPI):
[...]
def __init__(self, filename, autoCommit=1, **kw):
global sqlite
global using_sqlite2
if sqlite is None:
On Monday 22 October 2007, Jaime Wyant wrote:
> Hi all. Can anyone tell me why the code below commits rows to the
> table? I've read the documentation and I'm not quite sure why it is
> happening. # BEGIN CODE SNIPPET
> from sqlobject import *
>
> conn = connectionForURI('mysql://user:[EMAIL PROTE
On Friday 19 October 2007, Markus Gritsch wrote:
> On 10/19/07, Oleg Broytmann <[EMAIL PROTECTED]> wrote:
> > Hello!
>
> Hi Oleg,
>
> > On Fri, Oct 19, 2007 at 09:39:05AM +0200, Markus Gritsch wrote:
> > > in SQLObject a BoolCol() is stored as TINYINT(4) in the MySQL
> > > backend and as TINYINT in
On Friday 19 October 2007, Markus Gritsch wrote:
> From this page I cannot tell that TINYINT is the equivalent to
> TINYINT(1), maybe I just didn't see it.
integer_type(M) doesn't restrict the size of the storage, it only
specifies the maximum display width. In other words M doesn't specify the
paul kölle wrote:
> IMO the real solution (tm) would be to change ForeignKey() (and probably
> others) to match the type of the referrenced column. Otherwise the id
> code using UNSIGNED INT has to be reverted. Not sure what it buys you
> anyway...
>
it doubles the range of possible ids (it als
Currently the mysql backend for sqlobject uses an int for the table id
when generating the schema. The attached patch modifies it to use an
unsigned int. This will result in doubling the range of available ids and
also makes more sense considering that the table id is never negative.
--
Dan
I
On Monday 29 January 2007 19:03, Oleg Broytmann wrote:
>I am going to add the following tests:
>
> def test_dict():
> assert sqlrepr({"key": "value"}, "sqlite") == "('key')"
>
> def test_sets():
> try:
> set
> except NameError:
> pass
> else:
> assert sql
Any comment on this?
On Wednesday 24 January 2007 23:32, Dan Pascu wrote:
> The attached patch allows one to use set/frozenset sets (available
> since python 2.4) or Set/ImmutableSet sets (available since python 2.3)
> as sequences passed to the IN operator (currently only lists and tup
The attached patch allows one to use set/frozenset sets (available since
python 2.4) or Set/ImmutableSet sets (available since python 2.3) as
sequences passed to the IN operator (currently only lists and tuples can
be used). In fact it'll accept a set of values everywhere a list/tuple of
value
On Tuesday 16 January 2007 17:35, Oleg Broytmann wrote:
> On Tue, Jan 16, 2007 at 06:28:53PM +0300, Oleg Broytmann wrote:
> > > Further, Dan had also some concerns about transactions. He wrote
> > > that if the reconnectiong would happen at MySQLdb level, it could
> > > be handled gracefully, but
As I said before, this approach will mess transactions badly, as it can
change the connection in the middle of a transaction and the caller will
be unaware of this as there will be no indication of what happened. The
reconnect feature that is implemented by the mysql client library knows
if th
On Thursday 04 January 2007 20:52, David Turner wrote:
> On Sat, 2006-12-30 at 08:13 +0200, Dan Pascu wrote:
> > On Thursday 28 December 2006 21:40, David Turner wrote:
> > > I should probably also have a method which returns a dict of only
> > > items that have changed
On Saturday 30 December 2006 12:00, Markus Gritsch wrote:
> By reading Andy Dustmans (creator and maintainer of MySQLdb) reply at
> http://sourceforge.net/forum/forum.php?thread_id=1639447&forum_id=70461
> it is quite unlikely that a readily available patch, which would
> implement this, will be ap
On Thursday 28 December 2006 21:40, David Turner wrote:
> I should probably also have a method which returns a dict of only items
> that have changed between this version and a specified version (by
> default, the current version).
Such a method would be nice.
--
Dan
---
On Friday 29 December 2006 17:20, Oleg Broytmann wrote:
> On Fri, Dec 29, 2006 at 09:45:35AM +0200, Dan Pascu wrote:
> > Attached is a patch that fixes this in a better way. It still allows
> > reconnects if the database connection was lost because of a server
> > restart or
On Friday 29 December 2006 10:02, Oleg Broytmann wrote:
> > +for c in range(0, 3):
> > try:
> > if self.need_unicode:
> > # For MysqlDB 1.2.1 and later, we go
> > @@ -88,7 +100,9 @@
> > else:
> > return
On Thursday 28 December 2006 20:58, Oleg Broytmann wrote:
> On Thu, Dec 28, 2006 at 07:50:23PM +0100, Markus Gritsch wrote:
> > Well, this would not solve the problem intoduced with SQLObject 0.8.
> > An Error 2006 occurres in the following scenario using SQLObject 0.7:
> > * My application is runn
On Thursday 28 December 2006 20:50, Markus Gritsch wrote:
> Well, this would not solve the problem intoduced with SQLObject 0.8.
> An Error 2006 occurres in the following scenario using SQLObject 0.7:
> * My application is running, being connected to the MySQL database.
> * The MySQL service is sto
On Thursday 28 December 2006 20:36, Oleg Broytmann wrote:
> On Thu, Dec 28, 2006 at 06:56:08PM +0100, Markus Gritsch wrote:
> > Since there was no comment on the e-mail below, I resend it in case
> > it got lost.
>
>Sorry for the silence. I have got it the first time. Just don't have
> time to
On Friday 27 October 2006 14:37, sophana wrote:
> Frank Barknecht a écrit :
>
> I don't know if it is a coincidence. Spam started in the same time a
> guy was complaining about sourceforge mailling lists, and proposed to
> use google groups.
I wouldn't put this behind him considering what other pe
On Thursday 26 October 2006 13:23, Oleg Broytmann wrote:
> On Thu, Oct 26, 2006 at 01:06:24PM +0300, Dan Pascu wrote:
> > What about defining this new functionality using a different column
> > type, say SQLForeignKey or DBForeignKey?
>
>It would be much harder to support
On Thursday 26 October 2006 12:21, Oleg Broytmann wrote:
> Hello.
>
> On Thu, Oct 26, 2006 at 09:18:36AM +0300, Dan Pascu wrote:
> > Will it be possible to still use the current capability of SQLObject
> > to use foreign keys even on tables that are not capable of such thing
On Wednesday 25 October 2006 17:36, Oleg Broytmann wrote:
> On Wed, Oct 25, 2006 at 02:18:40PM +, Matthew Wilson wrote:
> > I created the following two tables, ran the sql, and then discovered
> > that the foreign keys were not in the database:
>
>Foreign key constraints will be implemented
On Tuesday 24 October 2006 17:49, Markus Gritsch wrote:
> Since Python string objects are immutable, a new instance of the
> object has to be created, which can become expensive, if the strings
> become quite long. A performant way to concatenate Strings is to add
> the strings to a list, and join
On Tuesday 24 October 2006 16:00, Hartmut Goebel wrote:
> Jorge Godoy schrieb:
> > Dan Pascu <[EMAIL PROTECTED]> writes:
> >> That is a common myth. People should test things themselves instead
> >> of believing everything that is written on the net.
> >
>
On Tuesday 24 October 2006 13:41, sophana wrote:
> > This is correct, since you tell python to add a Unicode-String to an
> > Asc-String:
> >s += 'café'
> > is the same as
> >s = s + 'café'
>
> Ok, but why is the right string encoded into ascii and not into the
> same encoding as the left u
On Tuesday 24 October 2006 13:30, Hartmut Goebel wrote:
> BTW: Using string-concationation is bad habbit, since it's slow. One
> should prever fthe % operator.
That is a common myth. People should test things themselves instead of
believing everything that is written on the net.
Here are some tes
On Tuesday 10 October 2006 23:48, Ilias Lazaridis wrote:
> You've ommitted the central par of my message:
Maybe it was his polite way of saying he is not interested. You really
insult the intelligence of people on this list continuing to make these
posts after your modus operandi was exposed by
On Monday 09 October 2006 07:21, Ilias Lazaridis wrote:
> >> No need, I'll choose another product, where contribution makes
> >> sense.
> >>
> >> As suggested, the project lead should shutdown this project (or at
> >> least place a visible remark on the website), thus other people to
> >> not loose
On Tuesday 03 October 2006 20:10, Oleg Broytmann wrote:
> On Tue, Oct 03, 2006 at 07:10:09PM +0300, Dan Pascu wrote:
> > So it seems that for objects that are obtained from classes derived
> > from object (strings, dictionaries, Obj(object), ...) it won't reuse
> > the
On Tuesday 03 October 2006 18:17, Oleg Broytmann wrote:
> I don't think the problem is in .expireAll(). What is going on, as I
> understand, is that .expireAll() clears the cache and as now there are
> only weak reference to the row, Python garbage-collects it immediately.
> After that Python is fr
On Tuesday 03 October 2006 01:07, Ilias Lazaridis wrote:
> Dan Pascu wrote:
> > On Monday 02 October 2006 18:37, Ilias Lazaridis wrote:
> >>> -- documentation is a big plus.
> >>
> >> again, can be provided incrementally
> >
> > Experience show
On Monday 02 October 2006 22:07, Oleg Broytmann wrote:
>I ran a few tests from the SQLObject test suite - all tests passed.
> So I believe it works at least with Python 2.3.
I can confirm it works with python2.3 as I use them together successfully.
That import was the only issue I encountered
On Monday 02 October 2006 21:12, Oleg Broytmann wrote:
> On Mon, Oct 02, 2006 at 09:01:14PM +0300, Dan Pascu wrote:
> > On Monday 02 October 2006 11:16, Oleg Broytmann wrote:
> > > -- do not break compatibility, remember, SQLObject is still
> > > supports Python 2.2;
&g
On Monday 02 October 2006 18:37, Ilias Lazaridis wrote:
> > -- documentation is a big plus.
>
> again, can be provided incrementally
Experience shows that this almost never happens. Once someone gets his pet
code integrated, they never care to document it. They know how it works
and don't need d
On Monday 02 October 2006 11:16, Oleg Broytmann wrote:
> -- do not break compatibility, remember, SQLObject is still supports
> Python 2.2;
Unfortunately this is more a desired thing than an actual fact. SQLObject
depends on FormEncode, and FormEncode contains python2.4 specific code.
It is true
06 17:08, Oleg Broytmann wrote:
> Hello! I'd like to return to the problem the patch caused in
> test_cache.
>
> On Mon, May 29, 2006 at 10:26:49PM +0300, Dan Pascu wrote:
> > def __init__(self, instance):
> > -self.instance = instance
> > +self
On Thursday 28 September 2006 22:00, Oleg Broytmann wrote:
> On Thu, Sep 28, 2006 at 09:16:49PM +0300, Dan Pascu wrote:
> > I think the original's poster patch is the right thing to do.
>
>Better to say "it could have more sense". Unfort
On Thursday 28 September 2006 20:16, Oleg Broytmann wrote:
> On Thu, Sep 28, 2006 at 02:04:00PM -0300, Loic Jeannin wrote:
> > http://www.tahorg.net/stuff/sqlobject-mysql-bug
>
>I think this should be solved with a proper style.
I think the original's poster patch is the right thing to do. I'v
On Friday 15 September 2006 12:41, Hiroki Tamakoshi wrote:
> On Fri, 15 Sep 2006 11:30:11 +0200
> calling gc.collect() doesn't change the memory usage.
> (Dan's patch is applied)
>
> obj_list = []
> for i in xrange( 1000 ):
> obj = SomeObject( parameters ... )
> obj_list.append( obj ) #
On Friday 15 September 2006 12:41, Hiroki Tamakoshi wrote:
> On Fri, 15 Sep 2006 11:30:11 +0200
>
> "Markus Gritsch" <[EMAIL PROTECTED]> wrote:
> > Because you cannot explicitely delete an object. By calling del on a
> > variable which holds a reference to it, you just remove this
> > particular r
On Thursday 14 September 2006 21:44, Oleg Broytmann wrote:
> On Thu, Sep 14, 2006 at 09:38:59PM +0300, Dan Pascu wrote:
> > BTW, what is the status on this? Do you intend to include it? If so,
> > what is holding it back for so long?
>
>I didn't want to include in 0
On Wednesday 13 September 2006 20:21, Oleg Broytmann wrote:
>There is a patch created by Dan Pascu <[EMAIL PROTECTED]> that may
> fix that. Can you test it (attached)? Does it help?
BTW, what is the status on this? Do you intend to include it? If so, what
is holding it back
On Monday 07 August 2006 19:14, Oleg Broytmann wrote:
> On Mon, Aug 07, 2006 at 11:00:39AM -0500, Rick Flosi wrote:
> > Could we handle this problem by creating a database view
>
>Do all the backends supported by SQLObject support VIEWs?
MySQL 4.x doesn't support them. There may be others.
--
On Friday 04 August 2006 14:59, sophana wrote:
> I waited 8 hours, the sqlobject patch doesn't work. It goes in an
> infinite loop.
> It's worse...
That's because your python-mysqldb module doesn't support reconnecting.
You need to patch python-mysqldb for this to work if you use mysql-5.x
And th
reconnect.
I have also noticed that if I use python-mysqldb with the patch applied
and compiled with libmysqlclient from mysql-4.x, it will not reconnect to
a mysql-5.0 server after it timeouts. If it is complied against
libmysqlclient from mysql-5.x then it works.
>
> Thanks
&g
I think this patch looks dubious.
1. It tries to solve a backend specific issue in the backend agnostic
dbconnection module. Importing mysql specific stuff in dbconnection
should be a big no-no
2. It erroneously considers any OperationalError exception as a need to
reconnect, instead of doing
On Sunday 30 July 2006 13:58, Oleg Broytmann wrote:
> On Wed, Jul 26, 2006 at 08:03:16AM +0300, Mircea Amarascu wrote:
> > I've read the "Handling exceptions" topic on this mailing list
> > (http://www.mail-archive.com/sqlobject-discuss%40lists.sourceforge.ne
> >t/msg00975.html) and decided to take
On Friday 28 July 2006 11:13, Oleg Broytmann wrote:
> > I've discovered that the Database API Specification v2.0 is followed
> > by both MySQL and
> > SQLite Python modules, so all that need to be done in this case was a
> > one-to-one mapping between
> > their exceptions and the SQLObject defined
Following the discussion we had about 2 months ago about having sqlobject
raise a set of exceptions independent of the backend used, I asked a
colleague of mine to implement this.
He did it for the mysql and sqlite backends, for which we have experience.
Not having any experience with the other
Just a test to check if the mailing list works. Please ignore.
(someone tried to send a patch to the list and it hasn't appeared on the
mailing list after more than 10 hours)
--
Dan
-
Take Surveys. Earn Cash. Influence the
On Thursday 15 June 2006 15:21, Oleg Broytmann wrote:
> On Thu, Jun 15, 2006 at 02:11:12PM +0300, Dan Pascu wrote:
> > What about the other 2 patches I sent?
> > The one to break some cyclic references
>
>I am going to test it, but I think I will apply it after 0.7.1.
&
On Wednesday 14 June 2006 17:47, Oleg Broytmann wrote:
> On Wed, May 31, 2006 at 03:18:38PM +0300, Dan Pascu wrote:
> > -opts['timeout'] = float(popKey(kw, 'timeout'))
> > +if using_sqlite2:
> > +op
On Thursday 01 June 2006 05:30, Jorge Vargas wrote:
> >The biggest problem is to translate exceptions. One DB API driver
> > raises
> > OperationError when another raises IntegrityError. We need to collect
> > information about what exceptions every driver raise in what
> > situations.
>
> I do
On Thursday 01 June 2006 05:46, Jorge Vargas wrote:
> On 5/31/06, Dan Pascu <[EMAIL PROTECTED]> wrote:
> As an example of why most of the time you will send out the "generic"
> this are mysqld error classes.
>
> class MySQLError(StandardError):
> class Warning(W
On Wednesday 31 May 2006 23:28, Oleg Broytmann wrote:
>The problem that I see with the plan is that if SQLObject starts
> catching all exceptions from DB API drivers and translate them to a
> single exception that would mask low-level exceptions and it would be
> hard to monitor what driver rai
On Wednesday 31 May 2006 21:28, Oleg Broytmann wrote:
>There is an item in the TODO to unify exceptions. But nobody's
> working on it now. Do you want to be the one?
What is the intention regarding this?
Is the plan to raise a single generic exception (say DatabaseError) with
specific detail
On Wednesday 31 May 2006 21:28, Oleg Broytmann wrote:
> On Wed, May 31, 2006 at 04:06:58PM +0300, Dan Pascu wrote:
> > However the code can raise exceptions from the backend (for example
> > connection errors, or integrity errors when duplicate rows are
> > inserted)
On Wednesday 31 May 2006 14:25, Oleg Broytmann wrote:
> On Wed, May 31, 2006 at 02:20:26PM +0300, Dan Pascu wrote:
> > Exception exceptions.RuntimeError: 'maximum recursion depth exceeded'
> > in > > ignored
>
>It was fixed long ago. Please try SQLObjec
I'm curious if there is a standard recipe on how to handle exceptions
raised by the database backend modules.
While I use sqlobject I obviously do not want to have to deal with
specific details of the database backends. One of the reasons of using it
is that it hides the database type and acce
When I specify a timeout for a sqlite connection that uses the older
sqlite db module I get the following warning:
/usr/lib/python2.3/site-packages/sqlite/main.py:472: DeprecationWarning:
integer argument expected, got float
self.db.sqlite_busy_timeout(timeout)
This is because the older sqli
If I try to create a transaction object and it fails in its __init__
method (for example it cannot get a connection because the db is down)
the _obsolete attribute will be missing and when __del__ is called to
destroy the unrealized object it will oscillate forever between the
__getattr__ and
On Tuesday 30 May 2006 17:41, Simon Cross wrote:
> > I think you misread my example. The test script I attached
> > creates a database object and immediately destroys it with
> > o.destroySelf() so the net result should be zero because the
> > object is removed from both the database and the sqlobj
On Monday 29 May 2006 23:59, Simon Cross wrote:
> Hi Dan,
>
> On 5/29/06, Dan Pascu <[EMAIL PROTECTED]> wrote:
> > I've found that the problem lies in 2 circular references: one is the
> > instance attribute of sqlmeta which points back to the object and
> >
Hi,
I've started using sqlobject in a project and I found that it leaks memory
after an object derived from SQLObject is destroyed and deleted.
The code is like:
obj = SomeObject(parameters...)
obj.destroySelf()
del obj
A simple infinite loop like this:
while True:
o = SomeObject(parame
92 matches
Mail list logo
