I answered with the best possible detail based on the provided information.
I've heard the same about Ruby, you can switch platforms if you want. But
taking technical advice personally won't help you there either.
Diego
On Tue, Sep 14, 2010 at 16:23, Corey Coogan <[email protected]> wrote:
> This is the 4th time I've tried to write this without coming off in a
> way that many others come off when answering questions for which they
> have no detail and only assumptions from which to pass judgment. It's
> pretty easy and cheap to do and may bring some people satisfaction in
> feeling that they are superior in every way. I think it's something
> that really pulls down our industry. I'm told it's not like this in
> the Ruby community but pretty rampant in .NET. I've not done much
> with Ruby, so I can't comment on that, but I agree with the .Net
> sentiment. Since I know the actual details beyond the made-up snippit
> I shared, I will bow out.
>
> Thanks for all the help!
>
> Corey
>
>
>
> On Sep 14, 2:13 pm, José F. Romaniello <[email protected]> wrote:
> > 2010/9/14 Corey Coogan <[email protected]>
> >
> > > For example, constraint violation,
> >
> > You never send something that may fail due a constraint violation. There
> are
> > corner cases but in most of the cases i do the validation logic in the
> > application, not in the database.
> >
> > > network hiccup,
> >
> > Ok this is an interesting case. In your first mail you said "if the
> update
> > to the table A fail, i want to save that value on the table B", if you
> have
> > a network hiccup you will not be able to save an update in the table B.
> > Better than that.. you want to make to separated call to update
> something,
> > when the unit of work pattern can make this two updates in one
> roundtrip....
> > So maybe you are causing the hiccups with so many calls.
> > You better start implementing loggin at a high level.
> >
> > table rename, etc.
> >
> >
> >
> > OHHHHHHH!!!! So you are running your application and somebody comes to
> the
> > database and execute a "table rename"... Instead of wiriting this
> exception
> > handling code, i will strongly recommend you to find this guy and cut off
> > his fingers.
> >
> > We are not saying that you don't have to handle the exceptions, you have
> to
> > do the logging stuff!
>
> --
> You received this message because you are subscribed to the Google Groups
> "nhusers" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected]<nhusers%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/nhusers?hl=en.
>
>
--
You received this message because you are subscribed to the Google Groups
"nhusers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/nhusers?hl=en.
