Michael Bayer wrote:
also i dont understand how sticking a __call__() on SessionContext would
have any impact on its existing get/set/del operations.
It's totally unnecessary and it clutters the interface. Unnecessary methods/properties/etc. are
confusing because they make people wonder "
Michael Bayer wrote:
ive liked __session__ all along. Dan's concern is that people will
think __session__ returns the session which the instance is attached to,
not just the "contextual" session which may be different.
Yeah, I'm not thrilled about __session__ for that exact reason. However,
ah...are you using any custom types ? unfornately I had to shake up
the interface for the TypeEngine object again. otherwise, yes id
need more detail since all the unit tests pass.
On May 2, 2006, at 4:01 PM, Florian Boesch wrote:
Mike, thx
True, for the simple example it worked, but no
On 5/2/06, Michael Bayer <[EMAIL PROTECTED]> wrote:
between() on the Column object is probably only in the trunk:
mytable.c.col1.between(3,5)
there *should* be a standalone between() function available in the
release which I think has an underscore (the underscore is optional
in the tru
Mike, thx
True, for the simple example it worked, but now I get an exception for my
application code.
File "build/bdist.linux-i686/egg/sqlalchemy/engine.py", line 868, in
__getattr__
File "build/bdist.linux-i686/egg/sqlalchemy/engine.py", line 812, in _get_col
File "build/bdist.linux-i686/e
On May 2, 2006, at 2:47 PM, Gustavo Niemeyer wrote:
This will not only avoid the underscore, but also create a visible
distinction between SQL and Python syntax.
and blur the distinction between SA and SQLObject ;)
ive grown pretty accustomed to the underscore syntax and now it looks
bette
between() on the Column object is probably only in the trunk:
mytable.c.col1.between(3,5)
there *should* be a standalone between() function available in the
release which I think has an underscore (the underscore is optional
in the trunk):
between_(mytable.c.col, 3, 5)
On
Hey All,
Tossed together this patch for databases/postgres.py (see attached) to support
pgsql's SELECT DISTINCT ON (col1, col2, col3...) col1, col2, ...
functionality. Included are testcases for it.
Supported syntax is:
select([...],distinct=True) # Classic 'DISTINCT' behavior on
I'd just like to ask if there would be any interest in renaming
functions that translate into SQL statements into their uppercase
equivalent, to avoid underscoring them due to conflicts with
existent Python syntax.
This will not only avoid the underscore, but also create a visible
distinction betw
florian -
download the trunk and you will see your memory usage is steady as a
rock.
- m
On May 2, 2006, at 7:04 AM, Florian Boesch wrote:
Hi,
Since more then one processes modifies my database I invoke
objectstore.clear()
prior to fetching data I need to display.
I noticed that I hav
ive liked __session__ all along. Dan's concern is that people will
think __session__ returns the session which the instance is attached
to, not just the "contextual" session which may be different.
In my original proposal, i was going to just have __session__ just
return wahtever contextu
http://www.sqlalchemy.org/docs/sqlconstruction.myt says "Supported
column operators so far are ... like(), startswith(), endswith(),
between(), and in()". But between() seems not to work:
In [110]:s = users.select(users.c.age.between(30,39))
---
> how about 'contextualsession' or somethingI really dislike the
> name "contextsession".
__session__ would probably be fine, unless you're afraid to conflict
with something else. We use __int__ to get ints out of an object,
__nonzero__ to get a boolean, and so on. Using __session__ looks li
> So would it work like this:
>
> callable = MyClass.__sessioncontext__
> session = callable()
>
> or like this:
>
> callable = MyClass.__sessioncontext__()
> session = callable()
>
> I'm not really liking the second one because it requires this to get a
> session directly from the object:
>
Hi,
Since more then one processes modifies my database I invoke objectstore.clear()
prior to fetching data I need to display.
I noticed that I have a huge objectleak all around (about 10k objects never get
collected at every request)
I wrote a testprogramm (atached) wich in a nutshell does
while
15 matches
Mail list logo
