On Thu, Nov 05, 2009 at 19:07 -0500, Michael Bayer wrote:
it would be an empty PrimaryKeyConstraint. It serves as the
primary_key column collection on the table object.
Thanks for clarifying this. Are there any plans to reflect the names of
Constraints in 0.6?
That would ease the removal of
On Tue, Nov 03, 2009 at 16:29 -0500, Michael Bayer wrote:
the error is raised directly by psycopg2.
I was afraid that the error is with psycopg2. Are you aware of any
bugtracker, mailing list or IRC channel that discusses psycopg2?
I'd try taking out the ; at the end of the statement,
That
On Tue, Nov 03, 2009 at 21:57 +0100, Wolodja Wentland wrote:
psql_engine = create_engine(
'postgresql+psycopg2://babilen:ax8xwymferm...@localhost/typeerr_bug')
^^ oops
Note to self: Double check for sensitive data :-). Guess it is time
On Tue, Nov 03, 2009 at 22:49 +0100, Wolodja Wentland wrote:
On Tue, Nov 03, 2009 at 16:29 -0500, Michael Bayer wrote:
the error is raised directly by psycopg2.
I was afraid that the error is with psycopg2. Are you aware of any
bugtracker, mailing list or IRC channel that discusses psycopg2
:
--- snip ---
$ psql -d typeerr_bug insert_stmt.sql
INSERT 0 32173
--- snip ---
What is causing this behaviour and even more importantly: What can I do
about it?
kind regards
Wolodja Wentland
signature.asc
Description: Digital signature
Hi all,
I am having a problem getting database creation on PostgreSQL done
correctly in an API that I am writing. I am using a svn checkout of SA trunk
from yesterday if that is important.
I have use the following code to create the database:
--- snip ---
...
try:
import psycopg2.extensions
On Tue, Oct 27, 2009 at 16:22 -0400, Michael Bayer wrote:
Wolodja Wentland wrote:
def create(self):
Create this database
# set isolation level to AUTOCOMMIT
# postgres can't CREATE databases within a transaction
self._admin_engine.connect
with IPython it is wise to check the
'python' behaviour before development code against this bug.
kind regards
Wolodja Wentland
signature.asc
Description: Digital signature
On Thu, Sep 10, 2009 at 23:27 +0200, Wolodja Wentland wrote:
Hi all,
I observed that if I define a relation (foo_query) as lazy='dynamic' and
access all referenced entities with foo_query.all() that the query will
be executed every time i access it. That is not a big surprise
, lazy='dynamic')
})
Which one is faster? Does it make a difference, given the
optimisation/cache in the database? Will it just mean more bloat in the
mapper definition?
thanks
Wolodja Wentland
signature.asc
Description: Digital signature
Wolodja Wentland
signature.asc
Description: Digital signature
way to do so, or do i have to define the index
by myself?
with kind regards
Wolodja Wentland
signature.asc
Description: Digital signature
On Tue, Sep 08, 2009 at 13:06 +0200, Wolodja Wentland wrote:
is it possible to drop primary key indexes from within SA? I already
found the table.indexes set, but it does not contain the primary key
index. I can therefore drop all indexes for a table except the primary
key one.
I did some
? Is this advisable? Is
there a better way to achieve this?
with kind regards and thanks for this great tool!
Wolodja Wentland
signature.asc
Description: Digital signature
On Tue, Sep 08, 2009 at 17:35 -0400, Michael Bayer wrote:
Wolodja Wentland wrote:
I can't drop these constraints as well. Even if i accept that my tables
are created with primary key definitions the recipe you showed me does
not work. It fails with:
--- snip ---
...
/sqlalchemy
', 'Susan']).
^ ^
in_() takes a *list* not a number of arguments.
with kind regards
Wolodja Wentland
signature.asc
Description: Digital signature
16 matches
Mail list logo
