Forum Replies Created

Viewing 15 posts - 31 through 45 (of 77 total)

  • RE: Time Bomb Design - A Longer Fuse

    David.Poole (6/10/2010)


    There seems to be an assumption that there is a single field acting as the PK. This isn't necessarily true.

    As to calling things ID because its easier for...

  • RE: Time Bomb Design - A Longer Fuse

    RichB (6/9/2010)


    Thomas-282729 (6/8/2010)


    Again, what you are suggesting is a poorly written query where the developer uses the wrong alias (A.Id instead of B.Id). How does that improve clarity in the...

  • RE: Time Bomb Design - A Longer Fuse

    Stefan Krzywicki (6/9/2010)


    Consider the difference between

    SELECT E.EmployeeID, E.LastName, E.FirstName, D.DepartmentID, D.Department,

    P.Project, P.ProjectID, PD.ProjectDetailID, PD.ProjectDetail PD.Comments

    FROM Employee E

    INNER JOIN Department D

    ON E.DepartmentID = D.DepartmentID

    INER JOIN ProjectInterim PRI

    ON PRI.EmployeeID = E.EmployeeID

    INNER JOIN...

  • RE: Time Bomb Design - A Longer Fuse

    To simply state "That is the problem of the developer" sets up an adversarial relationship.

    On the contrary, using "TableNameId" for the PK column is harder for the developer not easier...

  • RE: Time Bomb Design - A Longer Fuse

    While it may be "more logical", it isn't really within your power to ensure the developers code things your way. One of the main reasons for aliases is to keep...

  • RE: Time Bomb Design - A Longer Fuse

    I agree with most of the article except for this statement:

    "The instant you start writing queries that join tables together ID, name and description are taken outside of their context...

  • RE: Just For Fun: An Impossible Delete

    Aaron Cabrele (10/31/2009)


    It says no additional identity column so that doesn't outrule the hidden one that already exists... As for adding a guid it depends on how strictly you say...

  • RE: Just For Fun: An Impossible Delete

    The original article states that you cannot use an identity column but says nothing about adding columns in general. Doesn't the entire issue come down to uniquely identifying each row?...

  • RE: Effective Dating Series Part I - The Problem

    Jason Whitney (10/1/2009)


    I have run into this before, and the article gives the first half of the solution. The second part is what I can't figure out; how to avoid...

  • RE: Effective Dating Series Part I - The Problem

    Unfortunately, the article glossed over quite a bit. The Devil in these details is a much bigger beast. For example, including the effective dates as part of the primary key...

  • RE: Twenty tips to write a good stored procedure

    These are my 2 cents are the OA:

    RE Capitalizing keywords

    IMO, this is an outdated suggestion. Back in the day when people used monochrome editors, it made sense. It might even...

  • RE: 9 Things to Do When You Inherit a Database

    I must say that from a maintenance point of view, one of the hardest skills to teach developers is the skill of removing obsolete code. Many developers simply comment old...

  • RE: There Must Be 15 Ways To Lose Your Cursors… Part 2: Just Put It in a S

    If the idea of the article is present set-based solutions to common cursor implementations, I have one that I'd like to see. It is the simple list result. I want...

  • RE: There Must Be 15 Ways To Lose Your Cursors... part 1, Introduction

    Heh... that's a heck of a switch

    in gears from the "intuitive" stance

    you took just a couple of posts ago.

    Actually, it goes directly to my point. Unlike DBA purists,...

  • RE: There Must Be 15 Ways To Lose Your Cursors... part 1, Introduction

    It is clear that you gentlemen are missing the point. That developers should strive to refine their craft is obvious. No one disputes that. That set-based solutions are preferred in...

Viewing 15 posts - 31 through 45 (of 77 total)