From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 13 11:13:32 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 13 11:13:32 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 11:13:32 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 13 11:13:32 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 13 11:13:32 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 11:13:32 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 13 11:13:32 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 13 15:14:02 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 13 15:14:02 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 15:14:02 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 13 15:14:02 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 13 15:14:02 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 15:14:02 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 13 15:14:02 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 13 15:14:02 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 13 15:14:02 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 15:14:02 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 13 15:14:02 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 15:14:02 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 13 15:14:02 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 13 15:21:27 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 13 15:21:27 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 15:21:27 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 13 15:21:27 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 13 15:21:27 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 15:21:27 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 13 15:21:27 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 13 15:21:27 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 13 15:21:27 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 15:21:27 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 13 15:21:27 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 15:21:28 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 13 15:21:28 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 13 16:00:58 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 13 16:00:58 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 16:00:58 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 13 16:00:58 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 13 16:00:58 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 16:00:58 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 13 16:00:58 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 13 16:00:58 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 13 16:00:58 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 16:00:58 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 13 16:00:58 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 16:00:58 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 13 16:00:58 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 13 20:02:00 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 13 20:02:00 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 20:02:00 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 13 20:02:00 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 13 20:02:00 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 20:02:00 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 13 20:02:00 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 13 20:02:00 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 13 20:02:00 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 20:02:00 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 13 20:02:00 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 13 20:02:00 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 13 20:02:00 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 14 08:02:33 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 14 08:02:34 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 08:02:34 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 14 08:02:34 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 14 08:02:34 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 08:02:34 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 14 08:02:34 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 14 08:02:34 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 14 08:02:34 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 08:02:34 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 14 08:02:34 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 08:02:34 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 14 08:02:34 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 14 12:00:57 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 14 12:00:57 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 12:00:57 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 14 12:00:57 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 14 12:00:57 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 12:00:57 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 14 12:00:57 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 14 12:00:57 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 14 12:00:57 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 12:00:57 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 14 12:00:57 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 12:00:57 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 14 12:00:57 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 14 16:00:54 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 14 16:00:54 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 16:00:54 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 14 16:00:54 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 14 16:00:54 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 16:00:54 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 14 16:00:54 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 14 16:00:54 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 14 16:00:54 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 16:00:54 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 14 16:00:54 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 16:00:54 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 14 16:00:54 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 14 20:00:54 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 14 20:00:54 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 20:00:54 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 14 20:00:54 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 14 20:00:54 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 20:00:54 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 14 20:00:54 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 14 20:00:54 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 14 20:00:54 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 20:00:54 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 14 20:00:54 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 14 20:00:54 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 14 20:00:54 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 15 08:02:22 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 15 08:02:22 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 08:02:22 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 15 08:02:22 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 15 08:02:22 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 08:02:22 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 15 08:02:22 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 15 08:02:22 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 15 08:02:22 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 08:02:22 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 15 08:02:22 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 08:02:22 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 15 08:02:22 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 15 12:01:02 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 15 12:01:02 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 12:01:02 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 15 12:01:02 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 15 12:01:02 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 12:01:02 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 15 12:01:02 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 15 12:01:02 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 15 12:01:02 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 12:01:02 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 15 12:01:02 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 12:01:02 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 15 12:01:02 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 15 16:00:54 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 15 16:00:54 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 16:00:54 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 15 16:00:54 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 15 16:00:54 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 16:00:54 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 15 16:00:54 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 15 16:00:54 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 15 16:00:54 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 16:00:54 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 15 16:00:54 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 16:00:54 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 15 16:00:54 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 15 20:00:53 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 15 20:00:53 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 20:00:53 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 15 20:00:53 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 15 20:00:53 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 20:00:53 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 15 20:00:53 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 15 20:00:53 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 15 20:00:53 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 20:00:53 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 15 20:00:53 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 15 20:00:53 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 15 20:00:53 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 16 08:02:46 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 16 08:02:46 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 08:02:46 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 16 08:02:46 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 16 08:02:46 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 08:02:46 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 16 08:02:46 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 16 08:02:46 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 16 08:02:46 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 08:02:46 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 16 08:02:46 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 08:02:46 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 16 08:02:46 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 16 12:00:59 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 16 12:00:59 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 12:00:59 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 16 12:00:59 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 16 12:00:59 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 12:00:59 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 16 12:00:59 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 16 12:00:59 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 16 12:00:59 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 12:00:59 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 16 12:00:59 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 12:00:59 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 16 12:00:59 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 16 16:00:57 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 16 16:00:58 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 16:00:58 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 16 16:00:58 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 16 16:00:58 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 16:00:58 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 16 16:00:58 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 16 16:00:58 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 16 16:00:58 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 16:00:58 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 16 16:00:58 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 16:00:58 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 16 16:00:58 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 16 20:00:55 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 16 20:00:55 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 20:00:55 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 16 20:00:55 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 16 20:00:55 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 20:00:55 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 16 20:00:55 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 16 20:00:55 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 16 20:00:55 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 20:00:55 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 16 20:00:55 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 16 20:00:55 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 16 20:00:55 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 17 08:02:49 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 17 08:02:49 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 08:02:49 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 17 08:02:49 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 17 08:02:50 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 08:02:50 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 17 08:02:50 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 17 08:02:50 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 17 08:02:50 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 08:02:50 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 17 08:02:50 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 08:02:50 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 17 08:02:50 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 17 12:01:15 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 17 12:01:19 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 12:01:19 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 17 12:01:19 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 17 12:01:19 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 12:01:19 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 17 12:01:19 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 17 12:01:19 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 17 12:01:19 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 12:01:20 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 17 12:01:20 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 12:01:20 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 17 12:01:20 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 17 16:01:01 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 17 16:01:01 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 16:01:01 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 17 16:01:02 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 17 16:01:02 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 16:01:02 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 17 16:01:02 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 17 16:01:02 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 17 16:01:02 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 16:01:02 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 17 16:01:02 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 16:01:02 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 17 16:01:02 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 17 20:01:01 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 17 20:01:01 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 20:01:01 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 17 20:01:01 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 17 20:01:01 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 20:01:01 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 17 20:01:01 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 17 20:01:01 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 17 20:01:01 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 20:01:01 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 17 20:01:01 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 17 20:01:01 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 17 20:01:01 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Jan 18 08:04:35 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Jan 18 08:04:36 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 08:04:36 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Jan 18 08:04:36 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Jan 18 08:04:36 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 08:04:36 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Jan 18 08:04:36 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Jan 18 08:04:36 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Jan 18 08:04:36 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 08:04:36 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Jan 18 08:04:36 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 08:04:36 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Jan 18 08:04:36 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Jan 18 12:01:16 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Jan 18 12:01:17 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 12:01:17 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Jan 18 12:01:17 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Jan 18 12:01:17 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 12:01:17 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Jan 18 12:01:17 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Jan 18 12:01:17 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Jan 18 12:01:17 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 12:01:17 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Jan 18 12:01:17 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 12:01:17 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Jan 18 12:01:17 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Jan 18 16:01:50 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Jan 18 16:01:50 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 16:01:50 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Jan 18 16:01:50 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Jan 18 16:01:51 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 16:01:51 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Jan 18 16:01:51 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Jan 18 16:01:51 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Jan 18 16:01:51 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 16:01:51 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Jan 18 16:01:51 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 16:01:51 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Jan 18 16:01:51 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Jan 18 20:01:08 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Jan 18 20:01:08 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 20:01:08 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Jan 18 20:01:08 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Jan 18 20:01:08 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 20:01:08 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Jan 18 20:01:08 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Jan 18 20:01:08 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Jan 18 20:01:08 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 20:01:08 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Jan 18 20:01:08 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 18 20:01:08 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Jan 18 20:01:08 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Jan 19 08:04:58 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Jan 19 08:04:58 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 08:04:58 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Jan 19 08:04:58 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Jan 19 08:04:58 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 08:04:58 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Jan 19 08:04:58 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Jan 19 08:04:58 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Jan 19 08:04:58 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 08:04:58 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Jan 19 08:04:58 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 08:04:58 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Jan 19 08:04:58 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Jan 19 12:01:13 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Jan 19 12:01:13 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 12:01:13 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Jan 19 12:01:13 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Jan 19 12:01:13 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 12:01:13 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Jan 19 12:01:13 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Jan 19 12:01:13 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Jan 19 12:01:13 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 12:01:13 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Jan 19 12:01:13 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 12:01:13 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Jan 19 12:01:13 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Jan 19 16:03:45 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Jan 19 16:03:45 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 16:03:45 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Jan 19 16:03:46 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Jan 19 16:03:46 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 16:03:46 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Jan 19 16:03:46 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Jan 19 16:03:46 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Jan 19 16:03:46 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 16:03:46 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Jan 19 16:03:46 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 16:03:46 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Jan 19 16:03:46 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Jan 19 20:00:58 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Jan 19 20:00:58 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 20:00:58 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Jan 19 20:00:58 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Jan 19 20:00:58 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 20:00:58 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Jan 19 20:00:58 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Jan 19 20:00:58 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Jan 19 20:00:58 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 20:00:58 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Jan 19 20:00:58 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 19 20:00:58 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Jan 19 20:00:59 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 20 08:07:59 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 20 08:07:59 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 08:07:59 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 20 08:07:59 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 20 08:07:59 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 08:07:59 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 20 08:07:59 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 20 08:07:59 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 20 08:08:00 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 08:08:00 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 20 08:08:00 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 08:08:00 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 20 08:08:00 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 20 12:02:32 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 20 12:02:32 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 12:02:32 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 20 12:02:32 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 20 12:02:32 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 12:02:32 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 20 12:02:32 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 20 12:02:32 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 20 12:02:32 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 12:02:32 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 20 12:02:32 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 12:02:32 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 20 12:02:33 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 20 16:01:03 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 20 16:01:03 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 16:01:03 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 20 16:01:03 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 20 16:01:03 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 16:01:03 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 20 16:01:03 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 20 16:01:03 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 20 16:01:03 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 16:01:03 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 20 16:01:03 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 16:01:03 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 20 16:01:03 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 20 20:01:00 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 20 20:01:00 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 20:01:00 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 20 20:01:00 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 20 20:01:00 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 20:01:00 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 20 20:01:00 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 20 20:01:00 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 20 20:01:00 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 20:01:00 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 20 20:01:00 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 20 20:01:00 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 20 20:01:00 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 21 08:04:17 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 21 08:04:17 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 08:04:17 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 21 08:04:17 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 21 08:04:17 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 08:04:17 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 21 08:04:17 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 21 08:04:17 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 21 08:04:17 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 08:04:17 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 21 08:04:17 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 08:04:17 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 21 08:04:17 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 21 12:01:14 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 21 12:01:14 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 12:01:14 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 21 12:01:14 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 21 12:01:14 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 12:01:14 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 21 12:01:14 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 21 12:01:14 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 21 12:01:14 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 12:01:14 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 21 12:01:14 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 12:01:14 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 21 12:01:14 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 21 16:01:02 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 21 16:01:02 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 16:01:02 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 21 16:01:02 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 21 16:01:02 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 16:01:02 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 21 16:01:02 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 21 16:01:02 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 21 16:01:02 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 16:01:02 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 21 16:01:02 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 16:01:02 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 21 16:01:02 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 21 20:00:59 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 21 20:01:00 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 20:01:00 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 21 20:01:00 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 21 20:01:00 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 20:01:00 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 21 20:01:00 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 21 20:01:00 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 21 20:01:00 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 20:01:00 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 21 20:01:00 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 21 20:01:00 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 21 20:01:00 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 22 08:03:08 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 22 08:03:08 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 08:03:08 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 22 08:03:08 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 22 08:03:08 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 08:03:08 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 22 08:03:09 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 22 08:03:09 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 22 08:03:09 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 08:03:09 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 22 08:03:09 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 08:03:09 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 22 08:03:09 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 22 12:01:03 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 22 12:01:03 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 12:01:03 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 22 12:01:03 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 22 12:01:03 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 12:01:03 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 22 12:01:03 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 22 12:01:03 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 22 12:01:03 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 12:01:03 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 22 12:01:03 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 12:01:03 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 22 12:01:03 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 22 16:01:40 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 22 16:01:40 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 16:01:40 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 22 16:01:40 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 22 16:01:40 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 16:01:40 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 22 16:01:40 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 22 16:01:40 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 22 16:01:41 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 16:01:41 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 22 16:01:41 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 16:01:41 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 22 16:01:41 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 22 20:01:35 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 22 20:01:35 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 20:01:35 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 22 20:01:36 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 22 20:01:36 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 20:01:36 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 22 20:01:36 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 22 20:01:36 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 22 20:01:36 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 20:01:36 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 22 20:01:36 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 22 20:01:36 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 22 20:01:36 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 23 08:03:04 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 23 08:03:04 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 08:03:04 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 23 08:03:04 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 23 08:03:04 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 08:03:04 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 23 08:03:04 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 23 08:03:04 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 23 08:03:04 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 08:03:04 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 23 08:03:04 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 08:03:04 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 23 08:03:04 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 23 12:01:09 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 23 12:01:09 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 12:01:09 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 23 12:01:09 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 23 12:01:09 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 12:01:09 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 23 12:01:09 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 23 12:01:09 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 23 12:01:09 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 12:01:09 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 23 12:01:09 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 12:01:09 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 23 12:01:09 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 23 16:02:16 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 23 16:02:16 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 16:02:16 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 23 16:02:16 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 23 16:02:17 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 16:02:17 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 23 16:02:17 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 23 16:02:17 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 23 16:02:17 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 16:02:17 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 23 16:02:17 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 16:02:17 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 23 16:02:17 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 23 20:01:04 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 23 20:01:04 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 20:01:04 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 23 20:01:04 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 23 20:01:04 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 20:01:04 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 23 20:01:04 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 23 20:01:04 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 23 20:01:04 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 20:01:04 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 23 20:01:04 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 23 20:01:04 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 23 20:01:04 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 24 08:03:35 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 24 08:03:35 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 08:03:35 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 24 08:03:35 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 24 08:03:35 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 08:03:35 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 24 08:03:35 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 24 08:03:35 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 24 08:03:35 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 08:03:35 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 24 08:03:35 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 08:03:35 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 24 08:03:35 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 24 12:03:47 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 24 12:03:48 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 12:03:48 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 24 12:03:48 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 24 12:03:48 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 12:03:48 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 24 12:03:48 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 24 12:03:48 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 24 12:03:49 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 12:03:49 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 24 12:03:49 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 12:03:49 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 24 12:03:49 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 24 16:01:44 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 24 16:01:44 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 16:01:44 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 24 16:01:44 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 24 16:01:44 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 16:01:44 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 24 16:01:44 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 24 16:01:45 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 24 16:01:45 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 16:01:45 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 24 16:01:45 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 16:01:45 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 24 16:01:45 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 24 20:02:11 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 24 20:02:11 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 20:02:11 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 24 20:02:11 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 24 20:02:12 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 20:02:12 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 24 20:02:12 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 24 20:02:12 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 24 20:02:12 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 20:02:12 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 24 20:02:12 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 24 20:02:12 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 24 20:02:12 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Jan 25 08:02:29 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Jan 25 08:02:29 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 08:02:30 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Jan 25 08:02:30 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Jan 25 08:02:30 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 08:02:30 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Jan 25 08:02:30 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Jan 25 08:02:30 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Jan 25 08:02:30 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 08:02:30 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Jan 25 08:02:30 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 08:02:30 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Jan 25 08:02:30 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Jan 25 12:01:21 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Jan 25 12:01:21 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 12:01:21 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Jan 25 12:01:21 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Jan 25 12:01:21 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 12:01:21 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Jan 25 12:01:21 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Jan 25 12:01:21 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Jan 25 12:01:21 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 12:01:21 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Jan 25 12:01:21 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 12:01:21 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Jan 25 12:01:21 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Jan 25 16:01:16 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Jan 25 16:01:16 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 16:01:16 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Jan 25 16:01:16 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Jan 25 16:01:16 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 16:01:16 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Jan 25 16:01:16 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Jan 25 16:01:16 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Jan 25 16:01:16 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 16:01:16 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Jan 25 16:01:16 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 16:01:16 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Jan 25 16:01:16 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Jan 25 20:01:08 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Jan 25 20:01:08 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 20:01:08 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Jan 25 20:01:08 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Jan 25 20:01:08 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 20:01:08 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Jan 25 20:01:08 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Jan 25 20:01:08 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Jan 25 20:01:08 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 20:01:09 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Jan 25 20:01:09 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Jan 25 20:01:09 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Jan 25 20:01:09 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Jan 26 08:06:54 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Jan 26 08:06:55 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 08:06:55 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Jan 26 08:06:55 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Jan 26 08:06:55 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 08:06:55 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Jan 26 08:06:55 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Jan 26 08:06:55 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Jan 26 08:06:55 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 08:06:55 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Jan 26 08:06:55 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 08:06:55 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Jan 26 08:06:55 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Jan 26 12:01:23 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Jan 26 12:01:23 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 12:01:23 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Jan 26 12:01:23 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Jan 26 12:01:23 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 12:01:23 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Jan 26 12:01:23 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Jan 26 12:01:23 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Jan 26 12:01:23 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 12:01:23 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Jan 26 12:01:23 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 12:01:23 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Jan 26 12:01:23 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Jan 26 16:01:05 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Jan 26 16:01:06 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 16:01:06 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Jan 26 16:01:06 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Jan 26 16:01:06 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 16:01:06 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Jan 26 16:01:06 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Jan 26 16:01:06 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Jan 26 16:01:06 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 16:01:06 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Jan 26 16:01:06 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 16:01:06 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Jan 26 16:01:06 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Jan 26 20:00:57 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Jan 26 20:00:57 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 20:00:57 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Jan 26 20:00:57 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Jan 26 20:00:57 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 20:00:57 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Jan 26 20:00:57 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Jan 26 20:00:57 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Jan 26 20:00:57 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 20:00:57 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Jan 26 20:00:57 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 26 20:00:57 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Jan 26 20:00:57 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 27 08:07:51 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 27 08:07:52 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 08:07:52 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 27 08:07:52 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 27 08:07:52 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 08:07:52 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 27 08:07:52 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 27 08:07:52 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 27 08:07:52 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 08:07:52 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 27 08:07:52 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 08:07:52 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 27 08:07:53 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 27 12:02:30 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 27 12:02:30 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 12:02:30 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 27 12:02:30 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 27 12:02:30 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 12:02:30 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 27 12:02:30 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 27 12:02:30 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 27 12:02:30 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 12:02:30 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 27 12:02:30 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 12:02:30 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 27 12:02:30 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 27 16:01:20 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 27 16:01:20 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 16:01:21 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 27 16:01:21 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 27 16:01:21 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 16:01:21 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 27 16:01:21 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 27 16:01:21 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 27 16:01:21 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 16:01:21 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 27 16:01:21 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 16:01:21 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 27 16:01:21 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 27 20:01:12 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 27 20:01:12 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 20:01:12 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 27 20:01:12 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 27 20:01:12 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 20:01:12 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Jan 27 20:01:12 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 27 20:01:12 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 27 20:01:12 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 20:01:12 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 27 20:01:12 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Jan 27 20:01:12 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Jan 27 20:01:12 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 28 08:06:31 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 28 08:06:31 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 08:06:31 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 28 08:06:31 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 28 08:06:32 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 08:06:32 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 28 08:06:32 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 28 08:06:32 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 28 08:06:32 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 08:06:32 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 28 08:06:32 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 08:06:32 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 28 08:06:32 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 28 12:02:08 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 28 12:02:08 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 12:02:08 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 28 12:02:08 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 28 12:02:08 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 12:02:08 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 28 12:02:08 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 28 12:02:08 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 28 12:02:08 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 12:02:08 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 28 12:02:08 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 12:02:08 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 28 12:02:08 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 28 16:01:07 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 28 16:01:07 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 16:01:07 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 28 16:01:07 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 28 16:01:08 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 16:01:08 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 28 16:01:08 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 28 16:01:08 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 28 16:01:08 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 16:01:08 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 28 16:01:08 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 16:01:08 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 28 16:01:08 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 28 20:01:07 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 28 20:01:07 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 20:01:07 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 28 20:01:07 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 28 20:01:07 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 20:01:07 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Jan 28 20:01:07 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 28 20:01:07 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 28 20:01:07 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 20:01:07 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 28 20:01:07 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Jan 28 20:01:07 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Jan 28 20:01:07 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 29 08:07:57 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 29 08:07:57 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 08:07:57 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 29 08:07:57 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 29 08:07:57 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 08:07:57 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 29 08:07:57 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 29 08:07:57 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 29 08:07:57 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 08:07:57 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 29 08:07:57 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 08:07:57 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 29 08:07:57 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 29 12:01:18 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 29 12:01:18 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 12:01:18 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 29 12:01:18 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 29 12:01:18 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 12:01:18 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 29 12:01:18 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 29 12:01:18 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 29 12:01:18 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 12:01:18 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 29 12:01:18 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 12:01:18 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 29 12:01:18 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 29 16:01:06 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 29 16:01:06 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 16:01:06 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 29 16:01:06 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 29 16:01:06 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 16:01:06 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 29 16:01:06 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 29 16:01:07 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 29 16:01:07 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 16:01:07 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 29 16:01:07 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 16:01:07 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 29 16:01:07 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 29 20:01:09 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 29 20:01:09 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 20:01:09 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 29 20:01:09 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 29 20:01:09 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 20:01:09 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Jan 29 20:01:09 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 29 20:01:09 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 29 20:01:09 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 20:01:09 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 29 20:01:09 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Jan 29 20:01:09 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Jan 29 20:01:09 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 30 08:10:52 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 30 08:10:53 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 08:10:53 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 30 08:10:53 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 30 08:10:53 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 08:10:53 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 30 08:10:53 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 30 08:10:53 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 30 08:10:53 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 08:10:53 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 30 08:10:53 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 08:10:53 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 30 08:10:53 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 30 12:04:32 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 30 12:04:32 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 12:04:32 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 30 12:04:32 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 30 12:04:32 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 12:04:32 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 30 12:04:32 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 30 12:04:32 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 30 12:04:32 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 12:04:32 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 30 12:04:32 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 12:04:32 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 30 12:04:32 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 30 16:04:45 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 30 16:04:45 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 16:04:45 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 30 16:04:45 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 30 16:04:45 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 16:04:45 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 30 16:04:45 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 30 16:04:45 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 30 16:04:45 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 16:04:45 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 30 16:04:45 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 16:04:45 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 30 16:04:45 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 30 20:02:38 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 30 20:02:38 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 20:02:38 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 30 20:02:38 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 30 20:02:38 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 20:02:38 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Jan 30 20:02:38 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 30 20:02:38 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 30 20:02:38 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 20:02:38 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 30 20:02:38 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 30 20:02:38 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Jan 30 20:02:38 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 31 08:08:42 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 31 08:08:42 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 08:08:42 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 31 08:08:42 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 31 08:08:42 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 08:08:42 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 31 08:08:42 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 31 08:08:42 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 31 08:08:43 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 08:08:43 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 31 08:08:43 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 08:08:43 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 31 08:08:43 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 31 12:04:53 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 31 12:04:53 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 12:04:53 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 31 12:04:53 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 31 12:04:53 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 12:04:53 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 31 12:04:53 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 31 12:04:53 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 31 12:04:54 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 12:04:54 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 31 12:04:54 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 12:04:54 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 31 12:04:54 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 31 16:02:47 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 31 16:02:47 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 16:02:47 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 31 16:02:47 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 31 16:02:47 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 16:02:47 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 31 16:02:47 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 31 16:02:47 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 31 16:02:47 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 16:02:47 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 31 16:02:47 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 16:02:47 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 31 16:02:47 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 31 20:01:23 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 31 20:01:23 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 20:01:23 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 31 20:01:23 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 31 20:01:23 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 20:01:23 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Jan 31 20:01:23 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 31 20:01:23 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 31 20:01:23 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 20:01:23 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 31 20:01:23 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Jan 31 20:01:23 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Jan 31 20:01:23 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 1 08:11:00 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 1 08:11:00 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 08:11:01 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 1 08:11:01 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 1 08:11:01 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 08:11:01 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 1 08:11:01 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 1 08:11:01 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 1 08:11:01 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 08:11:01 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 1 08:11:01 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 08:11:01 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 1 08:11:01 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 1 12:03:12 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 1 12:03:12 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 12:03:12 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 1 12:03:12 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 1 12:03:12 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 12:03:12 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 1 12:03:12 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 1 12:03:12 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 1 12:03:12 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 12:03:12 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 1 12:03:12 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 12:03:12 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 1 12:03:12 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 1 16:01:22 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 1 16:01:22 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 16:01:22 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 1 16:01:22 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 1 16:01:22 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 16:01:22 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 1 16:01:22 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 1 16:01:22 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 1 16:01:22 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 16:01:22 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 1 16:01:22 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 16:01:22 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 1 16:01:22 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 1 20:01:16 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 1 20:01:16 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 20:01:16 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 1 20:01:16 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 1 20:01:16 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 20:01:16 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 1 20:01:16 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 1 20:01:16 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 1 20:01:16 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 20:01:16 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 1 20:01:17 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 1 20:01:17 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 1 20:01:17 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Feb 2 08:15:07 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Feb 2 08:15:08 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 08:15:08 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Feb 2 08:15:08 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Feb 2 08:15:08 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 08:15:08 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Feb 2 08:15:08 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Feb 2 08:15:08 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Feb 2 08:15:08 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 08:15:08 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Feb 2 08:15:08 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 08:15:08 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Feb 2 08:15:08 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Feb 2 12:03:21 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Feb 2 12:03:22 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 12:03:22 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Feb 2 12:03:22 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Feb 2 12:03:22 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 12:03:22 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Feb 2 12:03:22 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Feb 2 12:03:22 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Feb 2 12:03:22 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 12:03:22 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Feb 2 12:03:22 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 12:03:22 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Feb 2 12:03:22 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Feb 2 16:01:27 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Feb 2 16:01:27 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 16:01:27 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Feb 2 16:01:27 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Feb 2 16:01:27 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 16:01:27 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Feb 2 16:01:28 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Feb 2 16:01:28 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Feb 2 16:01:28 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 16:01:28 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Feb 2 16:01:28 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 16:01:28 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Feb 2 16:01:28 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Feb 2 20:01:19 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Feb 2 20:01:19 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 20:01:19 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Feb 2 20:01:19 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Feb 2 20:01:19 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 20:01:19 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Feb 2 20:01:19 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Feb 2 20:01:19 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Feb 2 20:01:19 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 20:01:19 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Feb 2 20:01:19 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 2 20:01:19 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Feb 2 20:01:19 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Feb 3 08:14:17 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Feb 3 08:14:18 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 08:14:18 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Feb 3 08:14:18 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Feb 3 08:14:18 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 08:14:18 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Feb 3 08:14:18 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Feb 3 08:14:18 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Feb 3 08:14:18 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 08:14:18 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Feb 3 08:14:18 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 08:14:18 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Feb 3 08:14:19 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Feb 3 12:03:15 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Feb 3 12:03:15 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 12:03:15 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Feb 3 12:03:15 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Feb 3 12:03:15 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 12:03:15 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Feb 3 12:03:15 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Feb 3 12:03:15 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Feb 3 12:03:15 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 12:03:15 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Feb 3 12:03:15 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 12:03:15 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Feb 3 12:03:15 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Feb 3 16:01:19 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Feb 3 16:01:19 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 16:01:19 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Feb 3 16:01:19 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Feb 3 16:01:19 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 16:01:19 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Feb 3 16:01:19 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Feb 3 16:01:19 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Feb 3 16:01:19 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 16:01:19 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Feb 3 16:01:19 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 16:01:19 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Feb 3 16:01:19 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Feb 3 20:01:24 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Feb 3 20:01:24 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 20:01:24 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Feb 3 20:01:24 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Feb 3 20:01:24 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 20:01:24 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Feb 3 20:01:24 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Feb 3 20:01:24 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Feb 3 20:01:24 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 20:01:24 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Feb 3 20:01:24 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 3 20:01:24 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Feb 3 20:01:24 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Feb 4 08:09:44 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Feb 4 08:09:44 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 08:09:45 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Feb 4 08:09:45 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Feb 4 08:09:45 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 08:09:45 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Feb 4 08:09:45 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Feb 4 08:09:45 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Feb 4 08:09:45 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 08:09:45 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Feb 4 08:09:45 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 08:09:45 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Feb 4 08:09:45 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Feb 4 12:03:16 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Feb 4 12:03:17 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 12:03:17 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Feb 4 12:03:17 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Feb 4 12:03:17 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 12:03:17 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Feb 4 12:03:17 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Feb 4 12:03:17 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Feb 4 12:03:17 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 12:03:17 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Feb 4 12:03:17 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 12:03:17 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Feb 4 12:03:17 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Feb 4 16:01:29 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Feb 4 16:01:30 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 16:01:30 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Feb 4 16:01:30 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Feb 4 16:01:31 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 16:01:31 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Feb 4 16:01:31 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Feb 4 16:01:31 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Feb 4 16:01:31 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 16:01:31 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Feb 4 16:01:31 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 16:01:31 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Feb 4 16:01:31 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Feb 4 20:01:21 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Feb 4 20:01:21 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 20:01:22 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Feb 4 20:01:22 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Feb 4 20:01:22 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 20:01:22 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Feb 4 20:01:22 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Feb 4 20:01:22 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Feb 4 20:01:22 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 20:01:22 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Feb 4 20:01:22 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 4 20:01:22 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Feb 4 20:01:22 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Feb 5 08:08:26 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Feb 5 08:08:27 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 08:08:28 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Feb 5 08:08:28 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Feb 5 08:08:28 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 08:08:28 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Feb 5 08:08:28 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Feb 5 08:08:28 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Feb 5 08:08:28 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 08:08:28 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Feb 5 08:08:28 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 08:08:28 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Feb 5 08:08:28 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Feb 5 12:03:15 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Feb 5 12:03:15 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 12:03:15 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Feb 5 12:03:15 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Feb 5 12:03:15 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 12:03:15 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Feb 5 12:03:15 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Feb 5 12:03:15 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Feb 5 12:03:15 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 12:03:15 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Feb 5 12:03:15 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 12:03:15 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Feb 5 12:03:15 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Feb 5 16:01:25 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Feb 5 16:01:25 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 16:01:25 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Feb 5 16:01:25 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Feb 5 16:01:25 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 16:01:25 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Feb 5 16:01:25 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Feb 5 16:01:25 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Feb 5 16:01:25 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 16:01:25 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Feb 5 16:01:25 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 16:01:26 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Feb 5 16:01:26 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Feb 5 20:01:18 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Feb 5 20:01:18 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 20:01:18 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Feb 5 20:01:18 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Feb 5 20:01:18 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 20:01:18 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Feb 5 20:01:18 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Feb 5 20:01:18 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Feb 5 20:01:18 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 20:01:18 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Feb 5 20:01:18 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 5 20:01:18 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Feb 5 20:01:18 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Feb 6 08:17:22 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Feb 6 08:17:24 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 08:17:24 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Feb 6 08:17:25 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Feb 6 08:17:25 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 08:17:26 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Feb 6 08:17:28 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Feb 6 08:17:28 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Feb 6 08:17:29 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 08:17:29 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Feb 6 08:17:29 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 08:17:29 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Feb 6 08:17:30 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Feb 6 12:03:21 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Feb 6 12:03:21 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 12:03:22 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Feb 6 12:03:22 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Feb 6 12:03:22 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 12:03:22 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Feb 6 12:03:22 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Feb 6 12:03:22 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Feb 6 12:03:22 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 12:03:22 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Feb 6 12:03:22 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 12:03:22 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Feb 6 12:03:22 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Feb 6 16:01:23 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Feb 6 16:01:23 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 16:01:23 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Feb 6 16:01:23 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Feb 6 16:01:23 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 16:01:23 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Feb 6 16:01:23 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Feb 6 16:01:23 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Feb 6 16:01:23 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 16:01:23 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Feb 6 16:01:23 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 16:01:23 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Feb 6 16:01:23 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Feb 6 20:01:20 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Feb 6 20:01:20 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 20:01:20 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Feb 6 20:01:20 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Feb 6 20:01:21 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 20:01:21 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Feb 6 20:01:21 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Feb 6 20:01:21 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Feb 6 20:01:21 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 20:01:21 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Feb 6 20:01:21 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 6 20:01:21 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Feb 6 20:01:21 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Feb 7 08:27:53 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Feb 7 08:27:55 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 08:27:55 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Feb 7 08:27:55 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Feb 7 08:27:55 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 08:27:55 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Feb 7 08:27:55 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Feb 7 08:27:55 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Feb 7 08:27:55 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 08:27:55 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Feb 7 08:27:55 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 08:27:55 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Feb 7 08:27:55 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Feb 7 12:03:54 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Feb 7 12:03:54 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 12:03:54 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Feb 7 12:03:54 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Feb 7 12:03:54 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 12:03:54 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Feb 7 12:03:54 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Feb 7 12:03:54 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Feb 7 12:03:54 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 12:03:54 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Feb 7 12:03:54 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 12:03:54 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Feb 7 12:03:54 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Feb 7 16:01:30 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Feb 7 16:01:30 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 16:01:30 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Feb 7 16:01:30 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Feb 7 16:01:30 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 16:01:30 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Feb 7 16:01:30 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Feb 7 16:01:30 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Feb 7 16:01:30 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 16:01:30 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Feb 7 16:01:30 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 16:01:30 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Feb 7 16:01:30 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Feb 7 20:01:24 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Feb 7 20:01:24 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 20:01:24 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Feb 7 20:01:24 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Feb 7 20:01:24 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 20:01:24 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Feb 7 20:01:24 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Feb 7 20:01:24 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Feb 7 20:01:24 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 20:01:25 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Feb 7 20:01:25 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 7 20:01:25 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Feb 7 20:01:25 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 8 08:26:59 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 8 08:27:00 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 08:27:00 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 8 08:27:00 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 8 08:27:01 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 08:27:01 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 8 08:27:01 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 8 08:27:01 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 8 08:27:01 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 08:27:01 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 8 08:27:01 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 08:27:01 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 8 08:27:01 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 8 12:04:07 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 8 12:04:07 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 12:04:07 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 8 12:04:07 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 8 12:04:07 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 12:04:07 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 8 12:04:07 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 8 12:04:07 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 8 12:04:07 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 12:04:07 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 8 12:04:07 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 12:04:07 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 8 12:04:07 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 8 16:01:34 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 8 16:01:34 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 16:01:34 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 8 16:01:34 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 8 16:01:34 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 16:01:34 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 8 16:01:34 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 8 16:01:34 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 8 16:01:34 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 16:01:35 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 8 16:01:35 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 16:01:35 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 8 16:01:35 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 8 20:01:23 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 8 20:01:23 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 20:01:23 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 8 20:01:23 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 8 20:01:23 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 20:01:23 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 8 20:01:23 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 8 20:01:23 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 8 20:01:23 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 20:01:23 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 8 20:01:23 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 8 20:01:23 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 8 20:01:23 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Feb 9 08:10:31 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Feb 9 08:10:31 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 08:10:31 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Feb 9 08:10:31 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Feb 9 08:10:31 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 08:10:31 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Feb 9 08:10:32 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Feb 9 08:10:32 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Feb 9 08:10:32 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 08:10:32 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Feb 9 08:10:32 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 08:10:32 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Feb 9 08:10:32 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Feb 9 12:03:51 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Feb 9 12:03:51 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 12:03:52 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Feb 9 12:03:52 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Feb 9 12:03:52 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 12:03:52 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Feb 9 12:03:52 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Feb 9 12:03:52 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Feb 9 12:03:52 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 12:03:52 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Feb 9 12:03:52 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 12:03:52 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Feb 9 12:03:52 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Feb 9 16:01:35 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Feb 9 16:01:35 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 16:01:35 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Feb 9 16:01:35 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Feb 9 16:01:35 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 16:01:35 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Feb 9 16:01:35 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Feb 9 16:01:35 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Feb 9 16:01:35 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 16:01:35 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Feb 9 16:01:35 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 16:01:35 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Feb 9 16:01:35 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Feb 9 20:01:31 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Feb 9 20:01:31 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 20:01:31 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Feb 9 20:01:31 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Feb 9 20:01:31 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 20:01:31 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Feb 9 20:01:31 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Feb 9 20:01:31 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Feb 9 20:01:31 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 20:01:31 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Feb 9 20:01:31 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 9 20:01:31 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Feb 9 20:01:31 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Feb 10 08:26:32 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Feb 10 08:26:33 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 08:26:34 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Feb 10 08:26:34 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Feb 10 08:26:34 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 08:26:34 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Feb 10 08:26:34 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Feb 10 08:26:34 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Feb 10 08:26:34 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 08:26:34 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Feb 10 08:26:34 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 08:26:34 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Feb 10 08:26:34 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Feb 10 12:04:22 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Feb 10 12:04:22 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 12:04:22 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Feb 10 12:04:22 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Feb 10 12:04:22 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 12:04:22 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Feb 10 12:04:22 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Feb 10 12:04:22 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Feb 10 12:04:22 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 12:04:22 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Feb 10 12:04:22 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 12:04:22 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Feb 10 12:04:22 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Feb 10 16:01:28 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Feb 10 16:01:28 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 16:01:28 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Feb 10 16:01:28 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Feb 10 16:01:29 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 16:01:29 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Feb 10 16:01:29 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Feb 10 16:01:29 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Feb 10 16:01:29 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 16:01:29 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Feb 10 16:01:29 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 16:01:29 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Feb 10 16:01:29 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Feb 10 20:01:26 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Feb 10 20:01:26 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 20:01:26 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Feb 10 20:01:26 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Feb 10 20:01:26 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 20:01:26 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Feb 10 20:01:26 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Feb 10 20:01:26 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Feb 10 20:01:26 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 20:01:26 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Feb 10 20:01:26 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Feb 10 20:01:26 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Feb 10 20:01:26 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Feb 11 08:14:19 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Feb 11 08:14:19 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 08:14:20 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Feb 11 08:14:20 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Feb 11 08:14:20 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 08:14:20 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Feb 11 08:14:20 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Feb 11 08:14:20 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Feb 11 08:14:20 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 08:14:20 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Feb 11 08:14:21 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 08:14:21 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Feb 11 08:14:21 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Feb 11 12:03:16 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Feb 11 12:03:16 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 12:03:16 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Feb 11 12:03:16 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Feb 11 12:03:16 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 12:03:16 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Feb 11 12:03:16 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Feb 11 12:03:16 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Feb 11 12:03:16 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 12:03:16 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Feb 11 12:03:17 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 12:03:17 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Feb 11 12:03:17 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Feb 11 16:01:23 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Feb 11 16:01:23 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 16:01:23 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Feb 11 16:01:23 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Feb 11 16:01:23 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 16:01:23 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Feb 11 16:01:23 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Feb 11 16:01:23 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Feb 11 16:01:23 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 16:01:23 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Feb 11 16:01:23 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 16:01:23 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Feb 11 16:01:23 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Feb 11 20:01:14 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Feb 11 20:01:14 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 20:01:14 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Feb 11 20:01:14 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Feb 11 20:01:14 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 20:01:14 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sat Feb 11 20:01:14 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Feb 11 20:01:15 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Feb 11 20:01:15 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 20:01:15 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Feb 11 20:01:15 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sat Feb 11 20:01:15 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sat Feb 11 20:01:15 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Feb 12 08:10:49 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Feb 12 08:10:50 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 08:10:50 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Feb 12 08:10:50 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Feb 12 08:10:50 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 08:10:50 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Feb 12 08:10:50 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Feb 12 08:10:50 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Feb 12 08:10:50 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 08:10:50 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Feb 12 08:10:50 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 08:10:50 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Feb 12 08:10:50 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Feb 12 12:03:21 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Feb 12 12:03:21 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 12:03:21 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Feb 12 12:03:21 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Feb 12 12:03:21 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 12:03:22 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Feb 12 12:03:22 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Feb 12 12:03:22 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Feb 12 12:03:22 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 12:03:22 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Feb 12 12:03:22 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 12:03:22 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Feb 12 12:03:22 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Feb 12 16:01:27 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Feb 12 16:01:27 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 16:01:27 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Feb 12 16:01:27 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Feb 12 16:01:27 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 16:01:27 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Feb 12 16:01:27 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Feb 12 16:01:27 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Feb 12 16:01:27 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 16:01:27 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Feb 12 16:01:28 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 16:01:28 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Feb 12 16:01:28 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Feb 12 20:01:20 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Feb 12 20:01:20 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 20:01:20 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Feb 12 20:01:20 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Feb 12 20:01:21 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 20:01:21 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Sun Feb 12 20:01:21 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Feb 12 20:01:21 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Feb 12 20:01:21 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 20:01:21 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Feb 12 20:01:21 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Sun Feb 12 20:01:21 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Sun Feb 12 20:01:21 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Feb 13 08:19:56 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Feb 13 08:20:00 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 08:20:00 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Feb 13 08:20:00 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Feb 13 08:20:00 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 08:20:00 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Feb 13 08:20:00 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Feb 13 08:20:00 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Feb 13 08:20:00 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 08:20:00 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Feb 13 08:20:00 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 08:20:00 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Feb 13 08:20:00 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Feb 13 12:03:45 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Feb 13 12:03:46 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 12:03:46 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Feb 13 12:03:46 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Feb 13 12:03:46 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 12:03:46 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Feb 13 12:03:46 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Feb 13 12:03:46 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Feb 13 12:03:46 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 12:03:46 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Feb 13 12:03:46 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 12:03:46 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Feb 13 12:03:46 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Feb 13 16:01:47 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Feb 13 16:01:47 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 16:01:47 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Feb 13 16:01:47 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Feb 13 16:01:47 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 16:01:47 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Feb 13 16:01:47 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Feb 13 16:01:47 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Feb 13 16:01:47 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 16:01:47 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Feb 13 16:01:47 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 16:01:47 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Feb 13 16:01:47 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Feb 13 20:01:24 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Feb 13 20:01:25 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 20:01:25 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Feb 13 20:01:25 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Feb 13 20:01:25 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 20:01:25 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Mon Feb 13 20:01:25 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Feb 13 20:01:25 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Feb 13 20:01:25 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 20:01:25 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Feb 13 20:01:25 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Feb 13 20:01:25 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Mon Feb 13 20:01:25 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Feb 14 08:21:59 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Feb 14 08:21:59 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 08:21:59 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Feb 14 08:21:59 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Feb 14 08:22:00 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 08:22:00 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Feb 14 08:22:00 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Feb 14 08:22:00 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Feb 14 08:22:01 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 08:22:01 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Feb 14 08:22:01 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 08:22:01 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Feb 14 08:22:01 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Feb 14 12:04:01 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Feb 14 12:04:01 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 12:04:01 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Feb 14 12:04:01 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Feb 14 12:04:01 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 12:04:01 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Feb 14 12:04:01 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Feb 14 12:04:01 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Feb 14 12:04:01 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 12:04:01 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Feb 14 12:04:02 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 12:04:02 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Feb 14 12:04:02 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Feb 14 16:02:01 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Feb 14 16:02:01 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 16:02:01 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Feb 14 16:02:01 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Feb 14 16:02:01 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 16:02:01 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Feb 14 16:02:01 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Feb 14 16:02:01 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Feb 14 16:02:01 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 16:02:01 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Feb 14 16:02:01 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 16:02:01 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Feb 14 16:02:01 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Feb 14 20:01:30 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Feb 14 20:01:30 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 20:01:30 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Feb 14 20:01:31 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Feb 14 20:01:31 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 20:01:31 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Tue Feb 14 20:01:31 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Feb 14 20:01:31 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Feb 14 20:01:31 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 20:01:31 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Feb 14 20:01:31 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Feb 14 20:01:31 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Tue Feb 14 20:01:31 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 15 08:34:01 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 15 08:34:01 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 08:34:02 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 15 08:34:02 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 15 08:34:02 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 08:34:02 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 15 08:34:02 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 15 08:34:02 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 15 08:34:02 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 08:34:02 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 15 08:34:02 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 08:34:02 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 15 08:34:02 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 15 12:06:18 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 15 12:06:18 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 12:06:18 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 15 12:06:18 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 15 12:06:18 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 12:06:18 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 15 12:06:18 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 15 12:06:18 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 15 12:06:18 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 12:06:18 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 15 12:06:18 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 12:06:18 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 15 12:06:18 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 15 16:01:55 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 15 16:01:55 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 16:01:55 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 15 16:01:55 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 15 16:01:55 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 16:01:55 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 15 16:01:55 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 15 16:01:55 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 15 16:01:55 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 16:01:55 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 15 16:01:55 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 16:01:55 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 15 16:01:55 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 15 19:28:33 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 15 19:28:33 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 19:28:33 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 15 19:28:33 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 15 19:28:33 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 19:28:33 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 15 19:28:33 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 15 19:28:33 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 15 19:28:33 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 19:28:33 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 15 19:28:33 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 19:28:33 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 15 19:28:33 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 15 20:15:45 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 15 20:15:45 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 20:15:45 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 15 20:15:45 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 15 20:15:45 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 20:15:45 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Wed Feb 15 20:15:45 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 15 20:15:45 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 15 20:15:45 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 20:15:45 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 15 20:15:45 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Feb 15 20:15:45 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Wed Feb 15 20:15:45 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Feb 16 08:51:00 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Feb 16 08:51:03 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 16 08:51:03 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Feb 16 08:51:03 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Feb 16 08:51:03 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 16 08:51:04 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Thu Feb 16 08:51:04 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Feb 16 08:51:04 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Feb 16 08:51:04 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 16 08:51:04 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Feb 16 08:51:04 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Feb 16 08:51:04 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Thu Feb 16 08:51:04 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten From fuf at mageo.cz Wed Nov 9 08:42:28 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Mar 31 16:34:29 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4370FBAC.8000306@easysoft.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> Message-ID: <20051109084226.GQ1318@foof.i3.cz> hello everyone, Marc, i'm having problems with Solid, unixODBC, mxODBC combo (please read below). i originally posted the problem description to unixodbc-support list but it seems this is not their problem. can someone please help how to get around this problem? i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. thank you, Michal Martin J. Evans wrote: >Nick Gorham wrote: >>Michal Vitecek wrote: >> >>>hello Nick, >>> >>>Nick Gorham wrote: >>> >>> >>>>Michal Vitecek wrote: >>>> >>>> >>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>error: >>>>> >>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>type attribute violation', 3326): from [snip] >>>>> >>>>>when i try to retrieve the column values via isql all i get is empty >>>>>strings for the column (all other columns of different types are okay). >>>>> >>>> >>>>At first sight I would guess you are asking the driver for a column >>>>in a type it doesn't understand. >>>> >>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>trace would at least show what mxODBC is asking the driver to do. >>>> >>> >>> >>>below is the relevant (i think) part of the trace. thank you again. >>> >>> >>Not much help, but I think the problem is between the driver and the >>app, the app is binding a null pointer, which I suspect is confusing the >>driver > >and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >unbinding - I think. > >>[ODBC][696][SQLBindCol.c][165] >> Entry: >> Statement = 0x8298a70 >> Column Number = 1 >> Target Type = 1 SQL_CHAR >> Target Value = (nil) >> Buffer Length = 0 >> StrLen Or Ind = (nil) >> >> >Martin >_______________________________________________ >unixODBC-support mailing list >unixODBC-support@easysoft.com >http://mail.easysoft.com/mailman/listinfo/unixodbc-support the relevant part of the trace: [ODBC][696][SQLExecDirect.c][233] Entry: Statement = 0x8298a70 SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] [ODBC][696][SQLExecDirect.c][496] Exit:[SQL_SUCCESS] [ODBC][696][SQLNumResultCols.c][149] Entry: Statement = 0x8298a70 Column Count = 0xbf864c5a [ODBC][696][SQLNumResultCols.c][234] Exit:[SQL_SUCCESS] Count = 0xbf864c5a -> 1 [ODBC][696][SQLRowCount.c][166] Entry: Statement = 0x8298a70 Row Count = 0xbf864c54 [ODBC][696][SQLRowCount.c][237] Exit:[SQL_SUCCESS] Row Count = 0xbf864c54 -> -1 [ODBC][696][SQLDescribeCol.c][231] Entry: Statement = 0x8298a70 Column Number = 1 Column Name = 0x829ae70 Buffer Length = 38 Name Length = 0x829ae96 Data Type = 0x829ae98 Column Size = 0x829ae9c Decimal Digits = 0x829aea0 Nullable = 0x829aea2 [ODBC][696][SQLDescribeCol.c][474] Exit:[SQL_SUCCESS] Column Name = [XMLSOURCE] Data Type = 0x829ae98 -> 12 Column Size = 0x829ae9c -> 262144 Decimal Digits = 0x829aea0 -> 0 Nullable = 0x829aea2 -> 1 [ODBC][696][SQLFreeStmt.c][140] Entry: Statement = 0x8298a70 Option = 2 [ODBC][696][SQLFreeStmt.c][246] Exit:[SQL_SUCCESS] [ODBC][696][SQLBindCol.c][165] Entry: Statement = 0x8298a70 Column Number = 1 Target Type = 1 SQL_CHAR Target Value = (nil) Buffer Length = 0 StrLen Or Ind = (nil) [ODBC][696][SQLBindCol.c][251] Exit:[SQL_SUCCESS] [ODBC][696][SQLFetch.c][158] Entry: Statement = 0x8298a70 [ODBC][696][SQLFetch.c][340] Exit:[SQL_ERROR] DIAG [07006] Restricted data type attribute violation -- fuf (fuf@mageo.cz) From fuf at mageo.cz Thu Nov 10 17:19:06 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Mar 31 16:34:29 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <20051110171903.GJ1358@foof.i3.cz> anyone please? i really need to find a solution for this. thank you, Michal Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? > > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > > thank you, > Michal > >Martin J. Evans wrote: >>Nick Gorham wrote: >>>Michal Vitecek wrote: >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > >the relevant part of the trace: > >[ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] >[ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a >[ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 >[ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 >[ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 >[ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 >[ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 >[ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 >[ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) >[ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] >[ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 >[ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Sat Nov 12 11:44:37 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Mar 31 16:34:29 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051109084226.GQ1318@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> Message-ID: <4375D5A3.7010900@egenix.com> Hi Michal, Michal Vitecek wrote: > hello everyone, Marc, > > i'm having problems with Solid, unixODBC, mxODBC combo (please read > below). i originally posted the problem description to unixodbc-support > list but it seems this is not their problem. > > can someone please help how to get around this problem? Some ODBC drivers don't like it when the app unbinds columns. The best thing to do in this case, is to simply comment out the unbinding section in mxODBC.c. > i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. Solid's ODBC driver is known to have the unbind incompatibility, so commenting out the section will fix the problem. The Nexus DB ODBC driver is another such candidate. > thank you, > Michal > > Martin J. Evans wrote: > >>Nick Gorham wrote: >> >>>Michal Vitecek wrote: >>> >>> >>>>hello Nick, >>>> >>>>Nick Gorham wrote: >>>> >>>> >>>> >>>>>Michal Vitecek wrote: >>>>> >>>>> >>>>> >>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>error: >>>>>> >>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>type attribute violation', 3326): from [snip] >>>>>> >>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>strings for the column (all other columns of different types are okay). >>>>>> >>>>> >>>>>At first sight I would guess you are asking the driver for a column >>>>>in a type it doesn't understand. >>>>> >>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>trace would at least show what mxODBC is asking the driver to do. >>>>> >>>> >>>> >>>>below is the relevant (i think) part of the trace. thank you again. >>>> >>>> >>> >>>Not much help, but I think the problem is between the driver and the >>>app, the app is binding a null pointer, which I suspect is confusing the >>>driver >> >>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>unbinding - I think. >> >> >>>[ODBC][696][SQLBindCol.c][165] >>> Entry: >>> Statement = 0x8298a70 >>> Column Number = 1 >>> Target Type = 1 SQL_CHAR >>> Target Value = (nil) >>> Buffer Length = 0 >>> StrLen Or Ind = (nil) >>> >>> >> >>Martin >>_______________________________________________ >>unixODBC-support mailing list >>unixODBC-support@easysoft.com >>http://mail.easysoft.com/mailman/listinfo/unixodbc-support > > > the relevant part of the trace: > > [ODBC][696][SQLExecDirect.c][233] > Entry: > Statement = 0x8298a70 > SQL = [SELECT xmlSource FROM scriptSource WHERE scriptId=28][length = 52] > [ODBC][696][SQLExecDirect.c][496] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLNumResultCols.c][149] > Entry: > Statement = 0x8298a70 > Column Count = 0xbf864c5a > [ODBC][696][SQLNumResultCols.c][234] > Exit:[SQL_SUCCESS] > Count = 0xbf864c5a -> 1 > [ODBC][696][SQLRowCount.c][166] > Entry: > Statement = 0x8298a70 > Row Count = 0xbf864c54 > [ODBC][696][SQLRowCount.c][237] > Exit:[SQL_SUCCESS] > Row Count = 0xbf864c54 -> -1 > [ODBC][696][SQLDescribeCol.c][231] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Column Name = 0x829ae70 > Buffer Length = 38 > Name Length = 0x829ae96 > Data Type = 0x829ae98 > Column Size = 0x829ae9c > Decimal Digits = 0x829aea0 > Nullable = 0x829aea2 > [ODBC][696][SQLDescribeCol.c][474] > Exit:[SQL_SUCCESS] > Column Name = [XMLSOURCE] > Data Type = 0x829ae98 -> 12 > Column Size = 0x829ae9c -> 262144 > Decimal Digits = 0x829aea0 -> 0 > Nullable = 0x829aea2 -> 1 > [ODBC][696][SQLFreeStmt.c][140] > Entry: > Statement = 0x8298a70 > Option = 2 > [ODBC][696][SQLFreeStmt.c][246] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLBindCol.c][165] > Entry: > Statement = 0x8298a70 > Column Number = 1 > Target Type = 1 SQL_CHAR > Target Value = (nil) > Buffer Length = 0 > StrLen Or Ind = (nil) > [ODBC][696][SQLBindCol.c][251] > Exit:[SQL_SUCCESS] > [ODBC][696][SQLFetch.c][158] > Entry: > Statement = 0x8298a70 > [ODBC][696][SQLFetch.c][340] > Exit:[SQL_ERROR] > DIAG [07006] Restricted data type attribute violation > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 12 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Mon Nov 14 17:18:09 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Mar 31 16:34:29 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <4375D5A3.7010900@egenix.com> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> Message-ID: <20051114171807.GD1358@foof.i3.cz> hello Marc, M.-A. Lemburg wrote: >Michal Vitecek wrote: >> hello everyone, Marc, >> >> i'm having problems with Solid, unixODBC, mxODBC combo (please read >> below). i originally posted the problem description to unixodbc-support >> list but it seems this is not their problem. >> >> can someone please help how to get around this problem? > >Some ODBC drivers don't like it when the app unbinds columns. > >The best thing to do in this case, is to simply comment >out the unbinding section in mxODBC.c. i looked at the code but unfortunately failed to find the spot to comment. can you please be more specific? >> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. > >Solid's ODBC driver is known to have the unbind incompatibility, >so commenting out the section will fix the problem. The Nexus DB >ODBC driver is another such candidate. in the meantime i tested with Solid 4.2 and the error 'Restricted data type attribute violation' gets replaced with another one: 'String data, right truncated' *sigh*. can you please help again? thanks a lot, Michal >> >> Martin J. Evans wrote: >>>Nick Gorham wrote: >>>>Michal Vitecek wrote: >>>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>error: >>>>>>> >>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>type attribute violation', 3326): from [snip] >>>>>>> >>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>strings for the column (all other columns of different types are okay). >>>>>>> >>>>>> >>>>>>At first sight I would guess you are asking the driver for a column >>>>>>in a type it doesn't understand. >>>>>> >>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>> >>>>> >>>>> >>>>>below is the relevant (i think) part of the trace. thank you again. >>>>> >>>>> >>>> >>>>Not much help, but I think the problem is between the driver and the >>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>driver >>> >>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>unbinding - I think. >>> >>> >>>>[ODBC][696][SQLBindCol.c][165] >>>> Entry: >>>> Statement = 0x8298a70 >>>> Column Number = 1 >>>> Target Type = 1 SQL_CHAR >>>> Target Value = (nil) >>>> Buffer Length = 0 >>>> StrLen Or Ind = (nil) >>>> -- fuf (fuf@mageo.cz) From fuf at mageo.cz Tue Nov 15 12:32:05 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Mar 31 16:34:29 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051114171807.GD1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> Message-ID: <20051115123202.GJ1358@foof.i3.cz> hello Marc, a bit of information ... Michal Vitecek wrote: >M.-A. Lemburg wrote: >>Michal Vitecek wrote: >>> hello everyone, Marc, >>> >>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>> below). i originally posted the problem description to unixodbc-support >>> list but it seems this is not their problem. >>> >>> can someone please help how to get around this problem? >> >>Some ODBC drivers don't like it when the app unbinds columns. >> >>The best thing to do in this case, is to simply comment >>out the unbinding section in mxODBC.c. > > i looked at the code but unfortunately failed to find the spot to > comment. can you please be more specific? i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). however commenting out the unbinding code doesn't help: mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or buffer length', 3258) any suggestions? i *really* need get this thing working. thanks, Michal >>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >> >>Solid's ODBC driver is known to have the unbind incompatibility, >>so commenting out the section will fix the problem. The Nexus DB >>ODBC driver is another such candidate. > > in the meantime i tested with Solid 4.2 and the error 'Restricted data > type attribute violation' gets replaced with another one: 'String data, > right truncated' *sigh*. > > can you please help again? > > thanks a lot, > Michal > >>> >>> Martin J. Evans wrote: >>>>Nick Gorham wrote: >>>>>Michal Vitecek wrote: >>>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>error: >>>>>>>> >>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>> >>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>> >>>>>>> >>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>in a type it doesn't understand. >>>>>>> >>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>> >>>>>> >>>>>> >>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>> >>>>>> >>>>> >>>>>Not much help, but I think the problem is between the driver and the >>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>driver >>>> >>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>unbinding - I think. >>>> >>>> >>>>>[ODBC][696][SQLBindCol.c][165] >>>>> Entry: >>>>> Statement = 0x8298a70 >>>>> Column Number = 1 >>>>> Target Type = 1 SQL_CHAR >>>>> Target Value = (nil) >>>>> Buffer Length = 0 >>>>> StrLen Or Ind = (nil) >>>>> > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From mal at egenix.com Tue Nov 15 12:56:31 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Mar 31 16:34:29 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <4379DAFB.4070106@egenix.com> Michal Vitecek wrote: > hello Marc, > > a bit of information ... > > Michal Vitecek wrote: > >>M.-A. Lemburg wrote: >> >>>Michal Vitecek wrote: >>> >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >>i looked at the code but unfortunately failed to find the spot to >>comment. can you please be more specific? > > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). This is the part I was talking about: /* Unbind the column in case SQLGetData is to be used... just in case */ if (use_getdata) { rc = SQLBindCol(dbcs->hstmt, (SQLUSMALLINT)(i + 1), var->ctype, NULL, 0, NULL); mxODBC_SQLCheck(henv,dbcs->dbc->hdbc,dbcs->hstmt); } > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) Debugging this will require more work. Please get a support ticket, so that we can dig deeper into your driver issues. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 15 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2005-10-17: Released mxODBC.Zope.DA 1.0.9 http://zope.egenix.com/ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From fuf at mageo.cz Tue Nov 15 13:04:39 2005 From: fuf at mageo.cz (Michal Vitecek) Date: Fri Mar 31 16:34:30 2006 Subject: [egenix-users] Re: [unixODBC-support] Solid, unixODBC & mxODBC: Restricted datatype attribute violation In-Reply-To: <20051115123202.GJ1358@foof.i3.cz> References: <20051108154414.GK1318@foof.i3.cz> <4370CE62.2040301@easysoft.com> <20051108162054.GM1318@foof.i3.cz> <4370EBDB.7070706@easysoft.com> <4370FBAC.8000306@easysoft.com> <20051109084226.GQ1318@foof.i3.cz> <4375D5A3.7010900@egenix.com> <20051114171807.GD1358@foof.i3.cz> <20051115123202.GJ1358@foof.i3.cz> Message-ID: <20051115130433.GK1358@foof.i3.cz> hello Marc, some more information ... Michal Vitecek wrote: >Michal Vitecek wrote: >>M.-A. Lemburg wrote: >>>Michal Vitecek wrote: >>>> hello everyone, Marc, >>>> >>>> i'm having problems with Solid, unixODBC, mxODBC combo (please read >>>> below). i originally posted the problem description to unixodbc-support >>>> list but it seems this is not their problem. >>>> >>>> can someone please help how to get around this problem? >>> >>>Some ODBC drivers don't like it when the app unbinds columns. >>> >>>The best thing to do in this case, is to simply comment >>>out the unbinding section in mxODBC.c. >> >> i looked at the code but unfortunately failed to find the spot to >> comment. can you please be more specific? > > i think i have found the place (mx/ODBC/unixODBC/mxODBC.c:3086). > however commenting out the unbinding code doesn't help: > > mxODBC.InternalError: ('S1090', 25204, '[unixODBC]Invalid string or > buffer length', 3258) if i set the GETDATA_THRESHOLD from 64k to 386k everything works correctly because vars[i].use_getdata == 0. however when the threshold is lowered again to 64k, the value of vars[i].use_getdata == 1. SQLFetch() call in mxODBCursor_Fetch() returns a value which mxODBC_SQLCheck() considers as an error and so SQLGetData() is never called. > > any suggestions? i *really* need get this thing working. > > thanks, > Michal > > >>>> i'm using Solid 3.5, mxODBC 2.0.7, unixODBC 2.2.11. >>> >>>Solid's ODBC driver is known to have the unbind incompatibility, >>>so commenting out the section will fix the problem. The Nexus DB >>>ODBC driver is another such candidate. >> >> in the meantime i tested with Solid 4.2 and the error 'Restricted data >> type attribute violation' gets replaced with another one: 'String data, >> right truncated' *sigh*. >> >> can you please help again? >> >> thanks a lot, >> Michal >> >>>> >>>> Martin J. Evans wrote: >>>>>Nick Gorham wrote: >>>>>>Michal Vitecek wrote: >>>>>>>Nick Gorham wrote: >>>>>>>Michal Vitecek wrote: >>>>>>>>>i'm in the process of trying to use unixODBC in between the Solid >>>>>>>>>database engine and the mxODBC (python extension which adds ODBC >>>>>>>>>support). the problem is that i'm unable to retrieve values of columns >>>>>>>>>which are defined as 'VARCHAR(262144)' (256KB) and get the following >>>>>>>>>error: >>>>>>>>> >>>>>>>>>Traceback: ProgrammingError ('07006', -1, '[unixODBC]Restricted data >>>>>>>>>type attribute violation', 3326): from [snip] >>>>>>>>> >>>>>>>>>when i try to retrieve the column values via isql all i get is empty >>>>>>>>>strings for the column (all other columns of different types are okay). >>>>>>>>> >>>>>>>> >>>>>>>>At first sight I would guess you are asking the driver for a column >>>>>>>>in a type it doesn't understand. >>>>>>>> >>>>>>>>isql doesn't show long fields so that may be the problem. A ODBC >>>>>>>>trace would at least show what mxODBC is asking the driver to do. >>>>>>>> >>>>>>> >>>>>>> >>>>>>>below is the relevant (i think) part of the trace. thank you again. >>>>>>> >>>>>>> >>>>>> >>>>>>Not much help, but I think the problem is between the driver and the >>>>>>app, the app is binding a null pointer, which I suspect is confusing the >>>>>>driver >>>>> >>>>>and binding a NULL TargetValuePtr and StrLen_Or_Ind is the same as >>>>>unbinding - I think. >>>>> >>>>> >>>>>>[ODBC][696][SQLBindCol.c][165] >>>>>> Entry: >>>>>> Statement = 0x8298a70 >>>>>> Column Number = 1 >>>>>> Target Type = 1 SQL_CHAR >>>>>> Target Value = (nil) >>>>>> Buffer Length = 0 >>>>>> StrLen Or Ind = (nil) >>>>>> >> >>-- >> fuf (fuf@mageo.cz) >> >> >>_______________________________________________________________________ >>eGenix.com User Mailing List http://www.egenix.com/ >>https://www.egenix.com/mailman/listinfo/egenix-users > >-- > fuf (fuf@mageo.cz) > > >_______________________________________________________________________ >eGenix.com User Mailing List http://www.egenix.com/ >https://www.egenix.com/mailman/listinfo/egenix-users -- fuf (fuf@mageo.cz) From morten at nilsen.com Fri Nov 25 15:23:27 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Mar 31 16:34:30 2006 Subject: [egenix-users] problem compiling mx-base package: Message-ID: <43872C6C.3030804@nilsen.com> I'm trying to build egenix-mx-base for TSL (community contrib package repository) and I've got some trouble running install: byte-compiling /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py to pytag.pyc /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: SyntaxWarning: name 'debugging' is used prior to global declaration python: stack smashing attack in function symtable_node/var/tmp/rpm-tmp.43489: line 22: 23519 Aborted CFLAGS="-fno-stack-protector" python setup.py install --root=$RPM_BUILD_ROOT error: Bad exit status from /var/tmp/rpm-tmp.43489 (%install) what is causing this? -- Morten From morten at nilsen.com Sun Nov 27 15:37:54 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Mar 31 16:34:30 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <43872C6C.3030804@nilsen.com> References: <43872C6C.3030804@nilsen.com> Message-ID: <4389D2CF.2030709@nilsen.com> Morten Nilsen wrote: > byte-compiling > /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py > to pytag.pyc > /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: > SyntaxWarning: name 'debugging' is used prior to global declaration > python: stack smashing attack in function hello? -- Morten From mal at egenix.com Sun Nov 27 17:52:30 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Mar 31 16:34:30 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389D2CF.2030709@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> Message-ID: <4389F25C.6000806@egenix.com> Morten Nilsen wrote: > Morten Nilsen wrote: > >> byte-compiling >> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >> to pytag.pyc >> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >> SyntaxWarning: name 'debugging' is used prior to global declaration >> python: stack smashing attack in function > > > hello? What's the question ? Note that pytag.py is no longer supported and should probably be removed from mxTextTools. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 17:55:44 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Mar 31 16:34:30 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F25C.6000806@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> Message-ID: <4389F31D.2000304@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>>byte-compiling >>>/var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>to pytag.pyc >>>/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>SyntaxWarning: name 'debugging' is used prior to global declaration >>>python: stack smashing attack in function >> > What's the question ? like I wrote in the first mail, what causes this - and - how can I resolve the issue? > Note that pytag.py is no longer supported and > should probably be removed from mxTextTools. > -- Morten From mal at egenix.com Sun Nov 27 17:57:49 2005 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Mar 31 16:34:30 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F31D.2000304@nilsen.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> Message-ID: <4389F39B.4050507@egenix.com> Morten Nilsen wrote: > M.-A. Lemburg wrote: > >> Morten Nilsen wrote: >> >>>> byte-compiling >>>> /var/tmp/python-egenix-buildroot/usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py >>>> >>>> to pytag.pyc >>>> /usr/lib/python2.3/site-packages/mx/TextTools/Examples/pytag.py:47: >>>> SyntaxWarning: name 'debugging' is used prior to global declaration >>>> python: stack smashing attack in function >>> >>> >> What's the question ? > > > like I wrote in the first mail, what causes this - and - how can I > resolve the issue? No idea. Try removing pytag.py. >> Note that pytag.py is no longer supported and >> should probably be removed from mxTextTools. >> > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Nov 27 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: From morten at nilsen.com Sun Nov 27 18:18:34 2005 From: morten at nilsen.com (Morten Nilsen) Date: Fri Mar 31 16:34:30 2006 Subject: [egenix-users] problem compiling mx-base package: In-Reply-To: <4389F39B.4050507@egenix.com> References: <43872C6C.3030804@nilsen.com> <4389D2CF.2030709@nilsen.com> <4389F25C.6000806@egenix.com> <4389F31D.2000304@nilsen.com> <4389F39B.4050507@egenix.com> Message-ID: <4389F878.7010502@nilsen.com> M.-A. Lemburg wrote: > Morten Nilsen wrote: >>like I wrote in the first mail, what causes this - and - how can I >>resolve the issue? > > No idea. Try removing pytag.py. not really sure how I can do that.. it's installed by setup.py install, which is the same command that fails.. after running these two commands before install; rm ./mx/TextTools/Examples/pytag.py rm ./build/lib.linux-i686-2.3/mx/TextTools/Examples/pytag.py the install succeeds, and I'm now able to package mx-base, thanks :) -- Morten