DAOMedge Files

NOTE:

This is a simple, fully documented, POJO using, light weight, fast, thoroughly tested, data access library with a code generator.

DAOMedge targets Java 17 and doesn't, strictly speaking, conform to the DAO pattern. It was developed over many years and simply works well as it is. Although DAOMedge is compiled to Java 17, you can run it using later JDKs and it will compile to that JDK (see the status label on the bottom of the screen).

For convenience the daomedgegen uses the latest daomedge.jar, but without the version number and date. This is useful to keep the projects together. You just really need the generator binary (which will be daomedgegen-11.0.0-31012026.zip) as that has daomedgegen.jar, daomedge.jar (in lib/), the reservedwordsmap.properties (for syntax highlighting and reserve word avoidance), documentation, and a slightly less cheesey icon than earlier.

The actual daomedge.jar has a version number in the file name but you can use either one.

I've attempted to ensure the documentation is extensive and up to date. You can grab either the source (daomedge.odt) or the compiled version (daomedge.pdf)
They are also in the source and compiled zips respectively.

There are entries in the supporting documents (manual and READMEs) that might sound condescending but that is because I have made these mistakes so I keep adding to the documentation to remind me.

Known Issues
There is a weird issue when adding the first interface, sometimes it works, other times it fails and doesn't show up even though it is there (if you attempt to add the interface again it tells you that it is already there) I think it is a race condition, but am not sure. If you attempt to add another interface it fails with an index out of bounds exception. To get around this simply exit and restart.

Bash script to run the generator:

  #!/bin/bash  
  cd /folder/daomedge/daomedgegen/  
  java -Xmx2g -jar daomedgegen.jar

Bash script to run the generator command line interface:

  #!/bin/bash  
  cd /folder/daomedge/daomedgegen/  
  java -Xmx2g -jar daomedgegen.jar my_database

Or even:

  #!/bin/bash  
  cd /folder/daomedge/daomedgegen/  
  java -Xmx2g -jar daomedgegen.jar $*

---

Sample Code

---

Simplest:
List<Customer> customers = dao.select(Customer.class);

Pattern Matching:
Customer c = new Customer();
c.setSurname("Smith");
List<Customer> customers = dao.select(c);

Sort and Filter:
daotable table = dao.getTable(Customer.class);
daoproperty property1 = dao.getProperty(Customer.class, Customer.SURNAME);
daoproperty property2 = dao.getProperty(Customer.class, Customer.GIVENS);
OrderBy orderBy2 = new OrderBy(property2);
SelectColumn column1 = new SelectColumn(property1);
SelectColumn column2 = new SelectColumn(property2);
Filter filter = new PropertyFilter(table, property1, "Smith");
List<Customer> customers = dao.select(table, new SelectColumn[]{column1, column2}, filter, new OrderBy[]{orderBy2});

NotSQL Limits Simpe queries can only have one table's columns in the get clasue.
Multi-table queries cannot use the * syntaxt.
Aggregate queries need the operand and value (even if it is != null or similar)

The Script
set classbase my.business;

{Query1}
get database.Customer.*
filter (database.Customer.surname = Smith | database.Customer.surname = 'Jones') & database.Customer.givens = 'John'
sort home.Person.dateOfBirth >;

{Query2}
sort home.Person.dateOfBirth >;
filter (database.Customer.surname not in [Smith, Jones) & database.Customer.givens = 'John'
get database.Customer.*

The Code For NotSQL
SimpleNotSQL notsql = new SimpleNotSQL(dao, notSQLScriptFromAbove);
List<Customer> customers = notsql.selectNotSQL("Query1");
customers = notsql.selectNotSQL("Query2");
// OR
customers = notsql.selectNotSQL(0);
customers = notsql.selectNotSQL(1);

Grab the latest documentation for a full list of examples.

---

Version 11.0.0 changelog

---

Treat weird data types as strings where possible which, now, includes UUIDs. Stops the IllegalArgumentException from being thrown.
Propagate the UnsupportedJavaVersionError to the top so it doesn't fail silently if you've generated to a newer java version than the project you are using it in.
Added validators to the DAO to be called, if configured, on insert or update throwing a ValidationException (which extends DAOException).
New syntax in extn for the validators, so we increment the major version number. Version 10 extn files will automatically be updated.
Added extra hoops you need to go through the edit the class path to ensure you do not remove a jar that is in use.
You can delete the import, remove the jar from the class path, then undelete the import. This will break the build, but I can't hold you hand too much :).
Code previews are now searchable.
Setting Max. Rows to zero or blank now displays all of the rows.
As I now use GIT and the documentation also lists the changes I removed the history from the source code.
You can now set the time zone (zoneid) on the DAOConnector when dealing with java time API.
Noticed that the "Home Page" link in the about dialog was pointing to the old home page.
Generating more than one at a time now doesn't confuse the output panel.
HTML edit panes in dialogs are set to the default colour.

11.0.0 was released on 31-Jan-2026

---

Known Issues

---

In version 11.0.0 I introduced a check against used imports. If you have an import from another jar file that has the same package name, the 'Show Usage' dialog will incorrectly list it as being in use.

If you started a genrator project from scratch then you might have encountered a NPE when setting up a new class path. This is because when you click on the "Class Path Jars" button the class path string is initially NULL. After a save/exit, however, it is set to blank and the NPE no longer happens. This was fixed in 11.0.1.

e.g. I have two jars, both have the same utilities package so both are flagged as being in use.