This project is read-only.

Request for online tool

May 18, 2013 at 3:49 AM
Edited May 18, 2013 at 3:50 AM
Love the Chrome based DB designer, it's exactly the sort of thing I've been looking for.

I'll second, though, the request for auto_increment support.

Also, it doesn't seem to handle primary keys that are composed of multiple fields properly. Each field gets a primary key line, rather than all of them being combined into a single primary key line.

Edit: and, saving diagrams to somewhere else would also be great. Integrating with Google Drive, or a file-based import/export.
May 19, 2013 at 1:48 PM
Edited May 19, 2013 at 1:52 PM
Small bug report: after manually editing the precision and scale of a DECIMAL field (in the table, not in the field edit breakout) and creating another table, the breaktout box stopped updating itself as I clicked in other fields. It still worked to edit the currently selected field, but wouldn't change to reflect the current values of that field.

Edit: started working again after I edited the name of a table.
May 19, 2013 at 2:25 PM
Thank you for your feedback and for reporting this bug! FYI, a rewrite is in the works that will address issues such as proper handling of multiple PK's, and I like your idea of interfacing with Google Drive. I'll look into it.
May 20, 2013 at 3:41 PM
Looking forward to the next version!

A file-based export/import would be very helpful. I'd like to use this in my database course in the fall. It's the easiest database design tool I've run across, just the thing for students who are learning database design and don't need all the bells and whistles of a more complex tool. For students to submit assignments, it'd be great if they could get their designs out to a file that I could then import.
May 31, 2013 at 9:04 PM
Another thing I just noticed is the lack of cardinality markers on the relationships. It hasn't bothered me for my personal projects, but I just realized that for students doing their first database design work, it'd be nice to have the one and many hash marks show automatically based on whether the relationship is between two primary keys or a primary key and non-primary key.