Is this true ?

[Morten Gulbrandsen]

Hello programmers,

is this true ? Could someone please comment on this.
http://www.dbdebunk.com/page/page/611060.htm

I have modeled some Entity Relationship Databases
using only MySQL, which was difficult.

According to what I believe, only connecting a database and accessing
a database is possible with PHP, and in addition creating dynamic web
pages.
To keep track of the users. And some history.

If this is true, then it would be possible to implement any database,
relational or Entity Relationship. Without MySQL.

I simply can't believe missing SQL statements can be remedied with php.

For instance create trigger, how can this be coded in php?

CREATE TRIGGER
Creates a trigger, which is a special kind of stored procedure that executes
automatically when a user attempts the specified data-modification statement
on the specified table. Microsoft® SQL ServerT allows the creation of
multiple triggers for any given INSERT, UPDATE, or DELETE statement.

Syntax
CREATE TRIGGER trigger_name
ON { table | view }
[ WITH ENCRYPTION ]
{
{ { FOR | AFTER | INSTEAD OF } { [ INSERT ] [ , ] [ UPDATE ] [ , ] [
DELETE ] }
[ WITH APPEND ]
[ NOT FOR REPLICATION ]
AS
[ { IF UPDATE ( column )
[ { AND | OR } UPDATE ( column ) ]
[ ...n ]
| IF ( COLUMNS_UPDATED ( ) { bitwise_operator } updated_bitmask )
{ comparison_operator } column_bitmask [ ...n ]
} ]
sql_statement [ ...n ]
}
}

Yours Sincerely

Morten Gulbrandsen
http://www.dbdebunk.com/page/page/611060.htm

MySQL is not a toy database - it is far superior to many I
have used in my long career. The lack of constraints is not
a weakness. It is eminently possible to create reliable
applications without the need for database constraints - I
should know because I have designed and built many
applications that did not use database constraints (mainly
because they were not available). Developers only rely on
database constraints to circumvent their sloppy code.
Anything that can be done within the database can also be
done within application code. I have seen what happens when
poor programmers try to shift logic from their code into the
database - they get it wrong and then blame the database for
their incompetence. I am used to designing and building
applications without relying on database'features', so I
write my code accordingly. It also means that the logic is
maintained in one place and not it bits and pieces here and
there.

--Tony Marston, http//groups.google.com, comp.lang.php

11/07/03

[Tom Thackrey]

On 24-Dec-2003, "Morten Gulbrandsen" <Mo****************@rwth-aachen.de>
wrote:

is this true ? Could someone please comment on this.
http://www.dbdebunk.com/page/page/611060.htm

I have modeled some Entity Relationship Databases
using only MySQL, which was difficult.

According to what I believe, only connecting a database and accessing
a database is possible with PHP, and in addition creating dynamic web
pages.
To keep track of the users. And some history.

If this is true, then it would be possible to implement any database,
relational or Entity Relationship. Without MySQL.

I simply can't believe missing SQL statements can be remedied with php.

For instance create trigger, how can this be coded in php?

CREATE TRIGGER
Creates a trigger, which is a special kind of stored procedure that
executes
automatically when a user attempts the specified data-modification
statement
on the specified table. Microsoft® SQL ServerT allows the creation of
multiple triggers for any given INSERT, UPDATE, or DELETE statement.

Syntax
CREATE TRIGGER trigger_name
ON { table | view }
[ WITH ENCRYPTION ]
{
{ { FOR | AFTER | INSTEAD OF } { [ INSERT ] [ , ] [ UPDATE ] [ , ] [
DELETE ] }
[ WITH APPEND ]
[ NOT FOR REPLICATION ]
AS
[ { IF UPDATE ( column )
[ { AND | OR } UPDATE ( column ) ]
[ ...n ]
| IF ( COLUMNS_UPDATED ( ) { bitwise_operator } updated_bitmask )
{ comparison_operator } column_bitmask [ ...n ]
} ]
sql_statement [ ...n ]
}
}

Yours Sincerely

Morten Gulbrandsen
http://www.dbdebunk.com/page/page/611060.htm

MySQL is not a toy database - it is far superior to many I
have used in my long career. The lack of constraints is not
a weakness. It is eminently possible to create reliable
applications without the need for database constraints - I
should know because I have designed and built many
applications that did not use database constraints (mainly
because they were not available). Developers only rely on
database constraints to circumvent their sloppy code.
Anything that can be done within the database can also be
done within application code. I have seen what happens when
poor programmers try to shift logic from their code into the
database - they get it wrong and then blame the database for
their incompetence. I am used to designing and building
applications without relying on database'features', so I
write my code accordingly. It also means that the logic is
maintained in one place and not it bits and pieces here and
there.

--Tony Marston, http//groups.google.com, comp.lang.php

It seems to me that any non-trivial application should encapsulate their
database access in a class or function library so that any need for
triggers, views or complex data relationships can be coded and enforced
therein. Personally, I wrap the PHP database calls so that I can port
between databases and to provide a central point for tracing if I need to
for debugging or performance tuning. Then I encapsulate the application
access in a class, so that the database structure is independent of the
application.

--
Tom Thackrey
www.creative-light.com
tom (at) creative (dash) light (dot) com
do NOT send email to ja*********@willglen.net (it's reserved for spammers)