[MDEV-13503] CONNECT engine table_type=JDBC no data showing for NTEXT datatype Created: 2017-08-11 Updated: 2017-10-26 Resolved: 2017-08-12 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - Connect |
| Affects Version/s: | 10.1.26 |
| Fix Version/s: | 10.0.33, 10.1.27, 10.2.8 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Robert Dyas | Assignee: | Olivier Bertrand |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Centos7 |
||
| Description |
|
When using the Microsoft JDBC driver, columns of type NCHAR and NVARCHAR now are being returned in SELECT statements (as of 10.1.26), but if a column is defined as NTEXT it is blank (columns defined as TEXT do work correctly). For testing see the connection info provided privately earlier, the new table is called: all_types but all the connection info remains the same. |
| Comments |
| Comment by Olivier Bertrand [ 2017-08-11 ] |
|
Which table should I test having NTEXT columns? Note that NTEST, TEST and IMAGE types are not defined as JDBC types. The corresponding SQL types are deprecated and will be remove in future versions of SQL Server. |
| Comment by Robert Dyas [ 2017-08-12 ] |
|
table: all_types SELECT myntext FROM all_types |
| Comment by Olivier Bertrand [ 2017-08-12 ] |
|
fixed 10.1 version should be 10.1.27. |
| Comment by Robert Dyas [ 2017-08-12 ] |
|
At the top of this, why does the Fixed Versions not include 10.1.27 ?? (it says only Fix Version/s: |
| Comment by Olivier Bertrand [ 2017-08-12 ] |
|
Because it was not in the drop down list when I closed this case! This is why I included it in my previous comment. |
| Comment by Robert Dyas [ 2017-08-12 ] |
|
Smells ripe for not being included in the build again |