active data table for mysql sp..

[sathyashrayan]

Dear group,
A mysql wrapper class, which just uses the CRUD operations for large scale
php development.
Is the same advisable for the mysql stored procedure? Following is a link I
got from
search http://www.phpclasses.org/browse/package/1615.html. All it does is do
the ADD/EDIT/DELETE/View
in stored procedure file. Any more links possible?

Is it necessary to go for active data table for mysql stored procedure?
The sp not only
does normal CRUD but implements business logic too. Advice me, thanks

--
sathyashrayan AT GmAAil (DOT) com,
TN,chennai,India.

[Barry]

"sathyashrayan" <sa***********@ATGmaIl.comwrote in message
news:48***********************@news.sunsite.dk...

Dear group,
A mysql wrapper class, which just uses the CRUD operations for large scale
php development.
Is the same advisable for the mysql stored procedure? Following is a link
I got from
search http://www.phpclasses.org/browse/package/1615.html. All it does is
do the ADD/EDIT/DELETE/View
in stored procedure file. Any more links possible?

Is it necessary to go for active data table for mysql stored procedure?
The sp not only
does normal CRUD but implements business logic too. Advice me, thanks

stored procedures are NOT scalable with application development. NEVER
implement business logic IN A DATABASE! not only will you find yourself
unable to maintain your application because validation is all over the
place, but for the same reason, you will find it virtually impossible to
make head-way in fixing bugs or adding enhancements. further, you are
requiring your developers to know MySql language constructs beyond cursory,
they will have to likewise know PHP. while the latter is a given, you will
find it harder to employ those who know both equally well...and that will
cost you.

imo, that consideration trumps your question about implementing stored
procedures using crud...save the amusement i get from associating the one
(sp's) with the literal interpretion of my feeling on the same (i.e. sp's
are crud!). don't do it my brutha.

:)

[sathyashrayan]

"Barry" <no****@example.comwrote in message
news:Y8************@newsfe07.lga...

>
"sathyashrayan" <sa***********@ATGmaIl.comwrote in message
news:48***********************@news.sunsite.dk...

>Dear group,
A mysql wrapper class, which just uses the CRUD operations for large
scale php development.
Is the same advisable for the mysql stored procedure? Following is a link
I got from
search http://www.phpclasses.org/browse/package/1615.html. All it does is
do the ADD/EDIT/DELETE/View
in stored procedure file. Any more links possible?

Is it necessary to go for active data table for mysql stored procedure?
The sp not only
does normal CRUD but implements business logic too. Advice me, thanks

stored procedures are NOT scalable with application development. NEVER
implement business logic IN A DATABASE! not only will you find yourself
unable to maintain your application because validation is all over the
place, but for the same reason, you will find it virtually impossible to
make head-way in fixing bugs or adding enhancements. further, you are
requiring your developers to know MySql language constructs beyond
cursory, they will have to likewise know PHP. while the latter is a given,
you will find it harder to employ those who know both equally well...and
that will cost you.

imo, that consideration trumps your question about implementing stored
procedures using crud...save the amusement i get from associating the one
(sp's) with the literal interpretion of my feeling on the same (i.e. sp's
are crud!). don't do it my brutha.

:)

Thanks for the reply. But any information for Sp just talks about the
besiness logic in the back end along with other things. For Example have the
wiki http://en.wikipedia.org/wiki/Stored_procedure in the para
"Simplification of data management"... But wiki is not the final though..Am
I missing something basic?

[Barry]

"sathyashrayan" <sa***********@ATGmaIl.comwrote in message
news:48***********************@news.sunsite.dk...

>
"Barry" <no****@example.comwrote in message
news:Y8************@newsfe07.lga...

>>
"sathyashrayan" <sa***********@ATGmaIl.comwrote in message
news:48***********************@news.sunsite.dk. ..

>>Dear group,
A mysql wrapper class, which just uses the CRUD operations for large
scale php development.
Is the same advisable for the mysql stored procedure? Following is a
link I got from
search http://www.phpclasses.org/browse/package/1615.html. All it does
is do the ADD/EDIT/DELETE/View
in stored procedure file. Any more links possible?

Is it necessary to go for active data table for mysql stored procedure?
The sp not only
does normal CRUD but implements business logic too. Advice me, thanks

stored procedures are NOT scalable with application development. NEVER
implement business logic IN A DATABASE! not only will you find yourself
unable to maintain your application because validation is all over the
place, but for the same reason, you will find it virtually impossible to
make head-way in fixing bugs or adding enhancements. further, you are
requiring your developers to know MySql language constructs beyond
cursory, they will have to likewise know PHP. while the latter is a
given, you will find it harder to employ those who know both equally
well...and that will cost you.

imo, that consideration trumps your question about implementing stored
procedures using crud...save the amusement i get from associating the one
(sp's) with the literal interpretion of my feeling on the same (i.e. sp's
are crud!). don't do it my brutha.

:)

Thanks for the reply. But any information for Sp just talks about the
besiness logic in the back end along with other things. For Example have
the wiki http://en.wikipedia.org/wiki/Stored_procedure in the para
"Simplification of data management"... But wiki is not the final
though..Am I missing something basic?

yes...everything i just said. and, wiki is NOT a good reference on
application architecture.

[Jerry Stuckle]

sathyashrayan wrote:

"Barry" <no****@example.comwrote in message
news:Y8************@newsfe07.lga...

>"sathyashrayan" <sa***********@ATGmaIl.comwrote in message
news:48***********************@news.sunsite.dk. ..

>>Dear group,
A mysql wrapper class, which just uses the CRUD operations for large
scale php development.
Is the same advisable for the mysql stored procedure? Following is a link
I got from
search http://www.phpclasses.org/browse/package/1615.html. All it does is
do the ADD/EDIT/DELETE/View
in stored procedure file. Any more links possible?

Is it necessary to go for active data table for mysql stored procedure?
The sp not only
does normal CRUD but implements business logic too. Advice me, thanks

stored procedures are NOT scalable with application development. NEVER
implement business logic IN A DATABASE! not only will you find yourself
unable to maintain your application because validation is all over the
place, but for the same reason, you will find it virtually impossible to
make head-way in fixing bugs or adding enhancements. further, you are
requiring your developers to know MySql language constructs beyond
cursory, they will have to likewise know PHP. while the latter is a given,
you will find it harder to employ those who know both equally well...and
that will cost you.

imo, that consideration trumps your question about implementing stored
procedures using crud...save the amusement i get from associating the one
(sp's) with the literal interpretion of my feeling on the same (i.e. sp's
are crud!). don't do it my brutha.

:)

Thanks for the reply. But any information for Sp just talks about the
besiness logic in the back end along with other things. For Example have the
wiki http://en.wikipedia.org/wiki/Stored_procedure in the para
"Simplification of data management"... But wiki is not the final though..Am
I missing something basic?

Forget what Barry said. He's still in the 1980's, with no idea what
he's talking about. SP's were designed to implement business logic -
and are excellent for this purpose.

I've been using SP's for well over 20 years now (starting with DB2 on
mainframes), and they work great. But sometime I do find them to be
overused. You shouldn't, for instance, use them for something which can
be done in a simple SQL statement. They can, however, be used for more
complex data validation than could be done with other methods such as
foreign keys. In MySQL, they could also be used to emulate recursive
SQL (which I hope MySQL will get some day - talk about powerful!).

But there's no need to emulate SP's in PHP. MySQL supports them now.

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
js*******@attglobal.net
==================

[Jerry Stuckle]

sathyashrayan wrote:

"Barry" <no****@example.comwrote in message
news:Y8************@newsfe07.lga...

>"sathyashrayan" <sa***********@ATGmaIl.comwrote in message
news:48***********************@news.sunsite.dk. ..

>>Dear group,
A mysql wrapper class, which just uses the CRUD operations for large
scale php development.
Is the same advisable for the mysql stored procedure? Following is a link
I got from
search http://www.phpclasses.org/browse/package/1615.html. All it does is
do the ADD/EDIT/DELETE/View
in stored procedure file. Any more links possible?

Is it necessary to go for active data table for mysql stored procedure?
The sp not only
does normal CRUD but implements business logic too. Advice me, thanks

stored procedures are NOT scalable with application development. NEVER
implement business logic IN A DATABASE! not only will you find yourself
unable to maintain your application because validation is all over the
place, but for the same reason, you will find it virtually impossible to
make head-way in fixing bugs or adding enhancements. further, you are
requiring your developers to know MySql language constructs beyond
cursory, they will have to likewise know PHP. while the latter is a given,
you will find it harder to employ those who know both equally well...and
that will cost you.

imo, that consideration trumps your question about implementing stored
procedures using crud...save the amusement i get from associating the one
(sp's) with the literal interpretion of my feeling on the same (i.e. sp's
are crud!). don't do it my brutha.

:)

Thanks for the reply. But any information for Sp just talks about the
besiness logic in the back end along with other things. For Example have the
wiki http://en.wikipedia.org/wiki/Stored_procedure in the para
"Simplification of data management"... But wiki is not the final though..Am
I missing something basic?

I should also add, if you want more info on SP's in MySQL, I suggest you
check out comp.databases.mysql. Instead of those who only think they
are experts but don't really know much, you'll find real database
experts there.

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
js*******@attglobal.net
==================

[Barry]

"Jerry Stuckle" <js*******@attglobal.netwrote in message
news:g5**********@registered.motzarella.org...

sathyashrayan wrote:

>"Barry" <no****@example.comwrote in message
news:Y8************@newsfe07.lga...

>>"sathyashrayan" <sa***********@ATGmaIl.comwrote in message
news:48***********************@news.sunsite.dk.. .
Dear group,
A mysql wrapper class, which just uses the CRUD operations for large
scale php development.
Is the same advisable for the mysql stored procedure? Following is a
link I got from
search http://www.phpclasses.org/browse/package/1615.html. All it does
is do the ADD/EDIT/DELETE/View
in stored procedure file. Any more links possible?

Is it necessary to go for active data table for mysql stored
procedure? The sp not only
does normal CRUD but implements business logic too. Advice me, thanks
stored procedures are NOT scalable with application development. NEVER
implement business logic IN A DATABASE! not only will you find yourself
unable to maintain your application because validation is all over the
place, but for the same reason, you will find it virtually impossible to
make head-way in fixing bugs or adding enhancements. further, you are
requiring your developers to know MySql language constructs beyond
cursory, they will have to likewise know PHP. while the latter is a
given, you will find it harder to employ those who know both equally
well...and that will cost you.

imo, that consideration trumps your question about implementing stored
procedures using crud...save the amusement i get from associating the
one (sp's) with the literal interpretion of my feeling on the same (i.e.
sp's are crud!). don't do it my brutha.

:)

Thanks for the reply. But any information for Sp just talks about the
besiness logic in the back end along with other things. For Example have
the wiki http://en.wikipedia.org/wiki/Stored_procedure in the para
"Simplification of data management"... But wiki is not the final
though..Am I missing something basic?

Forget what Barry said. He's still in the 1980's, with no idea what he's
talking about. SP's were designed to implement business logic - and are
excellent for this purpose.

uhm, no, i don't think so. now...here's where providing a cite would do you
well, jerry. simply declaring what you will, no matter how narcasistic you
are, doesn't make it so.

I've been using SP's for well over 20 years now (starting with DB2 on
mainframes), and they work great.

said the man with no clients.

[Barry]

"sathyashrayan" <sa***********@ATGmaIl.comwrote in message
news:48***********************@news.sunsite.dk...

>
"Barry" <no****@example.comwrote in message
news:Y8************@newsfe07.lga...

>>
"sathyashrayan" <sa***********@ATGmaIl.comwrote in message
news:48***********************@news.sunsite.dk. ..

>>Dear group,
A mysql wrapper class, which just uses the CRUD operations for large
scale php development.
Is the same advisable for the mysql stored procedure? Following is a
link I got from
search http://www.phpclasses.org/browse/package/1615.html. All it does
is do the ADD/EDIT/DELETE/View
in stored procedure file. Any more links possible?

Is it necessary to go for active data table for mysql stored procedure?
The sp not only
does normal CRUD but implements business logic too. Advice me, thanks

stored procedures are NOT scalable with application development. NEVER
implement business logic IN A DATABASE! not only will you find yourself
unable to maintain your application because validation is all over the
place, but for the same reason, you will find it virtually impossible to
make head-way in fixing bugs or adding enhancements. further, you are
requiring your developers to know MySql language constructs beyond
cursory, they will have to likewise know PHP. while the latter is a
given, you will find it harder to employ those who know both equally
well...and that will cost you.

imo, that consideration trumps your question about implementing stored
procedures using crud...save the amusement i get from associating the one
(sp's) with the literal interpretion of my feeling on the same (i.e. sp's
are crud!). don't do it my brutha.

:)

Thanks for the reply. But any information for Sp just talks about the
besiness logic in the back end along with other things. For Example have
the wiki http://en.wikipedia.org/wiki/Stored_procedure in the para
"Simplification of data management"... But wiki is not the final
though..Am I missing something basic?

i was perusing this topic this morning and thought you'd like to read some
thoughts that are counter to stored procedure use defined on wiki...whos
author, i believe, has very little experience in system architecture - at
least at the data layer. anyway, forget the guy in the link refers to .net
and asp. the issues discussed are language independent. also, notice how he
echos two of the points i made in my original response to you.

http://www.ytechie.com/2008/05/store...alability.html

despite what jerry's isolated view is - he himself has no public web site -
they are those with actual experience working with volumes of traffic and
data who would know best. if you google 'do "stored procedures" scale', you
will find one u.s. ton of those taking issue with jerry's advice. jerry
simply likes to chime in and bash as many others as possible along the way.
as you can tell by his thousands of posts per day, jerry has no job nor life
outside of usenet. he looks to be 65 based on his picture from the net. i
doubt he's employed. he probably picks up a programming bone thrown his way
every once in a while. again, though, given his 'presence' here the last
bone was some time ago.

cheers.