well, it's really a tough question, it's like PHP promotes unstructured code
...
>From my point of view, it's the programmers choice.
you can put a data access layer in your code to enforce constraints on your
transactions, or if you insist, you can use the InnoDB engine, also MySQL 5
supports triggers, you can use them to apply your constraints, or you can
dumb MySQL and try to find another DBMS.
it depends on what are your needs, and what suits your project more. i don't
think a language or a DBMS would promote anything, they are just tools to
make your life easier.
also db design is not just about constraints, a more important part of it is
where everything goes, how my queries are going to be faster, and what DBMS
you should use.
well MySQL gives you a variety of options, one of them should be default,
and that one is myisam, but there is a list of options, depends on your
need.
On 1/30/07, Al-Faisal El-Dajani <[EMAIL PROTECTED]> wrote:
>
> Hello guys,
>
> I was just thinking, does the use of MySQL DB engine promote bad DB design
> decisions?
>
> I am a huge fan of enforcing constraints wherever possible, and one of the
> most important constraints in DB design is the foreign key constraint. Since
> the default transaction manager in MySQL is MyISAM -which doesn't enforce
> those constraints, does MySQL promote bad design and development habits?
>
> Just a thought...
> --
> Al-Faisal El-Dajani
> Phone: +962-7-77 799 781
> P.O Box: 140056
> 11814 Amman, Jordan
> >
>
--
Ala'a A. Ibrahim
http://alaa-ibrahim.com/guru
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Jordan PHP Users Group" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/JoPHP
http://Jolug.org/
-~----------~----~----~----~------~----~------~--~---
