Book a Demo

Author Topic: Can't Reset unknown DBMS type  (Read 3612 times)

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Can't Reset unknown DBMS type
« on: January 07, 2009, 06:31:10 pm »
If the DB is not set (or not recognized) on the package when reverse engineering a DB, the DB displayed in the Database Dropdown for a table is set to null.  However, there is no option on the Reset DBMS Options to change from a current NULL DBMS to something else...

Now, if the DB is NOT set, then you can't set the Foreign Keys (reasonable enough).  However, since you can't reset the DBMS - you're snookered...

The corresponding Code Language dialog has the <All> entry - which DOES allow language resetting from Null...

Reported,
Paolo
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

«Midnight»

  • EA Guru
  • *****
  • Posts: 5651
  • Karma: +0/-0
  • That nice Mister Grey
    • View Profile
Re: Can't Reset unknown DBMS type
« Reply #1 on: January 08, 2009, 02:29:45 am »
But if the DBMS is not set code generation may produce bizarre results. Almost certainly not what was expected or required.
No, you can't have it!

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: Can't Reset unknown DBMS type
« Reply #2 on: January 08, 2009, 01:08:09 pm »
Quote
But if the DBMS is not set code generation may produce bizarre results. Almost certainly not what was expected or required.
This was just about Reverse Engineering...  I didn't even get as far as DDL Generation!  ;)

I would have thought that if you reverse engineer and set a value in PDATA2 that is NOT in the list of (currently) supported technologies for this instance of the repository.  (This particular model has a provenance SO old that SQL Server 2005 wasn't on the list of DBMSs!).  EA should warn the user that is, in fact, what is happening...  It should suggest that the user update the list to the latest version (which we've now done by exporting and importing the DDL data types from an 834 build).

But the problem is still that if you try and RE a DBMS that isn't even on the latest list, you may want to change the DBMS technology, so my request to provide the ability to change from <Any> (not <All> as <Any> is better semantics, I think) to a desired value is still pertinent.

Paolo
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

«Midnight»

  • EA Guru
  • *****
  • Posts: 5651
  • Karma: +0/-0
  • That nice Mister Grey
    • View Profile
Re: Can't Reset unknown DBMS type
« Reply #3 on: January 09, 2009, 10:25:47 pm »
Both this and my earlier comment - in your other thread - are things I brought up in EA 6.x days. At least one of them was around the time of the EA 7.0 beta, so might have been lost in the clutter.

Of course with the 7.5 beta due to begin shortly, I'd suggest anyone who finds this issues important should post bug reports or feature requests now. This might help raise the priority before the beta period obscures 'regular' bugs.

Just another 0.02 CAD from the Frozen North...
No, you can't have it!