OO DB question

I had a OO model worked out which involved forms populating new instances of
a class and being stored in an ArrayList. I'm now moving this over to a DB
backend rather than a file - I've been wondering if I even need to create
objects now? Could I just work directly with the DB e.g. form data will pass
directly to db handled in click events, the listview of objects can be read
straight from db (no need to instantiate classes).
I guess I'm after opinions on what others would do in these circumstances.
Would it be ok to interact directly with the DB, or should I use the class
instances as interfaces to the DB through their properties? Would this mean
I'd just instantiate a class to pass data to and from DB and then dispose of
it? Or keep one instance of each class to act as an interface?

Any opinions would be appreciated,

Chris

Ps Merry Christmas


.

Relevant Pages

  • Re: OO DB question
    ... Could I just work directly with the DB e.g. form data ... > I guess I'm after opinions on what others would do in these circumstances. ... > instances as interfaces to the DB through their properties? ... Chris ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Weird network issue
    ... or two interfaces on the same net. ... >address listed is the V120's own Mac address?!?! ... Expressed in this posting are my opinions. ... to opinions held by my employer, Sun Microsystems. ...
    (comp.unix.solaris)
  • Re: realpath
    ... There are a number of interfaces where I haven't been sure and ... have sometimes resorted to allocating PATH_MAX+1 bytes throughout a ... Expressed in this posting are my opinions. ... to opinions held by my employer, Sun Microsystems. ...
    (comp.unix.programmer)
  • Re: Port scans. What are these?
    ... RIPE ... There are more than two rings in the Olympic symbol ... /software/ interfaces, that is. ... the opinions expressed in this opinion do not necessarily ...
    (alt.computer.security)
Loading