Enter one-line summary

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Non-nullable columns with defaults in db will be generated as required
2.
3.

What is the expected output? What do you see instead?
Expect to see non-nullables with default values not required.

What version of the product are you using? On what operating system?

Please provide any additional information below.

Original issue reported on code.google.com by cfsile...@gmail.com on 25 Feb 2007 at 3:06

[GoogleCodeExporter]

This would require a the db metadata have knowledge of the default and will 
require
changes to the mysql, mssql and oracle support components. I plan to have this
resolved for a 1.0 release candidate.

Original comment by brian.ri...@gmail.com on 27 Feb 2007 at 2:37

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Original comment by brian.ri...@gmail.com on 27 Feb 2007 at 2:38

• Changed state: Accepted

[GoogleCodeExporter]

Just an FYI. I have coded a fix that will be committed this weekend. Basically 
if a
column has a default value in the database, it is considered nullable even if 
the
column is set to not allow nulls (ok that wording is awkward but I think you 
get my
point).

I will need someone to confirm the fix for oracle.

Original comment by brian.ri...@gmail.com on 9 Mar 2007 at 7:56

• Changed state: Started

[GoogleCodeExporter]

These changes have been committed to SVN. I have tested the MSSQL and MySQL 
version
but do not have Oracle to test.

Original comment by brian.ri...@gmail.com on 9 Mar 2007 at 11:54

• Changed state: Fixed