Re: MariaDB limitation on memo fields -- caps out at 255
On 2019-02-27 19:50, Eric Selje wrote: Well it's happened again where I discover a blog post I made that helps me towards a current problem. Looking here: http://saltydogllc.com/on-vfp-and-mysql-connectionstrings/ Here are the options (at the time, I doubt they've changed): 2 = Return matched rows instead of affected rows 8 = Allow big result sets 16 = Don’t prompt when connecting 32 = Enable dynamic cursors 64 = Ignore schema in column specifications 128 = Disable driver-provided cursor support 256 = Don’t use setlocale() 512 = Pad CHAR to full length with space 1024 = Include table name in SQLDescribeCol() 2048 = Use compression 4096 = Ignore space after function names 8192 = Force use of named pipes 16384 = Treat BIGINT columns as INT columns 32768 = Disable catalog support 65536 = Read options from my.cnf 131072 = Enable safe options (see documentation) 262144 = Disable transaction support 524288 = Log queries to myodbc.sql 1048576 = Don’t cache results of forward-only cursors 2097152 = Force use of forward-only cursors 4194304 = Enable automatic reconnect 8388608 = Enable SQL_AUTO_IS_NULL 67108864 = Allow multiple statements 134217728 = Limit column size to signed 32-bit range 268435456 = Always handle binary function results as character data Your value of 67174427 means: 67108864 = Allow multiple statements + 65536 = Read options from my.cnf + 16 = Don’t prompt when connecting + 8 = Allow big result sets + 2 = Return matched rows instead of affected rows + 1 (I don't know what this means) Not sure what's in your *my.cnf* that might affect the results. Maybe throw a 512 or 64 in there to see what happens? Eric What do you typically use, Eric? ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/a34f24d2985230ff5778c8d1ef1de...@mbsoftwaresolutions.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Re: MariaDB limitation on memo fields -- caps out at 255
On 2019-02-27 19:50, Eric Selje wrote: Well it's happened again where I discover a blog post I made that helps me towards a current problem. Looking here: http://saltydogllc.com/on-vfp-and-mysql-connectionstrings/ Here are the options (at the time, I doubt they've changed): 2 = Return matched rows instead of affected rows 8 = Allow big result sets 16 = Don’t prompt when connecting 32 = Enable dynamic cursors 64 = Ignore schema in column specifications 128 = Disable driver-provided cursor support 256 = Don’t use setlocale() 512 = Pad CHAR to full length with space 1024 = Include table name in SQLDescribeCol() 2048 = Use compression 4096 = Ignore space after function names 8192 = Force use of named pipes 16384 = Treat BIGINT columns as INT columns 32768 = Disable catalog support 65536 = Read options from my.cnf 131072 = Enable safe options (see documentation) 262144 = Disable transaction support 524288 = Log queries to myodbc.sql 1048576 = Don’t cache results of forward-only cursors 2097152 = Force use of forward-only cursors 4194304 = Enable automatic reconnect 8388608 = Enable SQL_AUTO_IS_NULL 67108864 = Allow multiple statements 134217728 = Limit column size to signed 32-bit range 268435456 = Always handle binary function results as character data Your value of 67174427 means: 67108864 = Allow multiple statements + 65536 = Read options from my.cnf + 16 = Don’t prompt when connecting + 8 = Allow big result sets + 2 = Return matched rows instead of affected rows + 1 (I don't know what this means) Not sure what's in your *my.cnf* that might affect the results. Maybe throw a 512 or 64 in there to see what happens? Eric What do you typically use, Eric? Also, I looked for the my.cnf file and couldn't find it on my or the client systems? ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/1403ab89b53308e535fd76f48d4a8...@mbsoftwaresolutions.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Re: MariaDB limitation on memo fields -- caps out at 255
Well it's happened again where I discover a blog post I made that helps me towards a current problem. Looking here: http://saltydogllc.com/on-vfp-and-mysql-connectionstrings/ Here are the options (at the time, I doubt they've changed): 2 = Return matched rows instead of affected rows 8 = Allow big result sets 16 = Don’t prompt when connecting 32 = Enable dynamic cursors 64 = Ignore schema in column specifications 128 = Disable driver-provided cursor support 256 = Don’t use setlocale() 512 = Pad CHAR to full length with space 1024 = Include table name in SQLDescribeCol() 2048 = Use compression 4096 = Ignore space after function names 8192 = Force use of named pipes 16384 = Treat BIGINT columns as INT columns 32768 = Disable catalog support 65536 = Read options from my.cnf 131072 = Enable safe options (see documentation) 262144 = Disable transaction support 524288 = Log queries to myodbc.sql 1048576 = Don’t cache results of forward-only cursors 2097152 = Force use of forward-only cursors 4194304 = Enable automatic reconnect 8388608 = Enable SQL_AUTO_IS_NULL 67108864 = Allow multiple statements 134217728 = Limit column size to signed 32-bit range 268435456 = Always handle binary function results as character data Your value of 67174427 means: 67108864 = Allow multiple statements + 65536 = Read options from my.cnf + 16 = Don’t prompt when connecting + 8 = Allow big result sets + 2 = Return matched rows instead of affected rows + 1 (I don't know what this means) Not sure what's in your *my.cnf* that might affect the results. Maybe throw a 512 or 64 in there to see what happens? Eric On Wed, Feb 27, 2019 at 11:16 AM < mbsoftwaresoluti...@mbsoftwaresolutions.com> wrote: > I'd appreciate that, Eric. I'm using 67174427. > > > On 2019-02-25 14:42, Eric Selje wrote: > > Yes I'd check your ConnectionString Options. Whil Hentzen's book about > > devloping with Fox and MySQL (Maria) goes over all of those. I can > > check > > it if you'd like. > > > > Eric > > > > On Mon, Feb 18, 2019 at 7:36 PM > > > > wrote: > > > >> On 2019-02-18 18:07, Fred Taylor wrote: > >> > Mike, > >> > > >> > Are you sure it's not a TINYTEXT field? TINYTEXT is 0 to 255 chars. > >> > > >> > TEXT is 65,535 > >> > > >> > And MEDIUMTEXT is 16,777,215. > >> > > >> > Fred > >> > >> > >> I'll double-check but I'm thinking it's my connection string OPTIONS > >> value. > >> [excessive quoting removed by server] ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/CAAwxvU=mpy2dm8cfzzrfnebefsdyoq-+wr5xx98mjcszmeq...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Re: MariaDB limitation on memo fields -- caps out at 255 (SOLVED)
On 2019-02-23 01:23, mbsoftwaresoluti...@mbsoftwaresolutions.com wrote: On 2019-02-18 15:50, mbsoftwaresoluti...@mbsoftwaresolutions.com wrote: My VFP9SP2 app connects to my web database with no issue. My client wanted to host the database on his network there so I installed MariaDB there and everything seemed to fire up just fine. HOWEVER, there's a problem with the memo fields capping at length=255. Given that it works with a different (my web) MariaDB database, I'm sure this is a configuration issue. Question is: where do I find/set that? His network OS is Windows 2016 Server. My web database is using a Linux OS iirc. tia, --Mike Here's the weird fix: instead of using a MEDIUMTEXT field, it worked just fine when I changed it to TEXT fields. Now MEDIUMTEXT is supposed to handle LARGER #s of characters, but in this case, just TEXT should suffice. Still...wonder why the ODBC (originally 3.51, then I upgraded to the latest 64-bit MariaDB driver) has a problem with MEDIUMTEXT on this Windows 2016 Server? My other database (where no issues at all) operates on a Debian Linux OS. Thoughts? No takers on this one. Look at the solution above. Thoughts on why TEXT worked and not MEDIUMTEXT (which is larger than TEXT iirc)? tia, --Mike ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/f743075b64adf1083a3e34348960e...@mbsoftwaresolutions.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Re: MariaDB limitation on memo fields -- caps out at 255
I'd appreciate that, Eric. I'm using 67174427. On 2019-02-25 14:42, Eric Selje wrote: Yes I'd check your ConnectionString Options. Whil Hentzen's book about devloping with Fox and MySQL (Maria) goes over all of those. I can check it if you'd like. Eric On Mon, Feb 18, 2019 at 7:36 PM wrote: On 2019-02-18 18:07, Fred Taylor wrote: > Mike, > > Are you sure it's not a TINYTEXT field? TINYTEXT is 0 to 255 chars. > > TEXT is 65,535 > > And MEDIUMTEXT is 16,777,215. > > Fred I'll double-check but I'm thinking it's my connection string OPTIONS value. [excessive quoting removed by server] ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/fbb6724da613f39736b11588b1c58...@mbsoftwaresolutions.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Re: MariaDB limitation on memo fields -- caps out at 255
Yes I'd check your ConnectionString Options. Whil Hentzen's book about devloping with Fox and MySQL (Maria) goes over all of those. I can check it if you'd like. Eric On Mon, Feb 18, 2019 at 7:36 PM wrote: > On 2019-02-18 18:07, Fred Taylor wrote: > > Mike, > > > > Are you sure it's not a TINYTEXT field? TINYTEXT is 0 to 255 chars. > > > > TEXT is 65,535 > > > > And MEDIUMTEXT is 16,777,215. > > > > Fred > > > I'll double-check but I'm thinking it's my connection string OPTIONS > value. > [excessive quoting removed by server] ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/caawxvuktcerb9v+yvoof5t96cb4fbu71mvbs1fuy0dwe67y...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Re: MariaDB limitation on memo fields -- caps out at 255 (SOLVED)
On 2019-02-18 15:50, mbsoftwaresoluti...@mbsoftwaresolutions.com wrote: My VFP9SP2 app connects to my web database with no issue. My client wanted to host the database on his network there so I installed MariaDB there and everything seemed to fire up just fine. HOWEVER, there's a problem with the memo fields capping at length=255. Given that it works with a different (my web) MariaDB database, I'm sure this is a configuration issue. Question is: where do I find/set that? His network OS is Windows 2016 Server. My web database is using a Linux OS iirc. tia, --Mike Here's the weird fix: instead of using a MEDIUMTEXT field, it worked just fine when I changed it to TEXT fields. Now MEDIUMTEXT is supposed to handle LARGER #s of characters, but in this case, just TEXT should suffice. Still...wonder why the ODBC (originally 3.51, then I upgraded to the latest 64-bit MariaDB driver) has a problem with MEDIUMTEXT on this Windows 2016 Server? My other database (where no issues at all) operates on a Debian Linux OS. Thoughts? ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/8526cee0d3a1d55f364dbe029a95e...@mbsoftwaresolutions.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Re: MariaDB limitation on memo fields -- caps out at 255
On 2019-02-18 18:07, Fred Taylor wrote: Mike, Are you sure it's not a TINYTEXT field? TINYTEXT is 0 to 255 chars. TEXT is 65,535 And MEDIUMTEXT is 16,777,215. Fred I'll double-check but I'm thinking it's my connection string OPTIONS value. ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/64a6e2b22c31b10dba7d051fcc6c1...@mbsoftwaresolutions.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Re: MariaDB limitation on memo fields -- caps out at 255
Mike, Are you sure it's not a TINYTEXT field? TINYTEXT is 0 to 255 chars. TEXT is 65,535 And MEDIUMTEXT is 16,777,215. Fred On Mon, Feb 18, 2019 at 1:48 PM wrote: > My VFP9SP2 app connects to my web database with no issue. My client > wanted to host the database on his network there so I installed MariaDB > there and everything seemed to fire up just fine. HOWEVER, there's a > problem with the memo fields capping at length=255. Given that it works > with a different (my web) MariaDB database, I'm sure this is a > configuration issue. Question is: where do I find/set that? > > His network OS is Windows 2016 Server. My web database is using a Linux > OS iirc. > > tia, > --Mike > [excessive quoting removed by server] ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/cajcbkspcma+4hwslqklc6yzoxdbf-mgfohx74wruujk7t0u...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
MariaDB limitation on memo fields -- caps out at 255
My VFP9SP2 app connects to my web database with no issue. My client wanted to host the database on his network there so I installed MariaDB there and everything seemed to fire up just fine. HOWEVER, there's a problem with the memo fields capping at length=255. Given that it works with a different (my web) MariaDB database, I'm sure this is a configuration issue. Question is: where do I find/set that? His network OS is Windows 2016 Server. My web database is using a Linux OS iirc. tia, --Mike ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/497fb3eb15f3d608fb2d07fc0e4f1...@mbsoftwaresolutions.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
