t meant to suggest JDBC is the best or only way to create a
database interface. It's just to illustrate that creating a class
Database and a category Reading, which don't naturally emerge from
breaking the problem down, could be a poor way to solve the problem.
-- GG
Subje
On 15 May 2009, at 2:57 PM, Тимофей Даньшин wrote:
Is it a good idea to split all those classes into categories for
writing, reading and testing? For example, Database (Writing),
Database(Reading), Database(Testing) and so on? Or is it a silly
thing to do for some reason?
That's something
Is it a good idea to split all those classes into categories for
writing, reading and testing? For example, Database (Writing),
Database(Reading), Database(Testing) and so on? Or is it a silly thing
to do for some reason?
Maybe ? What trade-offs have you considered ? On reason to use cat
Hello.
Suppose, I have an app that, for example, works with a database. It
can write to the db, it can select things. There is a class that works
with the database, a class that controls that class and a class that
interacts with the gui. And, of course, there is some testing code in
all
