Thanks a lot Tony. Unfortunately for me, I'm seeing myself in no conditions
for properly learning a framework. I want to learn PHP and a framework bring
so many concepts at once, that I found extremely complex and time consuming
do dig in, at once, right now. Since I have no more than a few months
""MEM"" wrote in message
news:000201ca0a9f$ca3fb110$5ebf13...@com...
> > > As for (1) even in my pre-OO days I was used to using a single
> > > generic DAO for all database access. The only time that more
> > > than one DAO existed was for a different DBMS engine. This
> > > is why I have one DA
> > > As for (1) even in my pre-OO days I was used to using a single
> > > generic DAO for all database access. The only time that more
> > > than one DAO existed was for a different DBMS engine. This
> > > is why I have one DAO class for MySQL, one for PostgreSQL
> > > and another for Oracle. If y
On Sun, Jul 19, 2009 at 03:56:43PM +0100, Tony Marston wrote:
> Two things strike me as wrong with your thinking:
>
> (1) The idea that you have a separate DAO for each entity instead of a
> single generic DAO which can act for any entity in the system.
> (2) The idea that pagination requires its
> Why not? Why can't you replace a call to a mysqli function with a call
> to a
> PDO function?
It's not just a simple replacement - I need to add bindparam, prepare,
execute, placeholders and fetchObject. But I will give it a try...
> > Also, I also intend to use fetchObject method instead of f
""MEM"" wrote in message
news:002001ca0898$5d183840$1748a8...@com...
> > As for (1) even in my pre-OO days I was used to using a single
> > generic DAO for all database access. The only time that more
> > than one DAO existed was for a different DBMS engine. This
> > is why I have one DAO class
> > As for (1) even in my pre-OO days I was used to using a single
> generic
> > DAO
> > for all database access. The only time that more than one DAO existed
> > was
> > for a different DBMS engine. This is why I have one DAO class for
> MySQL,
> > one
> > for PostgreSQL and another for Oracle. If
> As for (1) even in my pre-OO days I was used to using a single generic
> DAO
> for all database access. The only time that more than one DAO existed
> was
> for a different DBMS engine. This is why I have one DAO class for MySQL,
> one
> for PostgreSQL and another for Oracle. If you are incapable
Two things strike me as wrong with your thinking:
(1) The idea that you have a separate DAO for each entity instead of a
single generic DAO which can act for any entity in the system.
(2) The idea that pagination requires its own class, and therefore needs
this "is-a" and "has-a" nonsense.
As f
9 matches
Mail list logo
