You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Contributors.md
+11-9Lines changed: 11 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,22 +2,24 @@
2
2
3
3
Below is a list of features and improvements to which you can contribute. If you have any additional ideas, please raise an issue or implement them as well!
4
4
5
+
- When a user clicks "Show Data" in build database after creating a table, it will immediately crash the display page if the table does not have a primary and foreign key connected to another table. This is due to it not have its "nodes and edges" not being rendered in the "Flow.tsx" file. A future iteration team should consider making a conditional statement that will alert the user that they currently have no Entity Relationship establish within their schema. (see first bug in known bugs/issue)
5
6
- Logging needs a default settings list and direct reimport into live database.
6
-
- The SQL code to import has been placed into the DB_Schemas folder along with SQL Schema dumps. Also, log setting functionality is currently limited to Postgres databases and the code needs to be expanded to query and display log setting info from MySQL databases.
7
-
-Db-schemas
8
-
- The schemas are saved under db_schemas and is saved in the server. Have a way to delete the schemas on the server from the front end. It would also be convenient to add these schemas to a list of existing schemas and be able to pull these schemas to display for the user to avoid having to make a new connection to the same database multiple times.
9
-
-Complete the integration of SQLite as an optional database and expand compatibility with other SQL database such as IBM Db2, etc.
7
+
- The SQL code to import has been placed into the DB_Schemas folder along with SQL Schema dumps. Also, log setting functionality is currently limited to Postgres databases and the code needs to be expanded to query and display log setting info from MySQL databases.
8
+
-Increasing compatibility with other SQL-based databases: Although PostgreSQL and MySQL databases are perfectly compatible, dbSpy is currently not optimized to work with other SQL databases like Oracle SQL and Microsoft SQL.
9
+
- Saving multiple databases per user: dbSpy allows users to save and load one database per account, but allowing users to store multiple databases would make the application more functional.
10
+
-Allow users to delete one or more of their saved databases
10
11
- Add additional themes and graphical options to canvas and tables
11
12
- Live query feedback so users can see what their changes to the canvas look like as queries.
12
13
- As the ability to manipulate data has been recently added, there are not as many safe guards to prevent users from performing actions that are not allowed for some databases.
13
-
- Limiting the data types to only those possible for the the database the user is currently working on.
14
-
- Adding Account specific functionality and the ability to save data to your account.
14
+
- Limiting the data types to only those possible for the database the user is currently working on.
15
15
- TypeORM has been implemented to connect to multiple databases but can be modified to further universal database functions
16
-
- Create login feature to save multiple databases to user account and be able to load multiple past databases.
17
16
18
17
Known bugs/issues
19
18
19
+
- Clicking show data after building a database by adding tables causes the app to crash. *-Urgent Fix Needed*
20
+
- Clearing canvas after connecting a database and attempting to create a new table without refreshing causes the website to crash (blank screen).
20
21
- Undo function will not revert the state of the canvas to the point where it is empty.
21
-
- Attempting to change the name of a column while adding a foreign key will result in the page crashing and going all white. Changing the column name is currently disabled.
22
22
- When creating a new foreign key on a column, if you click submit while there is no table selected, the display area will shrink to a very small square in the top left corner of the page.
23
-
- Exporting your query has been affected in the course of adding additional databases and needs to be reorganized
23
+
- Exporting your query has been affected in the course of adding additional databases and needs to be reorganized
24
+
- The webpage reverts back to dark mode when it is refreshed even when if it is already in light mode
0 commit comments