Hi all,
I am porting an existing webapp to Pylons/SQLAlchemy. Since upgrade to
0.3.4, I now get 4 errors on code that used to work with 0.3.3. I have
looked in the tracker and in this group but they do not seem to have
been reported yet, so here are the tracebacks. I am newbie on this
group so pl
Hi Paul,
Yes, I had found this about the datatype size by way of breaking into
the relevant code and setting the parameter length manually. This made
the query work but just unveiled other problems.
I too made no further efforts to get it work as pymssql works fine for
my purposes - although ser
Arnar,
I agree that is an adodbapi problem; I have seen this as well. It is
because adodbapi isn't setting the length of the parameter, so ADO is
defaulting to 1 - hence you only getting "O". I do have an idea how to
fix this, however I'm choosing not to for now. adodbapi just isn't
maintaine
ive committed the patch for synonym reflection in r2335, corresponding
to ticket 379...so a table linked by a synonym should now be
reflectable.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
T
Yes, I imagined something like that. I only posted to avert users from
norcebo effect that they might encounter reading this thread.
On Feb 17, 5:16 pm, Michael Bayer <[EMAIL PROTECTED]> wrote:
> if you didnt have to change SA's "logging" module, its possibly
> because py2.5 has better support fo
if you didnt have to change SA's "logging" module, its possibly
because py2.5 has better support for absolute module imports (or
maybe py2exe does).
On Feb 17, 2007, at 11:58 AM, Ali wrote:
>
> Hi,
>
> I might be going insane, but I am successfully using Sqlalchemy
> (0.3.4, Python2.5, py2ex
On Feb 17, 2007, at 6:55 AM, [EMAIL PROTECTED] wrote:
> But I was a bit disappointed when I found that I couldn't access a
> view as a table (using autoload). The application I currently work on
> is based on Oracle and uses views heavily. The good news is that it
> uses a lot of materialized vi
bug, fixed in r2334. not much of a workaround other than trying to
append the constraints manually (for which there isnt really a public
API).
On Feb 17, 2007, at 4:47 AM, Andreas Jung wrote:
> I have a Table instance with a UniqueConstraint. SA fails while
> creating
> a copy of
Hi,
>But I was a bit disappointed when I found that I couldn't access a
>view as a table (using autoload). The application I currently work on
>is based on Oracle and uses views heavily. The good news is that it
>
>
Views work ok for me using MSSQL, although I haven't tried autoload. My
gut fe
Hi,
I might be going insane, but I am successfully using Sqlalchemy
(0.3.4, Python2.5, py2exe 0.6.6) with py2exe without any problems.
I did (as suggested) an "easy_install --always-unzip" to prevent
having an egg, and then included 'packages': 'sqlalchemy' in the
options dict for py2exe.
e.g.
On Feb 17, 2007, at 2:55 AM, jose wrote:
> My definition was:
>
> assign_mapper(context, Attivita, tbl['attivita'], properties = dict
> (specie = relation(Specie, backref='attivita'))
>
> now it is:
>
> assign_mapper(context, Attivita, tbl['attivita'], properties =
> dict(specie = relation(Speci
Views as normal tables work with mysql.
> view as a table (using autoload). The application I currently work on
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email
Michael Bayer ha scritto:
> pretty much. we use bind parameters for everything literal. also we
> dont spit out the DB passwords in error messages. not sure if you
> turn on connection pool logging if some of the DBAPIs put the
> passwords in the __repr__ for their connection objects, thats
> s
I've just downloaded and played with SQLAlchemy, and I must say I
quite like it. I've always enjoyed using plain SQL, and SA lets me do
that while integrating nicely with Python. Great work!
But I was a bit disappointed when I found that I couldn't access a
view as a table (using autoload). The a
I have a Table instance with a UniqueConstraint. SA fails while creating
a copy of the table using table.tometadata(). Is there a workaround?
Andreas
-
Traceback (most recent call last):
File "schema.py", line 77, in ?
M.createTables()
File "schema.py", line 35, in createTable
15 matches
Mail list logo
