Testing Goes On: JDBC

JDBC a Go-Go

Today I tested Awesome Sauce Java with JDBC.  It works well!

There are opportunities to develop new tools and functions for the purpose of making the install, configuration, and use easier, but I'm always happy to find another feature works.  Not that it isn't supposed to.  It means that I can validate, test, then learn how to extend the feature.

Here's the code I used to connect to the Derby database in NetBeans:

(setf dbp (new Properties))
(put dbp "user" "app")
(put dbp "password" "app")
(setf cs (new String "jdbc:derby://localhost:1527/sample;create=true"))
(setf conn (DriverManager.getConnection cs dbp))
(setf stmt (createStatement conn))
(setf rs (executeQuery stmt "SELECT * from CUSTOMER"))

(while (next rs)
   (println (getString rs 4))) ; print the company name.

Results in the following detail printing:

"New Enterprises"
"Wren Computers"
"Small Bill Company"
"Bob Hosting Corp."
"Early CentralComp"
"John Valley Computers"
"Big Network Systems"
"West Valley Inc."
"Zed Motor Co"
"Big Car Parts"
"Old Media Productions"
"Yankee Computer Repair Ltd"

I wrote a function to load-tuples, to pass column names, and get a set of tuples back.  I'm going through code today, to find areas where I can add utilities, factor code, and move library code into a useful place.  A lot of the applications I've been writing have grown from prototypes, to working apps, and now they contain code that can be harvested for other applications, so the utility parts are moving into general locations.

Plan for JDBC

Once I've thoroughly tested the JDBC code, I'm going to put together a JDBC application for creating, viewing, and editing tables.  It's a relief to get JDBC validated so I can start using it and stressing Awesome Sauce Java with large datasets.  It's going to be helpful to get a sense of performance of the language in a range of cases.  Plus, I want to have applications take advantage of database-resident data.

Third Party Libraries

I'm going to add integration of third party libraries now that I've got JDBC connected.  I want to have some of the more popular libraries available with the first release of Awesome Sauce Java, especially Amazon Web Services and similar cloud-based services.  I downloaded Google's GMail and Calendar libraries to evaluate everything from licenses to libraries, but I'd like to connect my Calendar application to Google's Calendar code, so I can see if their storage model is as robust as my calendar needs :-)

Today's Plan - Android Layouts & a Graphing App

I started an application yesterday for graphically building Android application prototypes.  The first step is to map architecture and components into a set of interfaces to construct the structure of an Android application - inside and out.  The second step will be to generate code, build the project, and install the application onto a device.

The application builder might leverage Android Studio to build the Android application, by generating the project code and supporting files, but I'll see what makes the most sense to start with and see whether there is more than one path or more than one opportunity to generate working Android code.  I may also build an Android rapid prototyping application, one that's capable of taking layout details and running them right away, similar to other rapid prototyping applications.  They represent a fast mechanism to evaluate layouts when compared to building a full app.  But I also like the idea of being able to prototype fully functioning applications.

The thing I'm going after with the interface builder is the creation of multiple applications - the Android app and the Awesome Sauce Java app for starters.  The Awesome Sauce Java app will be a stand-alone Java application.  Once I have the Android builder working, I'll extend it to iPhone development.

Graphing Application

While working on the code for the Android Prototyping application I started reviewing existing code from existing Awesome Sauce Java applications that I could leverage to help build it.  There's overlap with Awesome Draw, in the event and graphics objects management code, as well as the rendering code.
Like I mentioned earlier, I'm going to be factoring common functionality into library code.

One of the more interesting parts of building a language is learning how many different layers and libraries there are for each set of functionality.
The first step has been to learn how the language works, while smoothing the rough spots and edges.

Now that the language is becoming more stable, it's possible to smooth the edges where the applications come together.  Today I'm hoping to have a cleaner Awesome Draw app, as well as a library of functions that work for it.  The libraries will also provide leverage for building the new applications I'm working on today: the Android rapid prototyping and Awesome Graphing applications.

Have a great day!

Comments

Post a Comment

Popular posts from this blog

I Was Studying Exceptions, But Got Confused, So I Luckily Designed The Code Editor Instead

I spend a lot of time doing nothing without realizing I'm doing nothing. Brain injuries are like that, I guess.  I don't think anybody knows crap about anything & 99% of life is made up and provably stupid.  Whatever.  I seem to get going between 1-4pm.  No matter how hard I try to get moving, I bounce between different tasks until the fear piques and I find something to work on and hopefully find my focus. Awesome Sauce grew too much, or too big, or my living situation is overwhelming, or something.  Because I went from highly productive to scattered right after my son fed me his mom's lentils and rice.  Hmm. That's like what happened after the cup of coffee at his piano teacher's apt. Whatever. Keep forgetting nobody cares.  Except for those people putting me on blast on their social media accounts.  I'm probably good entertainment because I'm blind and write a lot. Last week I started trying to build diagrams for Awesome Sauce Java. The...
Read more

Just a Short Update

I'm reorganizing. What that means is Awesome Sauce Java is going to become structured for release.  Since the release path is forked, the structure of the project has to provide easy configuration for shipping: Stand-alone, Java based Awesome Sauce Java apps. Hot Sauce OS style, all apps running in their own threads & managed by Hot Sauce, based configuration. So all the code is getting moved and re-Git-ified to make sure all the parts can play nice, regardless of which release is being built/updated/released. One of the things I was working on last night on the train was making sure that both release formats provide the ability to edit the application while it's running, even after release, should the developer want their users to be able to edit and modify their application. What this means is that applications need to be able to connect to the ASJ Editor or ASJ Interface Builder apps.  The app, say it's a spreadsheet, needs to be able to connect to the devel...
Read more

A Day Away From a Glowing Screen

One thing I've noticed and written about having been whacked dramatically hard in the noggin' is that my focus works but doesn't. Learning what that means has taken observation and time. The difficulty is that I have to observe while I'm doing, but while I'm doing, I'm concentrating on what I'm doing, not on observing. Why do I suddenly feel like I'm writing what I read years ago from J. Krishnamurthi? Every once in a while, I do something that allows me to see detail from a different perspective.  When I'm really fortunate, I get the chance to see from a high-level perspective.  Like yesterday.  Because it helped me to see, again, how I focus on things that are mostly on the table in front of me. I took the day off from the computer yesterday and worked on paper.  It was depressing.  Because it highlighted how regimented and tiny my world is.  I have four places to go: the library, Whole Foods, Starbucks, & my racoon-stank room (that I...
Read more