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

Database Connections #138

Closed
karthikshashi opened this issue Jul 15, 2019 · 19 comments
Closed

Database Connections #138

karthikshashi opened this issue Jul 15, 2019 · 19 comments

Comments

@karthikshashi
Copy link

Wonderful work that you have done. Could you please add a Database functionality as well in your upcoming release. Also some text file options to trim / parse text will be of great help.

@saucepleez
Copy link
Owner

Hello,

We can look at adding Trim text. What do you mean by parse text? Also how do you imagine the database functionality working?

@humbertoanascimento
Copy link

Hi,

Could I participate this discussion? I work with some RPA tools.

The database could be compatible with generic driver connections, like DBeaver: you define the driver path the program and set others generals and specific configurarions. Thus is possible to use any desired driver.

Besides DB connection, is need some exception treatment that could be more generic, like a try-catch. This way is possible to define the behavior of automation when this case occur.

@saucepleez
Copy link
Owner

Hi,

Sure. So to do this we can look at implementing 4 commands (off the top):

  • Connect
  • Execute Stored Procedire
  • Execute Query
  • Disconnect

In terms of try-catch, we can look at implementing that for all commands, that should probably be a separate work item.

@shiddugmail
Copy link

shiddugmail commented Jul 18, 2019 via email

@karthikshashi
Copy link
Author

Hi,

Sure. So to do this we can look at implementing 4 commands (off the top):

  • Connect
  • Execute Stored Procedire
  • Execute Query
  • Disconnect

In terms of try-catch, we can look at implementing that for all commands, that should probably be a separate work item.

  • For the Connect action, it will be good to have information collected in different fields and then join them to create a connection string at real time. The password field can then be invisible / encrypted.
  • In the Execute Stored Procedure, the connection name will need to be available to specify which DB stored connection to run the query on.
  • Execute query action could be similar to Execute Stored Procedure and will be good to subscribe input from the output of a previously run object / action in the workflow.
  • Disconnect - Once a query is completed, session generally terminates.

Compatibility : SQL first and My SQL later?

This will be too good a functionality to have and thanks a ton.

@saucepleez
Copy link
Owner

@karthikshashi

Agreed. I think for the connect command we can use the data link builder:

image

This way we can support compatibility for most databases -- users will simply need to install the providers onto their machine. I started work on this but ran into a few bumps

@saucepleez
Copy link
Owner

Ok @karthikshashi, I have added the define connection and initial query commands using OLEDB.

Here is sample SQL Data Source:
image

Here is sample command to retrieve data:
image

Here is the result:
image

@saucepleez
Copy link
Owner

@karthikshashi @humbertoanascimento I have added database commands as well as try/catch/finally/end try. Please open new issues if you need help or encounter any problems, thanks.

@karthikshashi
Copy link
Author

karthikshashi commented Jul 31, 2019 via email

@karthikshashi
Copy link
Author

karthikshashi commented Jul 31, 2019 via email

@humbertoanascimento
Copy link

@saucepleez Its stunning your agility and fast answers! I will try the latest version tonight. Very thanks for these new features!

@saucepleez
Copy link
Owner

saucepleez commented Jul 31, 2019

@humbertoanascimento @karthikshashi Are you building from source code? If not, I will further test and release a compiled binary. The changes are active in the DEV branch as of now. I can create a test build, I generally release Friday - Sunday.

@karthikshashi
Copy link
Author

karthikshashi commented Jul 31, 2019 via email

@saucepleez
Copy link
Owner

@karthikshashi I will build a 3.1.0.0 binary tonight EST.

@saucepleez
Copy link
Owner

@karthikshashi Please see latest release preview

@karthikshashi
Copy link
Author

karthikshashi commented Aug 1, 2019 via email

@saucepleez
Copy link
Owner

@karthikshashi

What was the issue Symantec gave? This was the first build through Azure Pipelines. Binary should be signed.

@atotalnoob
Copy link
Contributor

@saucepleez test the binary in a vm

@saucepleez
Copy link
Owner

@atotalnoob There is no issue with the binary, the issue is with Symantec probably because it has not seen this file "in the wild" yet. Symantec does not offer whitelisting for developers so the only course of action will be for @karthikshashi to manually build the project until Symantec begins to trust the zip file.

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

No branches or pull requests

5 participants