#191 Use long for row count in meta data

[pothoven]

I have some tables with larger numbers of rows in them. When I try to generate the SchemaSpy models I get this error because there are more than 2,147,483,647 (max int) rows in the table. Could you change it to use a long instead?

Gathering schema details...java.lang.NumberFormatException: For input string: "2452632343"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.lang.Integer.parseInt(Integer.java:583)
at java.lang.Integer.parseInt(Integer.java:615)
at net.sourceforge.schemaspy.model.Database.getBasicTableMeta(Database.java:366)
at net.sourceforge.schemaspy.model.Database.initTables(Database.java:232)
at net.sourceforge.schemaspy.model.Database.<init>(Database.java:71)
at net.sourceforge.schemaspy.SchemaAnalyzer.analyze(SchemaAnalyzer.java:211)
at net.sourceforge.schemaspy.Main.main(Main.java:42)

[Rafal Kasa]

Hi pothoven

Please verify version https://github.com/schemaspy/schemaspy/releases,
if taht issue still exist please report it on Github.

Best Regards
Rafal

[pothoven]

Yes, it is still a problem in the new beta.

Using database properties:
[schemaspy-6.0.0-beta.1.jar]/org/schemaspy/types/mysql.properties
Gathering schema details...java.lang.NumberFormatException: For input string: "2827140533"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.lang.Integer.parseInt(Integer.java:583)
at java.lang.Integer.parseInt(Integer.java:615)
at org.schemaspy.service.DatabaseService.getBasicTableMeta(DatabaseService.java:381)
at org.schemaspy.service.DatabaseService.initTables(DatabaseService.java:81)
at org.schemaspy.service.DatabaseService.gatheringSchemaDetails(DatabaseService.java:48)
at org.schemaspy.SchemaAnalyzer.analyze(SchemaAnalyzer.java:175)
at org.schemaspy.SchemaAnalyzer.analyze(SchemaAnalyzer.java:83)
at org.schemaspy.Main.main(Main.java:52)

[Rafal Kasa]

Hi pothoven

Thank you very much for your time and verification version schemaspy-6.0.0-beta.1
I confirm this bug, and it will be fixed in next version planed on 23 Dec 2016.

I created releated issue to this topic on github https://github.com/schemaspy/schemaspy/issues/23

[Rafal Kasa]

Hi pothoven

The new version schemaspy-6.0.0-beta.2 was released you can download and tested.
https://github.com/schemaspy/schemaspy/releases/tag/v6.0.0-beta.2

[pothoven]

I can confirm that the fix works now. Thank you!