Also based on certain conditions I would not like to execute the
insert at all...
So is there a way to just return from execute method of MyProxy class
with out actually executing the insert statement?
--
You received this message because you are subscribed to the Google Groups
sqlalchemy
Hi
I am using sqlalchemy 0.6.6 with sybase dialect, I found that strings
larger than 16K are truncated to 16K even for TEXT column. Debug trace
shows that string contents are correct in SQL statement but after
execution (session.commit()) they are truncated to 16KB.
It is a known issue or I
Hello world!
I am currently trying to transform my code from classic (schema defined
in an extra python module) to declarative. As intermediate step I am
moving the table definitions to the class implementations.
What I am running into is sketched in the following example. In reality,
I have
likely a FreeTDS configuration issue, I'd check on that end (in particular
text size). Certainly nothing within SQLAlchemy.
On Apr 28, 2011, at 5:13 AM, Joel Zhou wrote:
Hi
I am using sqlalchemy 0.6.6 with sybase dialect, I found that strings
larger than 16K are truncated to 16K even
On Apr 28, 2011, at 12:45 AM, Sirko Schroeder wrote:
I have a problem with oracle column names that are oracle reserved
words (http://download.oracle.com/docs/cd/B19306_01/em.102/b40103/
app_oracle_reserved_words.htm). I read through the archive and found:
funny, that's absolutely a bug and it works in declarative because the same fix
you have there was already applied some time ago within declarative. this is
#2153 targeted at 0.6.8 so I will get to it when i make a pass through a set of
small 0.6.8 issues later in the week.
On Apr 28, 2011,
Hi all,
I'm new to sqlalchemy. I've always tended to write SQL directly (exposing
SQL results to python code using simple db interface libraries) and I'm
still trying to wrap my head around the purpose, style, and proper idioms of
ORM technology. This is mostly a cultural question I guess.
On Apr 28, 2011, at 2:24 PM, Jennifer Rodriguez-Mueller wrote:
Here is the core SQL (lots of distracting content trimmed):
SELECT s.*, a.*
FROM aliquot_table a
JOIN ( -- Biologically (p)lausible aliquot/specimen type logic
SELECT 3 AS a_type, 12 AS s_type UNION --
Thank you Michael, that makes things *much* clearer!
I had been thinking of sqlalchemy as a database manipulation system that
took inspiration from my source code, rather than thinking of a library that
uses compiled but introspectively accessible bytecode with variable names
preserved, so that
On Apr 29, 12:30 am, Michael Bayer mike...@zzzcomputing.com wrote:
The next issue is, this was a known issue that is fixed in both 0.6.7 and 0.7
(ticket 2100, unfortunately I had to go through creating a whole test just
now to figure that out, but there you go). And, if you name your
thanks Michael. It turns out that pyodbc was compiled with different
version of unixODBC, so there was a mismatch in the libraries used.
After recompiling pyodbc against the intented version of unixODBC,
things seem to work fine.
TPN
On Wed, Apr 27, 2011 at 5:51 PM, Michael Bayer
11 matches
Mail list logo
