Skip to content

Conversation

@raphaelahrens
Copy link
Contributor

In #234 @colesmj suggested to move the import of pydal into the sqlDumb function.
This commit does this and if the import fails raises an UIError with an explanation on how to proceed.
The text is just a first draft.

To move the import the function get_table was also moved inside the sqlDump function.

@raphaelahrens
Copy link
Contributor Author

Maybe you could add an explanation in the readme with instructions on how to proceed, which then can be linked in the error message.

In OWASP#234 @colesmj suggested to move the import of pydal into the sqlDumb
function.
This commit does this and if the import fails raises an UIError with an
explanation on how to proceed.
The text is just a first draft.

To move the import the function get_table was also moved inside the
sqlDump function.
@izar
Copy link
Collaborator

izar commented Mar 13, 2024

Love the Freudian slip in the commit message :)
What happened to lines 1215-1223 ?

@raphaelahrens
Copy link
Contributor Author

Love the Freudian slip in the commit message :) What happened to lines 1215-1223 ?

The function was moved from the the class into the method sqlDumP.
Since the get_table method is not using self and is only used inside of the sqlDump method. This was necessary because of the use of pydal.Field.

@izar izar merged commit c4a81a4 into OWASP:master Mar 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants