UML is (necessarily) incomplete. But I think you can handle the data
already:
In type field, use the SQL type (or something which you can translate
to that)
In the value field, give the default value, plus indication of
NULL/NOT NULL and additional data as the "property string": From UML
User Guide, pg 128:
origin:Point=(0,0) {not null, frozen}
Becomes:
name: origin
type: Point
value: (0,0) {not null, frozen}
KEY is non-OO and thus non-UML, but could be done as a private
pseudomethod, "KEY", whose arguments are the list of attributes
needed to form the key.
On Thu, 8 Feb 2001, Andreas Prlic wrote:
> Date: Thu, 8 Feb 2001 08:56:10 +0100
> To: [EMAIL PROTECTED]
> From: Andreas Prlic <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> Subject: dia & MYSQL suggestion
>
> Hi!
>
> I am using dia to draw physical entity relationship models of my
> MYSQL
> database. So I use the "UML class" object to create Tables and I
> add
> attributes to generate the columns of the Table.
>
> At the moment the "attribute data" allows to specify attribute
> name,
> type and value. To properly describe the MYSQL database tables I
> would need five "attribute data" fields, since in MYSQL every field
> is
> described by field name, type (int, char,etc) , NULL (if it can be
> empty), Key , Default value and Extra info. Would it be possible to
> create this kind of object?
>
> Generalizing this one could imagine a table object, which the user
> could define to be of N x M size, where M is the number of
> attribute
> data fields. And every data field could be named separately
>
> greetings,
> andreas
>
>
>
> --
>
>
> Andreas Prlic Center of Applied Molecular Engineering
>University of Salzburg, Jakob-Haringerstr. 3
>A - 5020 Salzburg, Austria
>Tel: +43 - 662 - 8044 5798
>http://www.came.sbg.ac.at/People/ap/home.html
>
>
>
>
--
Harry George
[EMAIL PROTECTED]
