sbshah97 / e-manager Goto Github PK

The apparent file isn't running due to some error in the code. Kindly find the bug in the code

Changes were made to master while the patch branch was active.
Because of this merging the two branches is not possible.

• Create a Database structure where each users' spending is documented! Initially run all the code in a trial code folder which allows the C++ program to connect to the database!

• In the current code, all the data is being written to a file as a result of which it is highly unorganized!

• Change this to send the data to a file and use the same to increase security as to what a person can read and write in the database!

• Use C++ bindings for a MySQL Database and use MySQL Workbench for the same!

Ground rules:

1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Create a Hash function instead of the current if-else loop.

Ground rules:

1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Ground rules:

1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Allow the use of comments to explain the code properly

Add a Contributing Guideline to contribute to the repository!
This is a starter issue.

🆕🐥☝ First Timers Only

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝 Read more about First Timers Only

🎃💻👕 Hacktoberfest: Trick or Treat!

If you haven’t yet, sign up for Hacktoberfest to earn an exclusive T-Shirt. Plus I’m sure we can teach you a cool trick or two in the process

🤔 What you will need to know

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you trough the process

❓ The Motivation

Every repository on GitHub has an exclusive guideline as to how to contribute to the repository stored in the CONTRIBUTING.MD file. Make sure you read this up so that you can contribute here.

🎯 The Goal

Create a new file called CONTRIBUTING.md and update the links in the README.md file

📋 Step by Step

• 🙋 Claim this issue: Comment below
  Please 🙏 only claim if you want to start working on it within a day.
  Once claimed we add you as contributor to this repository.
• 👌 Accept our invitation to this repository. Once accepted, assign yourself to this repository.
  In a nutshell: be patient and actively kind
• 🔄 replace the up for grabs label with in progress.
• 📝 Edit and replace its content with the content of
• 💾 Commit your changes with the message
• 🔀 Start a Pull Request. Set the title to and set description to There are two ways how you can start a pull request:
  1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.
  2. You can edit files directly in your browser
• 🏁 Done 👍 Replace the in progress label with ready. Ask in comments for a review :)