Forum Replies Created

Viewing 15 posts - 346 through 360 (of 432 total)

  • RE: SQL future

    GSquared (11/18/2009)


    SQL will, I'm sure, go the route of the buggy whip one day. But the replacement technology hasn't, to my knowledge, been invented yet. I expect that...

  • RE: SQL future

    Your SQL solution does not solve the problem because it is still possible to create an order in the Orders table without any corresponding Order_Item.

    You suggested using a trigger but...

  • RE: SQL future

    Lynn Pettis (11/18/2009)


    David Portas (11/18/2009)


    ... They include Dataphor, Muldis and various other open source efforts.

    Interesting that you mention Dataphor. There have been others that have been religous zealots...

  • RE: SQL future

    All my replies were intended in a positive and constructive spirit of contribution. I hope we can keep it that way. But as I said, I really didn't want to...

  • RE: SQL future

    GSquared (11/18/2009)


    Interesting problem, but easily solved by adding a foreign key constraint to the Orders table, referencing the OrdersItems table (a join table between Orders and Items).

    Then how would you...

  • RE: SQL future

    I didn't want this to become a discussion about nulls because if you fix the other issues (such as providing decent type support and a truly relational language) then the...

  • RE: SQL future

    Elliott W (11/17/2009)



    So in my view the three things you mention are already handled, could they be better, sure, but that doesn't support your position..

    Oh dear! I wasn't very clear...

  • RE: SQL future

    Elliott W (11/17/2009)


    SQL isn't broken, but that isn't to say that it solves EVERY need. What I see most is tweaks to existing features.

    I don't think tweaking or enhancing...

  • RE: SQL future

    GSquared (11/17/2009)


    The problem I've seen is that every non-relational data engine I've tested has had worse problems than SQL RDBMSs do. Sure, some of them solve some of the...

  • RE: SQL future

    I agree with the comments so far. However, I do wonder if we database professionals working with SQL are collectively partly to blame for the lack of momentum and new...

  • RE: null values

    Jeff Moden (11/7/2009)


    David Portas (11/7/2009)


    In either SQL or Oracle you can use COALESCE, which is the Standard SQL function instead of ISNULL and NVL which are non-standard.

    Why do you think...

  • RE: null values

    In either SQL or Oracle you can use COALESCE, which is the Standard SQL function instead of ISNULL and NVL which are non-standard.

  • RE: Datawarehouse Schema: column suffix Key or ID?

    Whatever you choose for a naming convention the most important thing is to be consistent about using it. Perhaps the intention in your case was to distinguish the name of...

  • RE: Set Based Solution

    Do you have to insert duplicates though - even though you can't declare a key?

    Basically the design is unusable - you can insert rows to it but you can never...

  • RE: Set Based Solution

    cy-513176 (10/9/2009)


    the codes will not be unique...bummer.

    Why not? What's the point of filling up a table with duplicate codes with different IDENTITY values? That goes against the very point of...

Viewing 15 posts - 346 through 360 (of 432 total)