ckfinite
Posts: 377
Joined: 7/20/2013 Status: offline
|
quote:
ORIGINAL: SaneStatistician quote:
ORIGINAL: ckfinite It's actually a pretty nice normalized design, so it's easy to understand. You can edit most things by hand easily, you just have to remember/write down a lot of IDs to do so. I'm trying to get a nice abstraction layer set up for .NET (EF6), but there are some issues, mostly on the framework side. Please remember that by reverse-engineering the database you violate the terms of your license. Surprisingly, it isn't actually violating the license. To quote the license, quote:
You may not copy, reproduce, translate, decompile, reverse engineer, disassemble, modify, or create derivative works from the assembled code or any part thereof (Emphasis mine, this is from the EULA, S.2 ). This means that it does violate the license to use a decompiler like DotPeek on the Command executable (which I have not done), or to examine the CIL code, for that matter. However, unless the database is originally described in code that is then assembled (which I doubt), then it is not covered under the EULA. This isn't very hard to fix, as far as I can tell. They just need to change "the assembled code or any part thereof" to "the software and included data, or any part thereof". Based on the lack of a clause alone, it seems that they'd be okay with a third-party analysis of the DB. I'm more than happy to abide by their wishes, if they don't want a DB editor, though. What I do for JASSM-ERs on F-35...
|