Import database schema.

Ken Lyle shared this idea 6 years ago
Completed

It's certainly state of the art for code generators to generate working database applications from a schema. It would be great for JIM to either import schemas directly, or to leverage an XML intermediary file, like the project files from PHPRunner.


This might seem backward, stepping back from working executable code to a prototype, but if Reports and Usernote's Commenting and User Testing Integration continue to improve, they can add considerable value, in my opinion at this time. Anyway, especially if both the code and/or the prototype fall out of the same project file, it seems a nice bonus.

Comments (11)

photo
1

You will be able to import data from databases (in csv format) to the data masters in the next release (February the 22nd)

photo
1

Thanks very much, Victor. So, that kind of implies importing schema, because you will take the headers of the CSV as field names?

photo
1

No, only the values. You will need to define the attributes in the data master first.

photo
1

That's not good. Obviously, it makes two steps out of one, but also introduces opportunities for errors. Smart people will be using a test data generator, or at least a spreadsheet, so there's no gain in requiring the fields to be defined manually, and separately from the data.


I am currently working on a prototype where one DM will use 12 or more fields to accurately represent a user profile.


I hope you'll reconsider.

photo
1

The thing is we plan to have that feature too but in a later release.

photo
1

Thanks, Victor. It seems like a major productivity issue, and a great feature for JIM to demo. If you could just import a CSV, then drag the DM to the canvas, click Simulate and have a working prototype of a form or a data grid page, that would be really cool. Looking forward to the next release.

photo
1

Hey, Victor, in the last 11 days, or between now and the 22nd, did you find a way to work in schema import?


Obviously, any substantive data master with more than a handful of fields, there is abundant room for error in misaligned fields. I think it's reasonable to say that if you don't include schema import, you'll cost users hundreds of hours per month across your user base.


Is there anything we can do to help? Do you need sample data sets? Anything else?

photo
1

Well, the thing is we are in the final stages of stabilizing the 4.5 release and adding more functionality now is just too dangerous. But that feature has been planned for the 5.0 release we plan to launch on April. Maybe, if we feel that many users need this earlier we can think about launching a 4.5.1 update just with this in a few weeks or so.

photo
1

Thanks very much for the acknowledgement. I think that once users start seeing that they can import data into DMs, that schema import will be the next thing on many Wish Lists.

photo
1

Solved in Prototyper 4.6 release

photo
1

Thanks, Victor!