Sqlite mac os x tutorial free#

You’ll start by creating a table in the database for your sample data. The application you’re going to make takes a CSV file as its input (found in the sample files provided), and adds the data to the SQLite database you were just working with. They are single files which can take an input by drag and dropping a file or folder onto them: This can become confusing when using a Folder Action, so for this lesson you’re going to make an Application.Īpplications are just like every other application in your applications folder. You could use a Folder Action to handle this, but the sample project requires you to work with multiple files of different natures, specifically a CSV file and a SQLite database. There may be occasions where you need to add sample data to a database or multiple databases - like when you’re making a demo or testing a new app. Making a standalone application to add data from CSV to Database It’s also possible to just use the Results section at the bottom of each action. Note: Use with care, as it’s not unusual for View Results to change the format of a string before it reaches output.

The output of the Get Specified Finder Items action will be the filepaths of all files included in the action. For example if you were to drag it above Execute SQL, the result would be something like:

Sqlite mac os x tutorial free#

You can now see the results of the SQL query in plain text.įeel free to experiment with the View Results action to fully understand what the output of each action is. You don’t need to put anything into this box as just a place to display information.Ĭlick the Run button at the top right to see what happens. If you’re working on much bigger workflows, or need instant feedback of what the current output is then this action is useful.ĭrag the View Results action from the library onto your workflow under Execute SQL. So far you’ve made a lot of assumptions based on what you believe the current variables being passed to the output to be. Now what you need is to be able to see the results returned by the query. In this case it should contain one line for each entity model you’ve set up. When this action runs, its output will be the result of the query.