Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 1105833
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 17, 20262026-05-17T01:41:49+00:00 2026-05-17T01:41:49+00:00

I’m creating similar thing to twitter retweet function! This is my database table for

  • 0

I’m creating similar thing to twitter retweet function!

This is my database table for tweets (status messages):

ID || USER_ID || TWEET || RETWEET_ID || RETWEET_NAME || DATE

What I’m trying to find out is, if the logged in user retweets something, when they refresh the page I don’t want them to see the retweet button (because obviously they have retweeted it). I’m more concerned with the app logic; it’s driving me crazy.

p.s. a user’s timeline is queried using a while loop array, so it has to distinguish between a normal tweet, and retweeted tweet, if you get my drift!! :))

EDIT: another thing is if it’s a normal tweet, both values RETWEET_ID and RETWEET_NAME are NULL, so that’s how I can differentiate between the two!!

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-17T01:41:50+00:00Added an answer on May 17, 2026 at 1:41 am

    I see two options

    1) You use similar to what you have now

    ID || USER_ID || TWEET_TEXT || RETWEET_ID || DATE
    

    But drop the retweet name. If each tweet id is unique, then your tweet would contain either a tweet_text or a retweet_id.

    2) The second option, and better solution would be to have two tables, tweets and retweets.

    TWEETS { ID || USER_ID || TWEET_TEXT || DATE }
    RETWEETS {ID || USER_ID || RETWEET_ID || DATE }
    

    The second option is cleaner, and will mean you will not have empty columns in your database, but the first option will make your querying easier, as you do not have to join the two tables, or create a view over the table etc.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.