On 3/19/07, Dave Crozier [EMAIL PROTECTED] wrote:
Now, my question. Using standard UML how do you represent this relationship?
Well, I don't think that you can, or should.
The relationship is between the PK and the FK, two identical fields.
If you're not joining the tables this way, you're not
Of Ted Roche
Sent: 19 March 2007 12:33
To: profox@leafe.com
Subject: Re: Playing with UML
On 3/19/07, Dave Crozier [EMAIL PROTECTED] wrote:
Now, my question. Using standard UML how do you represent this
relationship?
Well, I don't think that you can, or should.
The relationship is between
On 3/19/07, Dave Crozier [EMAIL PROTECTED] wrote:
As I'm converting (slowly) the existing native VFP table onto MySQL this
requirement to model the extended FK will eventually become redundant and
as you say I'll order the cursors using the additional order by in the SQL
statement. It's just
I've been using Visio and the SQL Server Express Management Studio to make
pictures for my current client: being able to make her own sub-diagrams has
helped her see the relationships better, instead of having extra lines all
over the screen. I think I'll need to look at investing in xCase,
Ted,
I just used those field names for simplicity. I know I've been bitten on
that - especially using Desc as an abbreviation for Description for a field
name in MySQL!
With regards to mixing RDBMS features in UML it is really surprising how
much you take VFP features for granted which speaks
On 3/19/07, Dave Crozier [EMAIL PROTECTED] wrote:
I just used those field names for simplicity. I know I've been bitten on
that - especially using Desc as an abbreviation for Description for a field
name in MySQL!
'ats what I thought.
The problem I have is managing and phasing the migration
6 matches
Mail list logo