2011/05/06 10:00 +0200, Rocio Gomez Escribano
Tables "client" an "user" are quite similar, but they don't have any
intersection, I mean, if somebody is a client, he or she cant be a user. So,
I have his or her driving license and I need to know what kind of person is.
Two others
mailto:h...@tbbs.net]
> Enviado el: miércoles, 04 de mayo de 2011 22:43
> Para: Rocio Gomez Escribano
> CC: mysql@lists.mysql.com
> Asunto: Re: RV: independent tables
>
> >>>> 2011/05/04 16:57 +0200, Rocio Gomez Escribano >>>>
> I suppose my solution is an
On Fri, 2011-05-06 at 09:00 +0100, Rocio Gomez Escribano wrote:
> Tables "client" an "user" are quite similar, but they don't have any
> intersection, I mean, if somebody is a client, he or she cant be a user. So,
> I have his or her driving license and I need to know what kind of person is.
>
> I
mayo de 2011 22:43
Para: Rocio Gomez Escribano
CC: mysql@lists.mysql.com
Asunto: Re: RV: independent tables
>>>> 2011/05/04 16:57 +0200, Rocio Gomez Escribano >>>>
I suppose my solution is an Join, but they have no intersection
<<<<<<<<
Really?
Your
2011/05/04 16:57 +0200, Rocio Gomez Escribano
I suppose my solution is an Join, but they have no intersection
Really?
Your examples are very much like a simple join, a special case of
... client OUTER JOIN user ON clientCodeDrivingLicense = userCodeDrivingLicense
What is wrong
The databas estructure:
mysql> describe user;
++-+--+-+-+-
---+
| Field | Type| Null | Key | Default | Extra
|
++-+--+-+-+-
---+
| userID
