Re: [gnome-db] Feature requests : reverse engeneering & md5 stamps

[Rodrigo Moya <rodrigo gnome-db org>]

On Fri, 2002-12-13 at 14:56, Jean-Michel POURE wrote:
> Dear all,
> 
> As regards pgAdmin2, I was wondering if you could consider these would-be 
> features :
> 
> 6) SQL reverse engeneering. We may need a "rev_eng" field in each object 
> carrying the required SQL code to create the object.
> 
we already have this for almost all schemas. You get the SQL for tables,
procedures, etc

> For example, in the case of triggers : 
> rev_eng = 
> "CREATE TRIGGER foo BEFORE UPDATE ON bar FOR EACH ROW EXECUTE foo_bar('toto')"
> 
> pgSchema, the object layer of pgAdmin2, offers such a feature, which is very 
> useful.
> 
> In the case of GnomeDB, the beauty of reverse engeneering would be to provide 
> an easy migration of schemas ... from one database system to another.
> 
well, that will work when passing data from one place to the other, but
always using the same RDBMS. It surely won't work very well when
converting to different RDBMS.

> 7) Also, as regards of pgAdmin2, when working in teams, it is always hard to 
> know whether an object was updated or not. IMHO, the only solution would be 
> to store an MD5 for the field rev_eng (let's call it renv_eng_md5). Everytime 
> we want to modify an object, the provider would query renv_eng_md5 and 
> compare it with the old value. If some other developper modified the object, 
> we could then warn the user.
> 
but do you mean actually adding a field to the table (or create a new
table)? If so, I don't like the idea. libgda should be as little
intrusive as possible, and creating fields in the database (as pgaccess
does, and probably pgAdmin) is not a good idea, IMO.

cheers