are you working with the ORM or just SQL ? is it the same version
of SA as the one you ran on the laptop ?
On Jan 21, 2006, at 12:33 AM, Robert Leftwich wrote:
I've just setup my app on a dual Athlon 64 4800 box running FreeBSD
6 and am finding that mapping of large data sets is significa
hey there -
update and try it again. the fix i made for you yesterday was
slightly incorrect. youll notice that the dependency graph produced
for the second commit is much smaller after you update this change.
when you have the TEST_SELFREF turned on, even though theres no
actual paren
I've just setup my app on a dual Athlon 64 4800 box running FreeBSD 6 and am
finding that mapping of large data sets is significantly slower and takes up
almost twice as much memory cf my laptop. The database is much faster, psql
queries are returned very speedily, so that is not the problem, an
On Jan 20, 2006, at 5:36 PM, Michael Bayer wrote:
Also, if you want to gain some understanding of objectstore, which
would be helpful if you have any ideas to offer, i just committed a
nicer "dependency dump" function. If you turn on
sqlalchemy.mapping.objectstore.LOG = True , youll see a "tas
On Jan 20, 2006, at 4:17 PM, [EMAIL PROTECTED] wrote:
nevertheless, i also wonder if this is something
that you expect to support in the future?
sorry to be bringing up less common use-cases,
but sqlalchemy gives me the hope of leveraging
these features through python.
I would love to add th
On Jan 20, 2006, at 11:32 AM, Michael Bayer wrote:
oh yeah, i forgot. Were we going to go with the information_schema
package being able to give you an SQL-92 compliant gateway to the
standard
information_schema tables, but only if that database has them
available ?
or did we want to make it
On Jan 19, 2006, at 8:21 PM, Michael Bayer wrote:
OK, that was a bug where it breaks down a save dependency into a
hierarchical graph of smaller dependencies, when you have a circular
mapper going...it was forgetting about all the other dependent
operations on the original save dependency. my
On Jan 20, 2006, at 6:12 AM, Jonathan Ellis wrote:
Incidently, the PEP has been updated following a python-dev thread in
which Ian Bicking noted that "I personally prefer cls, there are some
who use klass, and I haven't see class_ used." The PEP now recommends
the use of cls.
fwiw, as i unders
[EMAIL PROTECTED] wrote:
> ps. mike, did you have any further thoughts
> on the information_schema?
oh yeah, i forgot. Were we going to go with the information_schema
package being able to give you an SQL-92 compliant gateway to the standard
information_schema tables, but only if that database
well still, cant fault the code for following the style guide
:)"class_" is still up on the python site's PEP.
Jonathan Ellis wrote:
> On 1/6/06, Michael Bayer <[EMAIL PROTECTED]> wrote:
>>
>> all of my python conventions came from the styleguide:
>>
>> http://www.python.org/peps/pep-0008.html
On 1/6/06, Michael Bayer <[EMAIL PROTECTED]> wrote:
>
> all of my python conventions came from the styleguide:
>
> http://www.python.org/peps/pep-0008.html
>
> so this would explain why Im using "class_":
>
> If your public attribute name collides with a reserved keyword, append
>a single tra
11 matches
Mail list logo
