e sort
> of an ID for each type.
> of course you'll end up with a table with many columns, and many of
> them will be null depending on which type an entry is.
> but with this approach, you can easily associate with an address table.
>
> Tony S. Wu
> [EMAIL PROTECTED]
>
&g
addresses of your
> people.
>
> If you keep your 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'
loyee, 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 Ya
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
{
VISI
