ftMemo moved to ftBlob export section at DataSetToJSONArray and DataSetToJSONObject methods #198
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
MarcosFincotto
changed the title
MarcosFincotto
changed the title
|
Qual a finalidade de mover o ftMemo para junto do ftBlob? Acho que isso pode trazer problemas para quem já usa atualmente, visto que ftMemo é uma string, e o ftBlob é um binário. São informações diferentes. |
|
Isso foi discutido no telegram. O campo do tipo BLOB e subtype TEXT está sendo exportado como string, pois vc criou uma variável com max_length lá. Movendo para o ftBlob é forçado a serialização para base64. Se puder olhar no canal e pesquisar por ftMemo está lá o contexto.
|
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.
ftMemo moved to ftBlob export's sections