I have a table with the column structure as seen below
I create a wpDataTable with the following query
SELECT * FROM `view_name`
and the results are modified column types.
I need the column type to be persistent as when I created the table - so I dont have to go through thousands of column types and modify them. Or at least have the option to set the column types automatically when creating the table.
As far as I know, this is the plugin's default behavior when attempting to "guess" the correct data type. It does so by analyzing the first several rows of each column as they come from the data source.
Currently, there is no built-in way to change this.
However, I will check with our QA team to confirm and conduct additional testing to ensure accuracy.
2. Regarding manually pre-determining each column's data type before table generation:
This is only possible for Manual Tables. When you create a new manual table, it generates a standalone SQL table in the database with its own set of columns and rows.
As a result, you can define each column type in advance, which determines how the fields are created in the database.
On the other hand, for other table types—such as SQL Query-based tables—our plugin simply pulls the data and tries to "guess" the correct data type, as mentioned earlier.
We’ll follow up as soon as we have additional insights.
It does not make sense. Cant the backend scrip check the schema of the requested table/view? Also, the "guessing" algo isnt working well. See the attached screenshots showing the same data - in PhpMyAdmin the wpDataTable import view. I tried changing the column names to not "look" like numbers, and it does not really work. Why does the wpDatatable import converts decimal values to a date? It makes no sense.
Thank you for sharing your feedback. I completely understand your frustration, and I appreciate your detailed input on how our SQL parser handles column type detection.
As mentioned, our SQL feature is designed as a custom PHP & SQL parser, which inherently has certain limitations. Unlike a full-fledged database management system, it uses an internal logic to determine column types based on the first few rows of data.
As you pointed out, factors such as NULL values, header formats, and data patterns influence how the parser interprets each column.
I’ve forwarded your concerns to our development team and management for review.
I’ll also check if our developers can provide more insights into how the current logic works and whether improvements can be made.
I can't promise anything, but if one of our developers finds the time soon to provide more details on how that part of our parser logic works, I will report back and share them with you.
If you have specific suggestions on how this process/logic could be improved, I encourage you to submit a feature request on our suggestions page. If a similar request already exists, you can upvote it to help prioritize it for future development.
Additionally, you can stay updated on any changes, bug fixes, or new features through our changeLog page, (also available in the plugin dashboard), or by subscribing to our newsletter.
I have a table with the column structure as seen below
I create a wpDataTable with the following query
SELECT *
FROM `view_name`
and the results are modified column types.
I need the column type to be persistent as when I created the table - so I dont have to go through thousands of column types and modify them. Or at least have the option to set the column types automatically when creating the table.
Attached files: wpdatatable modified column types screenshot.JPG
table column definition.JPG
Hi Michael,
Thank you for reporting this.
As far as I know, this is the plugin's default behavior when attempting to "guess" the correct data type. It does so by analyzing the first several rows of each column as they come from the data source.
Currently, there is no built-in way to change this.
However, I will check with our QA team to confirm and conduct additional testing to ensure accuracy.
2. Regarding manually pre-determining each column's data type before table generation:This is only possible for Manual Tables. When you create a new manual table, it generates a standalone SQL table in the database with its own set of columns and rows.
As a result, you can define each column type in advance, which determines how the fields are created in the database.
On the other hand, for other table types—such as SQL Query-based tables—our plugin simply pulls the data and tries to "guess" the correct data type, as mentioned earlier.
We’ll follow up as soon as we have additional insights.
Kind Regards,
Miloš Jovanović
[email protected]
Rate my support
Try our FREE mapping plugin! MapSVG - easy Google maps, interactive SVG maps and floor plans, choropleth maps and much more - https://wordpress.org/plugins/mapsvg-lite-interactive-vector-maps/
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
Hello Milos,
It does not make sense. Cant the backend scrip check the schema of the requested table/view? Also, the "guessing" algo isnt working well. See the attached screenshots showing the same data - in PhpMyAdmin the wpDataTable import view. I tried changing the column names to not "look" like numbers, and it does not really work. Why does the wpDatatable import converts decimal values to a date? It makes no sense.
Attached files: wpDataTable Imported.PNG
PhpMyAdmin.PNG
Hi Michael,
Thank you for sharing your feedback. I completely understand your frustration, and I appreciate your detailed input on how our SQL parser handles column type detection.
As mentioned, our SQL feature is designed as a custom PHP & SQL parser, which inherently has certain limitations. Unlike a full-fledged database management system, it uses an internal logic to determine column types based on the first few rows of data.
As you pointed out, factors such as NULL values, header formats, and data patterns influence how the parser interprets each column.
I’ve forwarded your concerns to our development team and management for review.
I’ll also check if our developers can provide more insights into how the current logic works and whether improvements can be made.
I can't promise anything, but if one of our developers finds the time soon to provide more details on how that part of our parser logic works, I will report back and share them with you.
If you have specific suggestions on how this process/logic could be improved, I encourage you to submit a feature request on our suggestions page.
If a similar request already exists, you can upvote it to help prioritize it for future development.
Additionally, you can stay updated on any changes, bug fixes, or new features through our changeLog page, (also available in the plugin dashboard), or by subscribing to our newsletter.
Thanks again.
Kind Regards,
Miloš Jovanović
[email protected]
Rate my support
Try our FREE mapping plugin! MapSVG - easy Google maps, interactive SVG maps and floor plans, choropleth maps and much more - https://wordpress.org/plugins/mapsvg-lite-interactive-vector-maps/
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables