, Customer or non-Customer etc)
fkey(the pkey of Employee, Customer or non-Customer etc)
I know this design looks awkward but it does have the advantage of having
less tables otherwise.
BUT somehow it doesn't feel right. Can someone points me its pros and cons.
thanks all.
Tony Yau
--
PHP
current schema, you will have as many rows for one person
as many addresses for that person you have, and you will be duplicating
many
fields. So you must split your tables, one for your people and another for
your people's addresses.
-Original Message-
From: tony yau [mailto:[EMAIL
hi all,
I'm trying to make my classes compat with php4 and php5 is there a way of
doing something like this:
if( version== 4)
define( VISIBILITY, );
else if (version==5)
define( VISIBILITY, protected );
class Flex
{
VISIBILITY function CompatFunc();
}
--
Tony Yau
--
PHP
