This essay does not describe an existing computer program, just one that should exist. This essay is about a suggested student project in Java programming. This essay gives a rough overview of how it might work. I have no source, object, specifications, file layouts or anything else useful to implementing this project. Everything I have prepared to help you is right here.
This project outline is not like the artificial, tidy little problems you are spoon-fed in school, when all the facts you need are included, nothing extraneous is mentioned, the answer is fully specified, along with hints to nudge you toward a single expected canonical solution. This project is much more like the real world of messy problems where it is up to you to fully the define the end point, or a series of ever more difficult versions of this project and research the information yourself to solve them.
Everything I have to say to help you with this project is written below. I am not prepared to help you implement it; or give you any additional materials. I have too many other projects of my own.
Though I am a programmer by profession, I don’t do people’s homework for them. That just robs them of an education.
You have my full permission to implement this project in any way you please and to keep all the profits from your endeavour.
Please do not email me about this project without reading the disclaimer above.
Writing SQL (Standard Query Language) is tedious and error prone. It requires memorising equivalents between Java and SQL and the corresponding conversion functions each way. Further, the details of the SQL and JDBC (Java Data Base Connectivity) you write on the particular implementation of SQL you use.
Your mission, should you choose to accept it, is to write an SQL amanuensis. It generates SQL and Java source code for you.
You write a Java class with one field for each column in the corresponding SQL table. You feed either the Java source code or the compiled class file to your utility. It parses it and spits out:
The code does not need to be complete. You could tweak it after it is generated to adjust which fields you want to use as keys, or you might include magic comments or magic field names in the class code to give the generator a hint which fields to use as keys, or you might just use a convention that the first n fields are keys and you specify n to the generator.
SQLStomp is not a scheme like Hibernate that takes over your project. It is merely a tool you use to write code in shorthand. It leaves nothing behind. It has no runtime footprint. The results are not that different from if you hand coded.
You could also write a utility that starts with a SQL table definition and generates the Java class. This is the more logical way, though more difficult way to do it, it because:
This is ultra-lite version of what Hibernate and ORMs (Object Relational Mappings) do.
This page is posted
Optional Replicator mirror
Your face IP:[126.96.36.199]
You are visitor number|