Java generics were introduced in 2004 with Java 5. It has been around for eight years now, but Java generics still pose problems for experienced developers and newcomers alike. Beginners often find Java generics to be counterintuitive. I think it must be difficult to learn Java generics if you don't have the pre-generics perspective first. It's hard to understand some of Java generics' limitations if you don't have a firm grasp of Java code without generics. Experienced developers often have only a rough idea of what Java generics do. They don't want to dig into the details and are often surprised by generics behavior. Today we'll take a look at some of those surprises.
You have database schema. You have generated Java code (by OneWebSQL, of course). You have started developing an application. You're missing something -- the data in the database. Your database is empty. There are only tables, no rows.
In real-world applications, a database model can have a few hundreds of tables and views. How can you make such a diagram more readable? A solution is to color the entities in the diagram.
If you wish to color your ERD Diagrams, here is how you can do it in PowerDesigner.
If you wish to color your ERD Diagrams, here is how you can do it in Oracle Data Modeler (aka Oracle SQL Developer Data Modeler).
If you wish to color your ERD Diagrams, here is how you can do it in ERwin.
In this post I will show you three ways to crash your IDE using Java wildcards. If you are impatient, just download the file InstantCrash.java, open it in your IDE and compile.