• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Update method

 
Dalibor Kalna
Greenhorn
Posts: 8
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi all,

in my update method I'm concerned only about owner. That means I skip all fields in record beeing updated and I stop in front of owner field. Then I perform write. Is that right ? Could I ignore the other stuff completely ? This would be minimalistic but sufficient.

Thanks
Dalibor
 
Anton Golovin
Ranch Hand
Posts: 476
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Dalibor Kalna:
Hi all,

in my update method I'm concerned only about owner. That means I skip all fields in record beeing updated and I stop in front of owner field. Then I perform write. Is that right ? Could I ignore the other stuff completely ? This would be minimalistic but sufficient.

Thanks
Dalibor


It is up to you. If you ignore the other stuff, you would need to check it in your business logic by going lock-read-check-update-unlock.
 
mike acre
Ranch Hand
Posts: 197
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I think you maybe talking cross-purposes.
I understood the question to mean

"Can I ignore implementing update on all fields except customer"

If this is the question I would say this is a mistake.

I would implement the database tier completely for all methods and make them totally agnostic of the business logic. Your update should be able to update all fields and only care that the max field lengths are adhered to.

I don't really see that your suggested approach is defendable at all. Unless I misunderstand you.
 
I agree. Here's the link: http://aspose.com/file-tools
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic