Fix - "VALUES: rowvalues #1: rowvalue #2: types.MDString has no SQL representation" Error #520
Conversation
This file contains 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
|
Woah @maxdemaio, sorry I just saw this – small request actually if you're touching this file! Do you think you could also update the generator to account for the new NoteRepresentable struct as well? It's part of Definitions. We can put it in a |
Nickersoft
approved these changes
Jan 11, 2024
Nickersoft
deleted the
519-odict-dump-error-sql-values-rowvalues-1-rowvalue-2-typesmdstring-has-no-sql-representation
branch
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
These changes will allow us to dump odict files to SQL format by fixing the issue with markdown formatted values in
Descriptions andDefinitionValues.I think this will be one step further to getting a docker-compose file for our web repo! This closes #519
Steps to reproduce
examples/example2.xmlto odict formatgo run odict.go d -f postgres examples/example2.odict examples/output.sql