Add per-technology CData build skills (python, adonet, odbc, java) + Step 8 handoff#7
Open
justinf-cdata wants to merge 3 commits into
Open
Add per-technology CData build skills (python, adonet, odbc, java) + Step 8 handoff#7justinf-cdata wants to merge 3 commits into
justinf-cdata wants to merge 3 commits into
Conversation
Add build-phase skills that take over from cdata-cli once app code is being written, one per driver edition: - cdata-cli-python (CData Python Connector, DB-API 2.0) - cdata-cli-adonet (ADO.NET Data Provider, NuGet) - cdata-cli-odbc (ODBC Driver, DSN / DSN-less) - cdata-cli-java (JDBC Driver, reuses the cdata-cli jar) Route cdata-cli Step 8 (Generate Application Code) to them by language / driver technology, replacing the JDBC-only driver-locations block.
| - Driver class: `cdata.jdbc.<source>.<Source>Driver` | ||
| - JDBC URL: `jdbc:<source>:<connection-string>` | ||
| - License file: same directory, `cdata.jdbc.<datasource>.lic` | ||
| Steps 1–7 (connect, discover schema, validate SQL) are language-agnostic and are this |
Collaborator
There was a problem hiding this comment.
Make Java/JDBC the silent default. Unless specified by the user, use Java/JDBC as a default to avoid duplicate driver download/activate/connect/ effort.
Collaborator
Author
There was a problem hiding this comment.
per our conversation with jordan added a note about java/jdbc being the simplest option
… add discovery gate - Add Java-native foundation section to cdata-cli explaining JDBC as the underlying layer, Java as the simplest build path, and that ADO.NET/Python/ODBC editions require separate install/activation the CLI cannot perform - Update Step 8 to explicitly call out Java/JDBC simplicity vs other languages - Add discovery gate to all four build skills: invoke cdata-cli first if discovery hasn't been done yet - Fix ADO.NET install-license activation: tool always prompts for Name/Email even when a key is supplied; AI can pipe them in for trial, user runs manually for purchased key - Add existing DSN check to cdata-cli-odbc Step 3 before creating a new DSN - Add JDBC-only notices to Python, ADO.NET, and ODBC build skill prerequisites
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds four build-phase skills that take over from
cdata-clionce application code is being written — one per CData driver edition:cdata-cli-python— CData Python Connector (DB-API 2.0)cdata-cli-adonet— ADO.NET Data Provider (NuGet)cdata-cli-odbc— ODBC Driver (DSN / DSN-less; Node.js and other non-JVM languages)cdata-cli-java— JDBC Driver (reuses the jarcdata-clialready downloads)Also routes
cdata-cliStep 8 (Generate Application Code) to these skills by language/driver technology (replacing the JDBC-only driver-locations block), and updates the README (skills table + all-vs-individual install).Why
cdata-clihandles discovery (connect, schema, SQL) well; Step 8 was the seam where one generic skill had to guess at per-technology packaging, licensing, and connection idioms. Each build skill captures the non-obvious specifics: where to obtain the driver, per-edition licensing, connection idiom, and language gotchas.Notes
cdata-clistays the prerequisite; each build skill assumes discovery is done and reuses the validated SQL + connection details.