One project every month - making stuff better ...

GITHUB_UTL Tutorial 10: Even more data from github in sqlplus!

More on selecting data directly from your github repository, this time. So one of the things I have done since my last post, was replacing and refactoring the code that fetches data from the github api. This change has made it even more easy to get information displayed directly in sqlplus. What this also means though, is that you have to re install the entire github schema. But I have created an easy single install script, so simply log on as sys and execute the install.sql from the latest release, and you should be up and running in no time. So this time I will show you some of the selects that you can run inside of oracle to query your github repository.

GITHUB_UTL Roundup and status.

As a roundup, here is a list of all the blog entries I've done so far on the github_utl package. The project was fun, and I got to do a lot of github things, I had not done before. The reason that I even started out with github, was of course because of an incident :). A couple of months back I lost my primary and backup harddrive within an hour ... Bummer. So I lost one specific project I had been working on for close to 1 and a half years. So then I decided that all my code, from there on, should always be pushed to the cloud. The reason I chose GitHub, was simply because I had just downloaded another project from there, and it seemed easy to integrate into the OS using their API's.

GITHUB_UTL Tutorial 8: Fully automated github tracking of your PLSQL code.

This tutorial will try and see how you could implement an automatic push of your code, to a repository whenever that code changes. This could easily be implemented in a development environment, so that the chance of loosing code, is kept to a minimum. Most sites do not do backups of dev environments in the same frequency (or ever) as they do with production environments.

GITHUB_UTL Tutorial 9: Automatic github issues for error tracking

This is just going to be a short entry. In the last tutorial I showed you how to enable automatic revisioning of all your plsql code in an oracle schema. What you can also do with the github_utl package is setup automatic issue creation for schema errors. This basically means that you will get an issue in the right repository, every time a servererror happens in that schema. This makes it extremely easy to track if there are any logical errors with your code, or if your users are trying to use it the wrong way.

GITHUB_UTL Tutorial 7: Easy push of code and easy diff of code.

Today I will introduce a couple of new packages as well as show more of the integrated select functionality. The main new package I will show is a utility package to better use the base API functionality for something meaningfull. We will use these utilities to populate our GitHub repository with all our code, and also to detail the status between our live code and what lives in the repository.

GITHUB_UTL Tutorial 5: Selecting information from GitHub.

How do you use the GITHUB_UTL package to select information from your account? You can use the github_tables package, which is basically a collection of pipelined functions that uses the rest of the api to get information out in a row based fashion. So fire up your sqlplus and login as the user that installed the github packages.

GITHUB_UTL Tutorial 4: Creating issues and updating them.

In this tutorial I will take a look at how to create issues against existing projects. This is a nice feature of GitHub since it lets us track issues directly where we have the code located. The first thing we will do is create a new issue.

GITHUB_UTL Tutorial 1: Installation

Using GITHUB_UTL is very easy once it has been installed in the database, but to have it up and running requires some initial steps. To help you get started, here is a complete guide to get started.

GITHUB_UTL First real push

So my second codemonth project is a plsql framework, to integrate with the github api. What is basically allows you, is to push stuff from your database into github for version control.