Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JDBC Type inference should not fail #18

Open
mitalia opened this issue Apr 4, 2013 · 0 comments
Open

JDBC Type inference should not fail #18

mitalia opened this issue Apr 4, 2013 · 0 comments
Labels

Comments

@mitalia
Copy link
Contributor

mitalia commented Apr 4, 2013

When getting JDBC types from the database (e.g. for creating a table based off a query), DataExpress needs to use the metadata to ascertain what the type is. In most cases this is not an issue, but there are rare cases where this can fail. In one example case, SQLite will report a JDBC "Null" type for the column data type. For other databases, stored procedures may make it impossible to determine the type. For these scenarios, rather than total failure, DataExpress should warn that the type is not fully supported. The column on the new table should be created as a VARCHAR and then the data values should be coerced. The question remains what the view size of the VARCHAR should be, bu this likely can come from the database metadata's maximum VARCHAR size.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant