Importing schema from "Import Database Schema" dialog issues/suggestions (#9779)

Hello,

I have a few suggestions about generating Java classes from database schema from Hibernate Facet (Generate Persistence Mapping -> from Database Schema):

• I noticed that IDEA treats found Oracle sequences as tables, offering to generate Java class and mapping which is, I think, useless:

     <class name="foo.BarSeqVO"
           table="BAR_SEQ" schema="BV"/>
     Java class:
     public class BarSeqVO {
     }

• IDEA uses "mapped" composite primary keys:
  

     //generated PK
     public class FooVOPK{
          private Long key1;
          private Long key2;
          ///getters, setters
     }
     //generated VO

     public class FooVO{
          private Long key1;
          private Long key2;
          ///getters, setters
     }

    It would be convenient if the policy for generating composite-id was parametrized. As in Hibernate documentation, there are three approaches: http://www.hibernate.org/hib_docs/reference/en/html/mapping.html#mapping-declaration-compositeid

     //generated PK
     public class FooVOPK{
          private Long key1;
          private Long key2;
          ///getters, setters
     }
     //generated VO

     public class FooVO{
          private FooVOPK id;
          //getters, setters
     }

    <composite-id name="id" >
        <key-property name="key1"/>
        <key-property name="key2"/>
    </composite-id>

</class>

• could IDEA generate property/id/key-property "type" attribute (with the same value as "Mapped Type" column in the dialog)? It is optional, but if ommitted, Hibernate has to use reflection to guess.
• a checkbox (similar to "prefer primitive types") to prefer java.util.Date over java.sql.Date for date columns would be really nice.
• I noticed that char(1) columns are mapped to java.lang.Boolean by default. I think java.lang.Character/java.lang.String would be better