I tried to import boundMetadata and this has become MetaData, and I'm
getting an import error
ImportError: No module named sqlalchemy_schemadisplay
So I was wondering if this has moved out of MetaData or been renamed.
Morgan
Michael Bayer wrote:
where its always been...
sqlalchemy_schemadisplay.py is not part of the SQLAlchemy distribution -
it's a separate script attached to that wiki page. You can download it
from the link at the bottom of the page.
Hope that helps,
Simon
-Original Message-
From: sqlalchemy@googlegroups.com
[mailto:[EMAIL
Hi,
running SA 0.3.11 against PG 7.4.
A SA query like
session.query(Node).query(func.any(Node.c.tools=='1234')
produces the following SQL code:
select from node where
where any(node.tools) = '1234'.
However Postgres does not support this syntax and complains
with a syntax error.
I am not sure, but, I think after you save feed, in this case you don't
need to call session.flush() maybe it is clearing the sessionand the
feed object too. try to remove it or test if is none after
session.flush()
session.save (feed)
session.flush ()
post= Post (
--
On Mon, Jan 07, 2008 at 01:00:20AM -0200, Marcos Dione wrote:
until yesterday did worked, but seems like after I upgraded to the
new sqla 0.4.2-1 from Debian Sid, it broke this way. am I doing anything
conceptually wrong?
--
$ sqlite3 test.sqlt
SQLite version 3.4.2
Enter .help for
Hey I've been busy and haven't had a chance to comment on the 0.4.2 release
yet.
Just wanted to give a big congrats on this release. I know it's one of the
few releases out that have spawned an a (and looks like a forthcoming b)
interim releases, but aside from those issues, it's a really nice
hey list -
another small bug with big side effects noted today, involving
assignment of full collections (this is related to the overhaul of
attribute history tracking in 0.4.2). If anyone is on 0.4.2 or 0.4.2a
and having problems with flushes of collections, use svn r4023 or wait
for
On Mon, Jan 07, 2008 at 03:41:22PM -0200, Marcos Dione wrote:
On Mon, Jan 07, 2008 at 01:00:20AM -0200, Marcos Dione wrote:
class SQLAObject (object):
def __init__ (self, **kwargs):
object.__init__ (self)
self.__dict__.update (kwargs)
I got this in IRC:
Hello again !
This is a bugfix release and is recommended for all users who are
currently on 0.4.2 or 0.4.2a. There is one critical bugfix which
involves history calculation on collection-based attributes. Other
significant bugfixes include a potential error that can arise with
Database is mysql
I am having a problem with unicode and binary type.
I am using an XML parse the return Unicode strings.
I have a table in mysql with the default character set as utf8
I set the charset to utf8 in the connect string to charset=utf8
I am trying to send a unicode string to the
On Jan 7, 2008 12:20 PM, Michael Bayer [EMAIL PROTECTED] wrote:
This is a bugfix release and is recommended for all users who are
currently on 0.4.2 or 0.4.2a.
You really should bump the version number after a version has been
released. 'a' and 'b' look like alpha and beta.
I installed 0.4.2
Mike Bernson wrote:
Database is mysql
I am having a problem with unicode and binary type.
I am using an XML parse the return Unicode strings.
I have a table in mysql with the default character set as utf8
I set the charset to utf8 in the connect string to charset=utf8
I am trying
On Jan 7, 2008, at 7:02 PM, Mike Orr wrote:
On Jan 7, 2008 12:20 PM, Michael Bayer [EMAIL PROTECTED]
wrote:
This is a bugfix release and is recommended for all users who are
currently on 0.4.2 or 0.4.2a.
You really should bump the version number after a version has been
released. 'a'
Mike You just need pick letter that are after release. Thing like p1 is greater
then release
from the egg docs.
(A note about versions: the egg runtime system understands typical version
numbering schemes, so it knows that versions like 1.2a1 and 1.2rc5 are
actually older than the plain
Hi Guys,
Maybe I'm missing something.
I tried to import boundMetadata and this has become MetaData, and I'm
getting an import error
ImportError: No module named sqlalchemy_schemadisplay
So I was wondering if this has moved out of MetaData or been renamed.
Morgan
Michael Bayer wrote:
I'm using mysql-5.1.15, sqlalchemy-0.4.2, mysql-python-1.2.2.
In SA-0.3, the docs read:
When Tables are reflected from the database using autoload=True, any
DEFAULT values set on the columns will be reflected in the Table
object as PassiveDefault instances.
This is not indicated behavior for
On Jan 8, 12:25 am, Michael Bayer [EMAIL PROTECTED] wrote:
passivedefaults are reflected in 0.4 just as they are in 0.3, as much
as the underlying database allows them to be discovered.
Thanks for the quick reply. I reduced this to a small example and it
seems the failure I'm encountering
Smythe wrote:
On Jan 8, 12:25 am, Michael Bayer [EMAIL PROTECTED] wrote:
passivedefaults are reflected in 0.4 just as they are in 0.3, as much
as the underlying database allows them to be discovered.
Thanks for the quick reply. I reduced this to a small example and it
seems the failure
18 matches
Mail list logo
