Merge pull request #374 from kalebmmm/patch-1

IPv6 compatible schema (#355)

CODE_OF_CONDUCT.md

@@ -0,0 +1,46 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at therslgames@gmail.com. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

CONTRIBUTING.md

@@ -0,0 +1,33 @@
+# Writing a good issue report
+In order to be useful for the maintainers issues should include as much information as possible about the issue.  
+The information is crucial for reproducing the issue.
+
+- Tickets about Exceptions should include a full stack trace if at all possible. (Usually found in the Errors.txt file or console logs)
+- Tickets about Visual issue such as wrong characters or typos should include a screenshot of the affected window as well as what should be displayed instead.
+- Tickets about odd behaviour should include a detailed turn of events how this issue occurred, if at all possible.
+
+Additional information that might be useful:
+
+- Possible logs, debug logs, error logs
+- Plan and Server version & type
+- Database in use (SQLite / MySQL)
+- Possible config settings related to the issue
+- Information related to the issue in the database
+- Table structure in the database if related to the issue
+
+# Writing a good Pull Request
+Good pull requests make the work of maintainers easier, which will make the approval of the pull requests quicker.
+
+New code should be created in a new feature / bugfix / improvement branch.
+After done with the feature (Or prior) a PR can be opened.
+
+Good practices that make PR easier to approve:
+
+- Commit often with detailed commit messages: Commits are cheap and can be easily reversed if neccessary.
+- Before marking an issue solved in a commit message ("Fixed #issueN.o.") it should be ensured that the issue is fixed. (By manual testing or with Unit Tests.)
+- Name PR related to what it is attempting to accomplish. "Implemented improved graph creation", "Bugfix PR for Version 4.0.2"
+- In case the feature in PR is not self explanatory an attempt to explain the feature should be made in the message / comments of the PR.
+- Code follows similar style as rest of the code and is easy to read. (Brackets used always, Classes with BigFirstLetter, variablesCamelCase)
+
+PRs are never merged directly to the `master`-branch, and are instead merged into next version specific branch.  
+IF no version specific branch is available when making a PR, select master and notify in the comments about the fact - Maintainers will create a new version specific branch and change the branch of the PR.

Plan/src/main/java/com/djrapitops/plan/database/tables/IPsTable.java

@@ -43,7 +43,7 @@ public class IPsTable extends UserIDTable {
     public void createTable() throws DBCreateTableException {
         createTable(TableSqlParser.createTable(tableName)
                 .column(columnUserID, Sql.INT).notNull()
-                .column(columnIP, Sql.varchar(20)).notNull()
+                .column(columnIP, Sql.varchar(39)).notNull()
                 .column(columnGeolocation, Sql.varchar(50)).notNull()
                 .foreignKey(columnUserID, usersTable.getTableName(), usersTable.getColumnID())
                 .toString()