On Wednesday, August 25, 2010 12:26:42 Rawlins wrote:
Hello Guys,
Do we have support for CouchDB with SQlAlchemy? Can't seem to find
much information anywhere so I'm guessing not, just thought I would
check.
The SQL in SQLAlchemy pretty much says it all. The whole way CouchDB and
RDBMS
Thanks Diez and Daniel for the responses. It seems that this is the
way to go, but it's not quite there yet: now I can indeed load the
correct lass instance for my queries, but it seems to be restricted to
inherited classes already loaded in my current module. What would like
to do is being to
On Aug 19, 2010, at 10:39 PM, Eduardo Robles Elvira wrote:
Hello everyone:
This is my first post in this mailing list/group. My question is
simple: is there some way to tell sqlalchemy which method should be
called to instance models? Now, some background:
I'm working in a project with
On Tuesday 05 January 2010 19:26:56 Michael Bayer wrote:
On Jan 5, 2010, at 11:35 AM, Diez B. Roggisch wrote:
Hi,
we have a utility-script schemautil that allows us to re-create our DB
based on the metadata of SA, or simply dump the generated SQL for manual
inspection - the latter
Hi,
we have a utility-script schemautil that allows us to re-create our DB based
on the metadata of SA, or simply dump the generated SQL for manual
inspection - the latter is used when one writes migration scripts.
Now we noticed a strange behavior: the generated SQL isn't working for
On Thursday 09 April 2009 05:14:36 Bobby Impollonia wrote:
Now the decorator swallows exceptions silently. You have to reraise
the exception after rolling back like Michael did. I believe the
correct form is:
Darn.. you're right of course :)
Diez
On Wednesday 08 April 2009 05:53:12 Michael Bayer wrote:
On Apr 7, 2009, at 6:07 PM, rintin...@googlemail.com wrote:
Hey Everyone,
I'm new to SQLAlchemy (used to using Django's ORM but need to switch)
and there's just one thing I'm struggling with, which is when am I
supposed to create
not at all, when you commit/rollback, everything in the session is
expired (assuming you're on 0.5).
0.5.2
Doing a remove() at the end of a
request is a good way to ensure nothing is around from the previous
request but in theory its not needed. But again, I've no idea what
TG does in
Michael Bayer schrieb:
the close() will remove any objects left in the session and may help with
unit tests in that the subsequent tests aren't interfered with by objects
remaining from the previous test.
Where is the difference between a process running several tests and one
answering
Hi,
I've run into troubles with a TurboGears2-application that showed a difficult
to
track error when being integration tested - but not when the same test was run
locally.
Eventually I could track things down to two tests run after another - the first
somehow setting up the SA session in a
Hi,
with our old homegrown SQL-wrapping we enjoyed the possibility to time each
sql-query to drill down on performance bottlenecks.
This is currently not possible for us using SA. So I'd like to ask how to
approach this. I found some references on the net talking about profiling in
Index support for Postgres was recently added to the trunk and I merged
it into the reflection branch. You are welcome to check out the
reflection branch and give it a go. You could do a quick check like so:
import sqlalchemy as sa
from sqlalchemy.engine.reflection import Inspector
e =
Hi,
we've got some function-based indices we currently create using plain
text()-calls, like this:
CREATE UNIQUE INDEX
users_lower_email_index
ON
user_db.users (lower(email));
This works, but it would be nice to stay in the SA-world even with these
Sam schrieb:
One of the things I really liked about sqlobject was its versioning
plug-in. ( http://www.sqlobject.org/Versioning.html )
Is there anything similar for sqlalchemy? A google search turned up
versioned ( http://elixir.ematia.de/apidocs/elixir.ext.versioned.html
)
This is a
Hi,
I've got a table with a unique-constraint. And I've got an automatic
transaction management via decorator in place.
Now it can happen that the violation of that constraint occurs - then a
ProgrammingError is raised. As the violation is non-fatal, I try to
catch it, and continue.
The
Hi,
I have a rather complex query that I'd like to execute through SA on a
Postgres dababase.
This is the query:
SELECT questions.id, questions.question,
(SELECT count(attempts.id) AS count_1
FROM attempts
WHERE attempts.question_id = questions.id AND attempts.is_correct =
True) AS anon_1,
Michael Bayer schrieb:
On Sep 8, 2008, at 3:27 PM, Diez B. Roggisch wrote:
But it fails with
raise exc.DBAPIError.instance(statement, parameters, e,
connection_invalidated=is_disconnect)
OperationalError: (OperationalError) unrecognized token: : ...
text() treats :name as a bind
Michael Bayer schrieb:
On Sep 8, 2008, at 3:56 PM, Diez B. Roggisch wrote:
This does fail with the same error - the :: isn't properly
recognized. I
tried to escape as you said:
select([literal_column(rcount(*)\:\:float)],
and_(at.c.question_id ==
qt.c.id
yeah (select(x).as_scalar() / select(y).as_scalar).label('mylabel')
Ah. Good. I did look for alias, and obviously found the wrong thing.
Thanks,
Diez
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Hi,
I need to enhance sqlalchemy-migrate to consider schemas. I already wrote most
of the code - just one convenience-feature is missing: the possibility to
enumerate *all* schemas a certain engine has.
I can do that with a bit of sql of course - yet I wonder: is there a way to
accomplish
Michael Bayer schrieb:
not within SQLA, though you can propose this feature for sqlalchemy-
migrate.
schemas are a slippery topic among databases (such as on oracle, the
schema is really the user who owns the tables,
This is not entirely correct. Every user in oracle has a schema with
21 matches
Mail list logo
