UTC-7, Mike Bayer wrote:
>
> On Wed, Sep 13, 2017 at 6:13 PM, dirk.biesinger
> <dirk.bi...@gmail.com > wrote:
> > "oh that is very interesting." he says and then it's getting eerily
> quiet.
> > I guess Mike and Dilly are somewhere in the depth
"oh that is very interesting." he says and then it's getting eerily quiet.
I guess Mike and Dilly are somewhere in the depth of code and docs...
On Wednesday, September 13, 2017 at 2:05:22 PM UTC-7, Mike Bayer wrote:
>
> On Wed, Sep 13, 2017 at 4:29 PM, dirk.biesinger
> &l
Sep 13, 2017 at 3:58 PM, dirk.biesinger
> <dirk.bi...@gmail.com > wrote:
> > using
> >
> > connection = pyodbc.connect()
> > connection.autocommit = 0
> > cursor = connection.cursor()
> > cursor.execute([proper sql statement that references a ta
pyodbc connection works, this is
confirmed.
On Wednesday, September 13, 2017 at 12:49:33 PM UTC-7, Mike Bayer wrote:
>
> On Wed, Sep 13, 2017 at 3:27 PM, dirk.biesinger
> <dirk.bi...@gmail.com > wrote:
> > I have the 'patched' pyodbc.py file active.
> > Execu
I have the 'patched' pyodbc.py file active.
Executing your code snippet does NOT produce an error or any output for
that matter.
On Wednesday, September 13, 2017 at 12:22:30 PM UTC-7, Mike Bayer wrote:
>
> On Wed, Sep 13, 2017 at 3:14 PM, dirk.biesinger
> <dirk.bi...@gmail
u for your help.
Best,
DB
On Wednesday, September 13, 2017 at 11:45:15 AM UTC-7, Mike Bayer wrote:
>
> On Wed, Sep 13, 2017 at 2:41 PM, dirk.biesinger
> <dirk.bi...@gmail.com > wrote:
> > I don't get why the table is getting created in the first place. A table
> >
have most of them and you can make new ones too.
>
> On Wed, Sep 13, 2017 at 1:07 PM, dirk.biesinger
> <dirk.bi...@gmail.com > wrote:
> > Mike,
> >
> > here's the error stack (I had to mask some details):
> > The columns (dataformats) in the create tab
:
'\nCREATE TABLE [dbo.MSODS_DSI] (\n\t[a] DATETIME NULL, \n\t[b]
VARCHAR(max) NULL, \n\t[c] VARCHAR(max) NULL, \n\t[d] VARCHAR(max) NULL,
\n\t[e] VARCHAR(max) NULL, \n\t[f] FLOAT(53) NULL, \n\t[g] FLOAT(53)
NULL\n)\n\n']
On Monday, September 11, 2017 at 3:34:47 PM UTC-7, dirk.biesinger wrote:
>
And I just verified: version 1.1.13 is installed, and loaded for sure just
checked via sqlalchemy.__version__
Just to be sure.
On Tuesday, September 12, 2017 at 10:14:03 AM UTC-7, dirk.biesinger wrote:
>
> Mike,
>
> I'll post two stacks:
> the first one is just calling the
older version of the code somehow.
>
> Can you please provide the complete stack trace? no need for it to
> be an attachment.
>
> >
> > Unfortunately I can't give you permission to our database instance
> (customer
> > policies) but am able to cooperate as much as poss
re-attaching the files
On Monday, September 11, 2017 at 3:34:47 PM UTC-7, dirk.biesinger wrote:
>
> I am encountering errors when trying to use the pd.to_sql function to
> write a dataframe to MS SQL Data Warehouse.
> The connection works when NOT using sqlalchemy engines.
I am encountering errors when trying to use the pd.to_sql function to write
a dataframe to MS SQL Data Warehouse.
The connection works when NOT using sqlalchemy engines.
I can read dataframes as well as row-by-row via select statements when I
use pyodbc connections
I can write data via insert
12 matches
Mail list logo
