we have a long-standing ticket to support database comments but none of that is
implemented right now.
Bao Niu wrote:
> I wonder if there is a method/inspector in SQLAlchemy that allows me to
> set/access column comments residing in sqlite database schema? I know I can
> access it through PR
YouTube videos of
U.S. Congress money laundering hearing
of
Saudi Billionaire " Maan Al sanea"
with *bank of America*
and The owner of Saad Hospital and Schools
in the Eastern Province in *Saudi Arabia*
and the Chairman of the Board of Directors of Awal Bank in *Bahrain*
Wit
I wonder if there is a method/inspector in SQLAlchemy that allows me to
set/access column comments residing in sqlite database schema? I know I can
access it through PRAGMA table_info, I just wonder if I can do this
directly in SA? I've searched the documentation but didn't find anything
relate
Ed Rahn wrote:
>
> On 01/10/2015 01:51 PM, Jonathan Vanasco wrote:
>> It's hard to tell what could cause the issue:
>>
>> How many horses are there?
> 463827
>> What is going on in that other function?
> Just a regex search, two selects and a commit
>> Are there foreign key checks involved wi
Lycovian wrote:
> TL;DR:
> I'm trying to debug what is actually being sent to the pyodbc.connect
> function on connect in a custom dialect. I need to see the connection string
> that is being sent to the pyodbc.connect function *right* before it is sent
> but it has been difficult for me to
On 01/10/2015 01:51 PM, Jonathan Vanasco wrote:
It's hard to tell what could cause the issue:
How many horses are there?
463827
What is going on in that other function?
Just a regex search, two selects and a commit
Are there foreign key checks involved with the commit?
Yep
When I set up
TL;DR:
I'm trying to debug what is actually being sent to the pyodbc.connect
function on connect in a custom dialect. I need to see the connection
string that is being sent to the pyodbc.connect function *right* before it
is sent but it has been difficult for me to unravel the layers of
indire
Thanks! That is exactly what I needed. I can now trace through the
enclosing SQLA calls now.
On Friday, January 9, 2015 at 5:40:58 PM UTC-8, Lycovian wrote:
>
> I'm attempting to debug a custom dialect using pudb. Once my custom
> create_connect_args function returns to strategies.py pudb st
>
> yeah, holding onto the all() result is pretty key :)
>
A hacky trick I use on web projects is to have a "sqlalchemy_persistance"
array on the `request` object. i just append everything I load that "might
be needed again" onto that.
--
You received this message because you are subscrib
It's hard to tell what could cause the issue:
How many horses are there?
What is going on in that other function?
Are there foreign key checks involved with the commit?
If you want to break a huge batch into smaller commits, there is the
`Windowed Range Query` strategy
-- https://bitbucket.org/
Would this work for you:
- download the source from github
- in your environment, `python setup.py develop`
the reason why i suggest using the github source, is that you can insert
whatever breakpoints/traces you need in a new branch, and quickly see what
is modified with a git command or switc
11 matches
Mail list logo
