in reply to Parse PHP or Perl and Reconstruct MySQL Schema

(following paragraph added in update)

I'm being very presumptuous here, in that you didn't mention trying to get your hands on the specs from which the PHP and Perl where written. If you have tried to get them, I apologize.

(end of addition)

Considering that somebody managed to lose an entire database (and its backups?), I guess it would be too much to hope for somebody actually having the documents describing the database tables floating around.

My thinking is that whoever wrote the PHP and Perl code would have needed descriptions of the database in order to do anything. If this documentation is available, even if slightly outdated, it would make your task easier. Even the original specifications from which the Perl and PHP were written would help.

emc

e(π√−1) = −1
  • Comment on Re: Parse PHP or Perl and Reconstruct MySQL Schema

Replies are listed 'Best First'.
Re^2: Parse PHP or Perl and Reconstruct MySQL Schema
by UnderMine (Friar) on Jun 06, 2006 at 05:35 UTC
    This is a classic example of why you should include a database schema as part of your release (but not globally accessible as that a security risk).

    There are various pieces of software that can generate schemas one of the better and cheaper is Dezign for Databases.
    For simple to use, generates DDL schemas for large variety of databases, can reverse engineer schemas from source or database connections.
    Against only available for windows, cost varies between $230 and $700 depending on version.

    Used this on a number of projects, especially useful when the coder never documented his database and just let it evolve.

    Hope it helps
    UnderMine