Is there some other way I can execute a query using a list as a bound parameter?
res = db.db_con.text('SELECT module_extra_key_name FROM module_extra_keys
WHERE module_id IN :module_ids').execute({'module_ids': [1,2]})
The above is giving me an You cannot execute SELECT statements in
Starting with r2598, I'm seeing some failures with how I'm using the
association proxy. I've modified the
examples/association/proxied_association.py file which duplicates the
problem.
It is possible that I'm not suppose to remove associations like I am.
But it did work before (in 0.3.7 and
ticket #597 for this.
On Jun 12, 2:22 am, Paul Kippes [EMAIL PROTECTED]
wrote:
Starting with r2598, I'm seeing some failures with how I'm using the
association proxy. I've modified the
examples/association/proxied_association.py file which duplicates the
problem.
It is possible that I'm
These sound like a good progression of the library.
Would there be a way to turn on warnings if one were to use a
deprecated interface? Or if the programmer wants to be even more
strict, raise an exception? This wouldn't be the default, but rather
an available option.
First, let me admit that I'm not an expert at Python.
I'm trying to test the newer versions of SQLAlchemy before I install
it on my server. According to
http://docs.python.org/inst/search-path.html, the PYTHONPATH should
add paths to the beginning of sys.path. The docs at
I found the thread about PYTHONPATH--interesting.
It does seem that eggs are not only preventing the expected behavior,
but they are also preventing the documented behavior.
However, I don't think that using eggs is the best choice for a fast
progressing library like SQLAlchemy--especially with
I have a query that started to fail with r2620. Here is a portion on
the code and the exception that was thrown. I've tested against the
most current revision and that also fails. Is this something I'm
doing wrong or a real bug? --Thanks, Paul
in_sql =
Michael, I certainly understand why this hasn't been added. With some
databases like sqlite, a case sensitive search isn't even possible.
This is much more complicated that I would have imagined.
--~--~-~--~~~---~--~~
You received this message because you are
Currently sqlalchemy doesn't support a query like this:
SELECT my_name FROM names WHERE my_name LIKE 'larry\_%' ESCAPE '\'
Could such a feature be added to be used in a similar way to the LIMIT
feature? It looks like a simple enough patch for me to do. But I
don't have knowledge of the array
it going to do to that
\ ?) ? what DB is this ? can this same functionality be achieved via
bind parameters ?
On Apr 4, 2007, at 10:30 AM, Paul Kippes wrote:
Currently sqlalchemy doesn't support a query like this:
SELECT my_name FROM names WHERE my_name LIKE 'larry\_%' ESCAPE '\'
Could
. then an explicit
visit_like() would be added to ansisql.py to process the construct as
well as the optional escapes keyword argument.
otherwise, please add a new enhancement ticket to trac (via the
bugs link on the site) and we'll get it in the queue.
On Apr 4, 2007, at 12:34 PM, Paul Kippes
In my version of sqlalchemy I didn't find any ability for ILIKE. Is
this supported?
If a patch is needed, would a new operator ilike be okay?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To
I'm finally getting a bit more at ease with the more complex aspects
of SQLAlchemy. But yet again, I still need some help. Now I'm trying
to change the ordering from my mapper's default. My Signal mapper was
defined to order by the signal_name (using an AssociationProxy). That
has been
I'm trying to create a subselect that has a where condition using an
identically named column as the outer select. I'm not able to figure
out how to tell SQLAlchemy that I need two parameters--one for each
query. Here is what my SQL would look like if I wrote it by hand:
SELECT signals.*
14 matches
Mail list logo
