Announcement

Collapse
No announcement yet.

1,000,000, posts

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Shining Arcanine
    replied
    Originally posted by filburt1
    If you drop and reapply auto_increment, it could start to fill in blank IDs. If you delete post ID 2, then reapply auto_increment, suddenly it could be filled with a new post.

    If the dateline had millisecond precision, it could be used as the primary key instead (provided no two posts share the same post time to the millisecond). The point of an ID is to uniquely identify data, not to necessarily describe it.

    (I'm taking a database design class, but I knew this going into it anyway)
    There would still be the possibility of collisions even with millisecond precision.

    I did not know that reseting auto_increment would fill in unused IDs. Thanks for the information.

    Leave a comment:


  • Joe Gronlund
    replied
    Congrats on the 1,000,000, posts

    Leave a comment:


  • filburt1
    replied
    If you drop and reapply auto_increment, it could start to fill in blank IDs. If you delete post ID 2, then reapply auto_increment, suddenly it could be filled with a new post.

    If the dateline had millisecond precision, it could be used as the primary key instead (provided no two posts share the same post time to the millisecond). The point of an ID is to uniquely identify data, not to necessarily describe it.

    (I'm taking a database design class, but I knew this going into it anyway)

    Leave a comment:


  • Shining Arcanine
    replied
    To my knowledge never in the history of forum software has a post ever been made after a post with a higher ID number than it.

    Leave a comment:


  • filburt1
    replied
    Originally posted by Arsenik
    You probably deleted some post there and there... so using the postid as a reference wouldnt work. You would need to run a query to find out exactly.

    This for example (where vb3_post is your post table...):

    Code:
    SELECT * 
    FROM vb3_post 
    WHERE visible = 1
    ORDER BY postid
    LIMIT 999999, 1
    It will return the 1 000 000th post...
    Order it by dateline, not post ID. All an ID is, at least in vBulletin's database, is a unique identifier for a row. It has no other special meaning. They simply ascend because that's what auto_increment does by default.

    Leave a comment:


  • zombie_UC
    replied
    hola

    Leave a comment:


  • alexanderpas
    replied
    Originally posted by TripleT
    finally reached the magic number
    You might want to check this thread too... http://www.vbulletin.com/forum/showthread.php?t=47430

    Leave a comment:


  • LeeD
    replied
    Congrats - very nice!

    Leave a comment:


  • TalkMilitary
    replied
    Congrats! Nice milestone to hit.

    Leave a comment:


  • Arkham
    replied
    Congratulations!!!

    Leave a comment:


  • Thunderfall
    replied
    Welcome to the million posts club!

    Leave a comment:


  • bullfrog45
    replied
    IT's a dream to me

    Leave a comment:


  • dutchbb
    replied
    Great, thanks

    Leave a comment:


  • Arsenik
    replied
    You probably deleted some post there and there... so using the postid as a reference wouldnt work. You would need to run a query to find out exactly.

    This for example (where vb3_post is your post table...):

    Code:
    SELECT * 
    FROM vb3_post 
    WHERE visible = 1
    ORDER BY postid
    LIMIT 999999, 1
    It will return the 1 000 000th post...
    Last edited by Arsenik; Tue 28 Feb '06, 7:30am.

    Leave a comment:


  • dutchbb
    replied
    Originally posted by Andrew111888
    Code:
    http://www.site.com/forum/showpost.php?p=1000000&postcount=1
    thanks

    however the database show more posts and the statistics on forumhome less? How is this possible?

    Leave a comment:

Related Topics

Collapse

Working...
X