Re: OO DB question
- From: "Chris" <misterjingo@xxxxxxxxx>
- Date: Sun, 25 Dec 2005 09:21:51 GMT
"Chris" <misterjingo@xxxxxxxxxxxxxxx> wrote in message
news:Intrf.32011$vl2.11600@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
>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
>
Just to clarify, when I say create objects, I originally had objects for
each form (a diary page) which stored all the text and options. This was
placed in an ArrayList and output to a file on saving.
Chris
.
- Follow-Ups:
- Re: OO DB question
- From: Joanna Carter [TeamB]
- Re: OO DB question
- References:
- OO DB question
- From: Chris
- OO DB question
- Prev by Date: OO DB question
- Next by Date: Microsoft Development Environment The operation could not be completed - error
- Previous by thread: OO DB question
- Next by thread: Re: OO DB question
- Index(es):
Relevant Pages
|
Loading