Nabble - Tedia2Sql

Patch for recognizing presence of gunzip

2008-07-14T06:32:21Z

The test for the presence of 'gunzip' does not seem correct on Windows. Below is a patch to 1.2.12.

Perl now has 'gunzip' available through IO::Uncompress::Gunzip. Would a patch that used it be accepted?

===

$ diff ../tedia2sql-1.2.12/tedia2sql/tedia2sql ./tedia2sql
220a221
> $gunzipExists = ($? == 0 ? 1 : 0);

PK not recognized for association

2008-07-10T10:59:50Z

Attached is a .dia 0.96.1 file. There are only two tables (classes). Each has a PK defined by setting "Protected". However, running tedia2sql generates the following message. The 'sale_id' field is prefixed with '#' and an explicit index has been created for 'sale_id' in each table. Being part of the PK should be enoough, shouldn't it?

$ "/cygdrive/c/Documents and Settings/watsopau/../../Master/tedia2sql/tedia2sql/tedia2sql" -d -k -t oracle -i test1.dia -o test1
In association fk_sale_sale_sales_rep_rel sale_id doesn't refer to a primary key or unique index

Any suggestions? Thanks.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

test1.dia (37K) Download Attachment

Out of memory error?

2008-05-08T20:34:33Z

I get this error when trying to run the program:

Ran out of memory for input buffer at /usr/lib/perl5/XML/Parser/Expat.pm line 469.

Any thoughts? Attached is the file I want to convert to sql... it's just a quick throw together to see how this thing works.
Josiah Kiehl
http://www.josiahkiehl.com
http://www.timebridge.com/mytime/josiahkiehl [Availability]

"If I find in myself a desire which no experience in this world can satisfy, the most probable explanation is that I was made for another world."

-- C. S. Lewis (Mere Christianity)

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

databaseSchema.dia (3K) Download Attachment

Re: SQLite support

2008-02-03T10:33:37Z

Thank you for responding.
I should look into it and try to add it. Just, it will take some time,
even to start with it.

Martin

On 1/28/08, Mike Ginou <mike@...> wrote:

> Martin,
>
> There are no plans for adding SQLite in any incarnation. Unfortunately,
> tedia2sql hasn't seen any development love in a long while.
>
> If you'd like to add the support yourself, I will do my best to review
> and integrate your patch, though.
>
> Regards,
> Mike
>
> Martin Saturka wrote:
> > Hello,
> > I'd like to ask if you plan to add a support for SQLite3
> > (www.sqlite.org) into the tedia2sqlite.
> >
> > Martin
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@...
> > For additional commands, e-mail: users-help@...
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: SQLite support

2008-01-28T10:12:32Z

Martin,

There are no plans for adding SQLite in any incarnation. Unfortunately,
tedia2sql hasn't seen any development love in a long while.

If you'd like to add the support yourself, I will do my best to review
and integrate your patch, though.

Regards,
Mike

Martin Saturka wrote:

> Hello,
> I'd like to ask if you plan to add a support for SQLite3
> (www.sqlite.org) into the tedia2sqlite.
>
> Martin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

SQLite support

2008-01-27T12:30:33Z

Hello,
I'd like to ask if you plan to add a support for SQLite3
(www.sqlite.org) into the tedia2sqlite.

Martin

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Fwd: tedia2sql]

2007-11-24T09:33:37Z

I just wanted this to be recorded in the archives.

If anyone who reads this list actually has time to make these changes,
please do. Test them, report back!

-Mike

-------- Original Message --------
Subject: tedia2sql
Date: Tue, 6 Nov 2007 03:22:38 +0800
From: Beau Kissinger <mrkissinger@...>
To: mginou@..., ttiimmeelleessss@...

I found a bug in tedia2sql, and I added a line of code.

sub sqlComment($$) {
my $commentString = shift;

if ($opt_t eq 'db2' || $opt_t eq 'informix' || $opt_t eq 'ingres' || $opt_t
eq 'mssql' || $opt_t eq 'mysql' || $opt_t eq 'oracle' || $opt_t eq
'postgres' || $opt_t eq 'sybase' || $opt_t eq 'innodb') {
$commentString=~s/\n/ /g; # Process multi-line comment in Dia
return "-- $commentString";

} elsif ($opt_t eq 'sas') {
return "/* $commentString */";
}
}

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Missing feature tedia2sql

2007-11-14T06:36:32Z

Hi,

(not sure if this is the correct list, please forward in case not.)

First of all: thanks for this nice tool :-).
I am using it for quite a while and found it very useful.

I discovered recently a missing feature :
The CREATE statements are not database scoped.
e.g.
CREATE TABLE mytable (..
better:
CREATE TABLE mydatabase.mytable (..

In my case I had a table called 'Endpoint'. When executing the generated
CREATE statement, the server (MySQL 5.0.45 DB) refused it due to the
'Endpoint' name (this works however in mysql 4.x).
It did work when I used the scoped statement.
create table mydb.Endpoint (...

Thanks in advance,
Felix

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: mysql foreign key contraint bug

2007-11-08T11:50:50Z

I'm sorry, I didn't correct against the latest revision, just the one
in the ubuntu repository. The bug is still there though, it's just on
lines 2838 and 2840.

-Chris

On Nov 8, 2007 12:10 AM, Chris Dosé <chris.dose@...> wrote:

> Hi,
> I noticed a bug in the creation of foreign key constraints when using
> the mysql option. When printing the sql for foreign keys using the
> mysql or ingres types, it prints the first line of the alter table
> block as a comment, and at the end appends "for $opt_t" instead of the
> regular line delimiter. I have this diff file here:
>
> 2818c2818
> < $return = "alter table $className add constraint $constraintName" . $nl;
> ---
> > $return = &sqlComment("alter table $className add constraint $constraintName") . $nl;
> 2820c2820
> < $return .= $in . "$refTable ($refColumns) $goCommand";
> ---
> > $return .= $in . "$refTable ($refColumns) for $opt_t";
>
> That fixes the problem for me, but I don't know perl at all, so I may
> have done something not so good. Anyway, I like this project, it's
> been useful to me, and I hope this helps fix this problem permenantly.
>
> -Chris
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

mysql foreign key contraint bug

2007-11-07T22:10:00Z

Hi,
I noticed a bug in the creation of foreign key constraints when using
the mysql option. When printing the sql for foreign keys using the
mysql or ingres types, it prints the first line of the alter table
block as a comment, and at the end appends "for $opt_t" instead of the
regular line delimiter. I have this diff file here:

2818c2818
< $return = "alter table $className add constraint $constraintName" . $nl;
---
> $return = &sqlComment("alter table $className add constraint $constraintName") . $nl;
2820c2820
< $return .= $in . "$refTable ($refColumns) $goCommand";
---
> $return .= $in . "$refTable ($refColumns) for $opt_t";

That fixes the problem for me, but I don't know perl at all, so I may
have done something not so good. Anyway, I like this project, it's
been useful to me, and I hope this helps fix this problem permenantly.

-Chris

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Autoreply: [TEDIA2SQL-USERS] Patch: Don't lc constants in enums

2007-06-10T14:05:43Z

Vielen Dank f�r Ihre Nachricht. Ich bin vom 8. Juni 2007 bis zum 19. Juni 2007 im Urlaub und habe keinen Zugang zu meinen E-Mails. Wenden Sie sich daher in dringenden F�llen bitte an
Thomas Woinke:
t.woinke@...
Telefon 07121 348 121

--
konrad wacker

21TORR AGENCY gmbh
engineering unit

heinestrasse 72
d-72762 reutlingen
phone +49-7121-348-226
fax +49-7121-348-159
k.wacker@...
21TORR - die neue medien leidenschaft
www.21torr.com

--
Aktuelle Projekte von 21TORR live im Internet:

Die G-Klasse. Verwechslung ausgeschlossen.
http://www.mercedes-benz.com/g-klasse

Klaus ist raus! Wer kann ihn ersetzen?
http://www.klaus-ersetzen.de/
--
Gesch�ftsf�hrer 21TORR AGENCY gmbh:
Gaby Munz, Marcus Reiser, Alexander Hafemann

Amtsgericht Stuttgart HRB 353716

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Patch: Don't lc constants in enums

2007-06-10T14:05:38Z

Hi. It seems wrong to lowercase string constants in enums,
this patch will fix it.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

tedia2sql.patch (748 bytes) Download Attachment

Re: tedia2sql - backwards?

2007-05-20T09:20:40Z

There is a tool called sql2dia and another called AutoDia.

Neither generates a tedia2sql compliant diagram. AutoDia appears to
create UML diagrams, so those could probably be modified fairly easily.

If you do plan on using one of the above in conjunction with tedia2sql,
please report back about your experience.

Cheers,
Mike

Dominic Blythe wrote:
> Do you know of any DDL to DIA tools?
> Do you have any plans to make one?
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: Re: int or integer ?

2007-04-27T08:09:27Z

Hi,

I was using "integer" in my dia schema and the script was working fine
until I tried the last CVS version.

The "problem" with using "integer" is that type compatibility checks
fails comparing "serial <=> integer" on a relation, but works on
"serial <=> int" (check revision 1.65 on CVS).

The script *should* accept both of them as both are documented in
postgresql... But let say it would be a new feature for a release on a
galaxy far far away ;) The modif on the doc is well enough. I changed my
schema.

Thanks to both of you, timeless, Mike.

Have a nice week-end.

Massimiliano

Le jeudi 26 avril 2007 à 14:49 -0700, Time Less a écrit :

> On 4/26/07, Mike Ginou <mike@...> wrote:
> > About this integer/int thing, if 'int' is "the way", then it
> should at
> > least be mentioned somehow in the documentation page :
> > http://tedia2sql.tigris.org/usingtedia2sql.html
> >
> > There's some examples talking about using 'integer'.
>
> Yes, you're absolutely right. I'll put it on my list of things
> to do.
> I'm not very fast at getting to them though :)
>
> I don't think I'm fully understanding the issues with 'int' vs
> 'integer' here, but since we seem happy to refer to it as 'int' on the
> docs page as resolving the issue, I edited the docs and checked them
> in. The page now refers to 'int' rather than 'integer.'
>
> --
> timeless(ness)
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: Re: int or integer ?

2007-04-26T15:49:01Z

On 4/26/07, Mike Ginou <mike@...> wrote:

> About this integer/int thing, if 'int' is "the way", then it should at
> least be mentioned somehow in the documentation page :
> http://tedia2sql.tigris.org/usingtedia2sql.html
>
> There's some examples talking about using 'integer'.

Yes, you're absolutely right. I'll put it on my list of things to do.
I'm not very fast at getting to them though :)

I don't think I'm fully understanding the issues with 'int' vs 'integer' here, but since we seem happy to refer to it as 'int' on the docs page as resolving the issue, I edited the docs and checked them in. The page now refers to 'int' rather than 'integer.'

--
timeless(ness)

Re: Re: int or integer ?

2007-04-26T08:01:50Z

> About this integer/int thing, if 'int' is "the way", then it should at
> least be mentioned somehow in the documentation page :
> http://tedia2sql.tigris.org/usingtedia2sql.html
>
> There's some examples talking about using 'integer'.

Yes, you're absolutely right. I'll put it on my list of things to do.
I'm not very fast at getting to them though :)

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: Re: int or integer ?

2007-04-26T01:49:20Z

Hi Mike,

Thanks for you answer. I was sure you would propose me to code a
function :) That was the solution I had in mind to resolve this matter.
I may perhaps have the time in the next months. I let you know.

About this integer/int thing, if 'int' is "the way", then it should at
least be mentioned somehow in the documentation page :
http://tedia2sql.tigris.org/usingtedia2sql.html

There's some examples talking about using 'integer'.

Just my 2cts.

Massimiliano

Le mardi 24 avril 2007 à 10:17 -0400, Mike Ginou a écrit :

> Massimiliano,
>
> I see the problem, however, since int and integer are synonyms according
> to the PostgreSQL manual. Therefore I cannot make the simple change that
> you describe. To do so would mean that others who use 'int' rather than
> 'integer' in their classes will encounter the same problem.
>
> I investigated making changes to the function that determines type
> mismatches for associations, however the change would be complex and is
> generally beyond the type of maintenance work that is done for this project.
>
> If you would like to work on it and submit a change, I would be happy to
> review it. The relevant subroutine is generateOneToAnyAssociation (there
> may be some other subroutines that require modification as well). What
> would be required is to parse out the attributes of the association and
> rather than simply comparing them directly, a new comparison function
> would be needed. The comparison function would allow for any special
> case comparisons to be made. In the case of most DBs (and in your
> particular example, postgres) int is a synonym for integer thus an
> association with int on one side and integer on the other would be
> considered a match.
>
> -Mike
>
>
> Massimiliano Franco wrote:
> > Hello,
> >
> > I created a quick Gentoo ebuild to test the latest CVS version of
> > tedia2sql.
> >
> > I'm using the 'postgres' DB and I encountered a problem with relations
> > between tables when in the first table I have an entry with a serial
> > type and in the second I have an integer type.
> >
> > I noticed that the 1.66 revision introduces a treatment on the serial
> > type:
> > ***********************
> > + # Returns base type of some DMBS specyfic types (eg in PostgreSQL
> > serial is int)
> > + sub getBaseType($) {
> > + my $typeName = shift;
> > + if ($opt_t eq 'postgres') {
> > + if ($typeName eq 'serial' || $typeName eq 'SERIAL') {
> > + return 'int';
> > + }
> > + } else {
> > + return $typeName;
> > + }
> > + }
> > ***********************
> > It's the "return 'int'" that annoys me. Since this revision the script
> > exits with this kind of error:
> > Attribute types (id_client is serial, id_client is integer) don't match
> > in clientsCli_con (clients,cli_con)
> > Number or types of (id_client) don't match (id_client) in clientsCli_con
> >
> > I suggest replacing "return 'int'" to "return 'integer'" as the mapping
> > is already handled. I don't know if it breaks other things.
> >
> > Thanks for your time.
> >
> > Have a nice day !
> >
> > Massimo
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: utf8 support

2007-04-25T20:06:15Z

Mike Ginou escribió:

>> Today working on some files I see these aren't saved at utf8 and ask why?
>> looking in my system I see utf8 don't was my default locale!
>> when upgrade debian, the locale utf8 dissapear like default,
>> so now revert the code of tedia2sql I haved to change and work perfectly!
>>
>
>
> So to be clear the standard debian standard version of tedia2sql works fine?
>
> -Mike
>
> PS - I'm glad it
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>
>

work very pretty fine!

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: utf8 support

2007-04-25T19:08:00Z

> Today working on some files I see these aren't saved at utf8 and ask why?
> looking in my system I see utf8 don't was my default locale!
> when upgrade debian, the locale utf8 dissapear like default,
> so now revert the code of tedia2sql I haved to change and work perfectly!

So to be clear the standard debian standard version of tedia2sql works fine?

-Mike

PS - I'm glad it

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: int or integer ?

2007-04-24T08:17:56Z

Massimiliano,

I see the problem, however, since int and integer are synonyms according
to the PostgreSQL manual. Therefore I cannot make the simple change that
you describe. To do so would mean that others who use 'int' rather than
'integer' in their classes will encounter the same problem.

I investigated making changes to the function that determines type
mismatches for associations, however the change would be complex and is
generally beyond the type of maintenance work that is done for this project.

If you would like to work on it and submit a change, I would be happy to
review it. The relevant subroutine is generateOneToAnyAssociation (there
may be some other subroutines that require modification as well). What
would be required is to parse out the attributes of the association and
rather than simply comparing them directly, a new comparison function
would be needed. The comparison function would allow for any special
case comparisons to be made. In the case of most DBs (and in your
particular example, postgres) int is a synonym for integer thus an
association with int on one side and integer on the other would be
considered a match.

-Mike

Massimiliano Franco wrote:

> Hello,
>
> I created a quick Gentoo ebuild to test the latest CVS version of
> tedia2sql.
>
> I'm using the 'postgres' DB and I encountered a problem with relations
> between tables when in the first table I have an entry with a serial
> type and in the second I have an integer type.
>
> I noticed that the 1.66 revision introduces a treatment on the serial
> type:
> ***********************
> + # Returns base type of some DMBS specyfic types (eg in PostgreSQL
> serial is int)
> + sub getBaseType($) {
> + my $typeName = shift;
> + if ($opt_t eq 'postgres') {
> + if ($typeName eq 'serial' || $typeName eq 'SERIAL') {
> + return 'int';
> + }
> + } else {
> + return $typeName;
> + }
> + }
> ***********************
> It's the "return 'int'" that annoys me. Since this revision the script
> exits with this kind of error:
> Attribute types (id_client is serial, id_client is integer) don't match
> in clientsCli_con (clients,cli_con)
> Number or types of (id_client) don't match (id_client) in clientsCli_con
>
> I suggest replacing "return 'int'" to "return 'integer'" as the mapping
> is already handled. I don't know if it breaks other things.
>
> Thanks for your time.
>
> Have a nice day !
>
> Massimo
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: utf8 support

2007-04-24T07:57:06Z

Alvaro,

Some preliminary investigation of utf8 support was made some time ago.
At the time it was concluded that simply adding

use open ':locale';

was sufficient to fix encoding mishaps (provided your locale is set
properly in your environment).

I have attached a very small patch that makes that fix, can you test it out?

Alvaro wrote:

> Hi,
> I am new user of tedia2sql, because I am spanish speaking have some
> problems with inserts created by tedia2sql because don't have utf8
> encode support, so I did a patch in perl code.
>
> I don't know anything about perl, but I tryed and it works!
>
> I explain it:
>
> first you have tell perl about encode type to open and save files and
> use of encode/decode functions:
>
> use open IO => ':utf8';
> use Encode
>
> I think that value (utf8) must be passed trough command line,
> also there is a way to use 'locale' instead of 'utf8'
>
> then when teadia2sql do:
> print $iout &createInsertStatements ($compName, $compText);
>
> you have to do
>
> print $iout &createInsertStatements ($compName, decode('utf8,'$compText));
>
> again it must be a value passed by command-line
>
> Well I say again I don't know perl so checkit out please, if you like me
> submit
> a patch with command-line support and well code please tell me how I
> submit that.
>
> Greate work! very useful to me!
> thanks
>
> Alvaro
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>

Index: tedia2sql
===================================================================
RCS file: /cvs/tedia2sql/tedia2sql,v
retrieving revision 1.68
diff -u -r1.68 tedia2sql
--- tedia2sql 19 Dec 2004 03:44:42 -0000 1.68
+++ tedia2sql 24 Apr 2007 13:52:28 -0000
@@ -52,6 +52,8 @@
# actual license is at http://www.gnu.org/licenses/gpl.txt as well.
# ------------------------ LICENSE SUMMARY ------------------------------------

+use open ':locale';
+
sub parseRCFile($);
sub checkExtraClauseUsage();
sub checkMacroUsage();

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

utf8 support

2007-04-23T11:36:27Z

Hi,
I am new user of tedia2sql, because I am spanish speaking have some
problems with inserts created by tedia2sql because don't have utf8
encode support, so I did a patch in perl code.

I don't know anything about perl, but I tryed and it works!

I explain it:

first you have tell perl about encode type to open and save files and
use of encode/decode functions:

use open IO => ':utf8';
use Encode

I think that value (utf8) must be passed trough command line,
also there is a way to use 'locale' instead of 'utf8'

then when teadia2sql do:
print $iout &createInsertStatements ($compName, $compText);

you have to do

print $iout &createInsertStatements ($compName, decode('utf8,'$compText));

again it must be a value passed by command-line

Well I say again I don't know perl so checkit out please, if you like me
submit
a patch with command-line support and well code please tell me how I
submit that.

Greate work! very useful to me!
thanks

Alvaro

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: postgres inheritance

2007-04-17T23:27:35Z

Is this diff format suitable to you?

Index: tedia2sql
===================================================================
RCS file: /cvs/tedia2sql/tedia2sql,v
retrieving revision 1.68
diff -r1.68 tedia2sql
1210a1211,1214
> if ($opt_t eq 'postgres') {
> &addInheritance ($createFileHandle, $objectOperations)
> }
>
1242a1247,1270

> # Inheritance is temporarily resolved using a class operation called "inherits", whose
> # type is interpreted as the name of the table the class is inheriting from.
> # The correct way to go should be the use of generalization assocation links.
> #
> # TODO: interpret relation "generalization, class inheritance" from UML diagram instead.
> # Implement table declaration ordering (they must be declared after their ancestor tables),
> # probably safest way is create inheritance tree during diagram scanning.
> # Handle multiple inheritance: inherits (a,b,c)
> #
>
> sub addInheritance($$$) {
>
> my $createFileHandle = shift;
> my $theOperations = shift;
>
> foreach my $oneOp (@$theOperations) {
> my ($opName, $opType, $opParams) = @$oneOp;
> if ($opName eq 'inherits') {
> print "* table inherits from: $opType\n" if ($verbose);
> print $createFileHandle "inherits ($opType) ";
> }
> }
> }
>

2007/4/18, Mike Ginou <mike@...>:

> Yes! Please do forward the patch. I would very much like to take a look
> at it.
>
> -Mike
>
> albert wrote:
> > Mike,
> >
> > Thank you for your support. I have momentarily hacked tedia2sql perl
> > script to add inheritance to postgres tables when a class is found to
> > have an operation named "inherits". Its type is used to refer to the
> > table name it inherits from. Ugly, but it works for the timing
> > deadline I am currently on.
> >
> > Problems:
> >
> > 1. The correct way to interpret inheritance is, as I understand it,
> > make use of the "Generalization" association type. Have digged into
> > the source and guess the correct approach is to add the inheritance
> > info into the class definition when traversing through the association
> > nodes (a function called generateAssocSqlFromNodeList if I'm not
> > mistaken).
> >
> > 2. On complex diagrams, the ordering of table definitions will
> > eventually upset postgres at import time (an inheriting table has to
> > be defined after the table it inherits from). Not sure if Dia's object
> > Z-order might help, but safest solution I guess is to build a
> > parent-child relationship tree during diagram scanning.
> >
> > Unfortunately am not very skillfull on Perl, but I am more than happy
> > to help implement and document it if there's interest. Let me know if
> > you'd like me to forward the temporary patch.
> >
> > best regards
> > albert
> >
> > 2007/4/18, Mike Ginou <mike@...>:
> >> Albert,
> >>
> >> Unfortunately, I don't have any experience with inheritence in an RDBMS.
> >> Therefore, I don't think I'm in a good position to add this feature.
> >>
> >> If you're willing to dig into it yourself, I would be more than happy to
> >> offer suggestions and to answer any questions you might have.
> >>
> >> Cheers,
> >> Mike
> >>
> >> albert wrote:
> >> > Hi all,
> >> >
> >> > I've been searching through multiple sites including this official
> >> > mailing list, on how to implement postgres table inheritance using
> >> > tedia2sql. There's some mentions about this feature being implemented,
> >> > but sadly enough, grepping through a fresh cvs checked-out revision
> >> > has returned me no results.
> >> >
> >> > I'm looking for a way to represent this postgres definition:
> >> >
> >> > CREATE TABLE a (...) with oids;
> >> > CREATE TABLE b (...) inherits a;
> >> >
> >> > on a dia diagram which tedia2sql can understand properly.
> >> >
> >> > best regards
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: users-unsubscribe@...
> >> > For additional commands, e-mail: users-help@...
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@...
> >> For additional commands, e-mail: users-help@...
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@...
> > For additional commands, e-mail: users-help@...
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: postgres inheritance

2007-04-17T23:21:15Z

Yes! Please do forward the patch. I would very much like to take a look
at it.

-Mike

albert wrote:

> Mike,
>
> Thank you for your support. I have momentarily hacked tedia2sql perl
> script to add inheritance to postgres tables when a class is found to
> have an operation named "inherits". Its type is used to refer to the
> table name it inherits from. Ugly, but it works for the timing
> deadline I am currently on.
>
> Problems:
>
> 1. The correct way to interpret inheritance is, as I understand it,
> make use of the "Generalization" association type. Have digged into
> the source and guess the correct approach is to add the inheritance
> info into the class definition when traversing through the association
> nodes (a function called generateAssocSqlFromNodeList if I'm not
> mistaken).
>
> 2. On complex diagrams, the ordering of table definitions will
> eventually upset postgres at import time (an inheriting table has to
> be defined after the table it inherits from). Not sure if Dia's object
> Z-order might help, but safest solution I guess is to build a
> parent-child relationship tree during diagram scanning.
>
> Unfortunately am not very skillfull on Perl, but I am more than happy
> to help implement and document it if there's interest. Let me know if
> you'd like me to forward the temporary patch.
>
> best regards
> albert
>
> 2007/4/18, Mike Ginou <mike@...>:
>> Albert,
>>
>> Unfortunately, I don't have any experience with inheritence in an RDBMS.
>> Therefore, I don't think I'm in a good position to add this feature.
>>
>> If you're willing to dig into it yourself, I would be more than happy to
>> offer suggestions and to answer any questions you might have.
>>
>> Cheers,
>> Mike
>>
>> albert wrote:
>> > Hi all,
>> >
>> > I've been searching through multiple sites including this official
>> > mailing list, on how to implement postgres table inheritance using
>> > tedia2sql. There's some mentions about this feature being implemented,
>> > but sadly enough, grepping through a fresh cvs checked-out revision
>> > has returned me no results.
>> >
>> > I'm looking for a way to represent this postgres definition:
>> >
>> > CREATE TABLE a (...) with oids;
>> > CREATE TABLE b (...) inherits a;
>> >
>> > on a dia diagram which tedia2sql can understand properly.
>> >
>> > best regards
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: users-unsubscribe@...
>> > For additional commands, e-mail: users-help@...
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@...
>> For additional commands, e-mail: users-help@...
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: postgres inheritance

2007-04-17T19:54:44Z

Mike,

Thank you for your support. I have momentarily hacked tedia2sql perl
script to add inheritance to postgres tables when a class is found to
have an operation named "inherits". Its type is used to refer to the
table name it inherits from. Ugly, but it works for the timing
deadline I am currently on.

Problems:

1. The correct way to interpret inheritance is, as I understand it,
make use of the "Generalization" association type. Have digged into
the source and guess the correct approach is to add the inheritance
info into the class definition when traversing through the association
nodes (a function called generateAssocSqlFromNodeList if I'm not
mistaken).

2. On complex diagrams, the ordering of table definitions will
eventually upset postgres at import time (an inheriting table has to
be defined after the table it inherits from). Not sure if Dia's object
Z-order might help, but safest solution I guess is to build a
parent-child relationship tree during diagram scanning.

Unfortunately am not very skillfull on Perl, but I am more than happy
to help implement and document it if there's interest. Let me know if
you'd like me to forward the temporary patch.

best regards
albert

2007/4/18, Mike Ginou <mike@...>:

> Albert,
>
> Unfortunately, I don't have any experience with inheritence in an RDBMS.
> Therefore, I don't think I'm in a good position to add this feature.
>
> If you're willing to dig into it yourself, I would be more than happy to
> offer suggestions and to answer any questions you might have.
>
> Cheers,
> Mike
>
> albert wrote:
> > Hi all,
> >
> > I've been searching through multiple sites including this official
> > mailing list, on how to implement postgres table inheritance using
> > tedia2sql. There's some mentions about this feature being implemented,
> > but sadly enough, grepping through a fresh cvs checked-out revision
> > has returned me no results.
> >
> > I'm looking for a way to represent this postgres definition:
> >
> > CREATE TABLE a (...) with oids;
> > CREATE TABLE b (...) inherits a;
> >
> > on a dia diagram which tedia2sql can understand properly.
> >
> > best regards
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@...
> > For additional commands, e-mail: users-help@...
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: postgres inheritance

2007-04-17T14:51:57Z

Albert,

Unfortunately, I don't have any experience with inheritence in an RDBMS.
Therefore, I don't think I'm in a good position to add this feature.

If you're willing to dig into it yourself, I would be more than happy to
offer suggestions and to answer any questions you might have.

Cheers,
Mike

albert wrote:

> Hi all,
>
> I've been searching through multiple sites including this official
> mailing list, on how to implement postgres table inheritance using
> tedia2sql. There's some mentions about this feature being implemented,
> but sadly enough, grepping through a fresh cvs checked-out revision
> has returned me no results.
>
> I'm looking for a way to represent this postgres definition:
>
> CREATE TABLE a (...) with oids;
> CREATE TABLE b (...) inherits a;
>
> on a dia diagram which tedia2sql can understand properly.
>
> best regards
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

postgres inheritance

2007-04-16T22:55:23Z

Hi all,

I've been searching through multiple sites including this official
mailing list, on how to implement postgres table inheritance using
tedia2sql. There's some mentions about this feature being implemented,
but sadly enough, grepping through a fresh cvs checked-out revision
has returned me no results.

I'm looking for a way to represent this postgres definition:

CREATE TABLE a (...) with oids;
CREATE TABLE b (...) inherits a;

on a dia diagram which tedia2sql can understand properly.

best regards

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: Mysql Syntax

2007-03-09T15:08:18Z

Mike,

Thanks for the info. Everything is working fine now. The tool works really well.

Thanks

On Fri, 2007-03-09 at 14:55 -0500, Mike Ginou wrote:

> I did not put in the default key word and am not sure how I got them in there.

tedia2sql puts it there automatically when you place unrecognized values
in the value field. Examples of recognized values are "not null" and
"auto_increment". Anything that tedia2sql doesn't recognize as a valid
keyword for a column is interpreted as being the column's default value.

> 
> Thanks for the help.
> 
> 
> On Fri, 2007-03-09 at 11:37 -0500, Mike Ginou wrote:
>> Robert,
>>
>> I created a very simple diagram that covers the basic schema you have
>> shown below.
>>
>> I think you wanted to make the columns varchar(40) (variable character
>> fields with a maximum length of 40). To do that you simply specify the
>> length in parentheses as part of the datatype.
>>
>> Mike
>>
>> Robert Fulcher wrote:
>> > I have a single table and trying to get the hang of building tables in
>> > dia and them exporting them to mysql.  I can't get a single table to go
>> > over and am not sure what I am doing wrong.  It comes down to sql syntax
>> > that is created by tedia2sql (based on what I put in the uml model). 
>> > Here is what I get:
>> > 
>> > tiadia2sql output:
>> > 
>> > create table contacts (
>> >   id                        int default 10 not null,
>> >   firstname                 varchar default 40 NULL,
>> >   lastname                  varchar default 40,
>> >   created                   datetime,
>> >   modified                  datetime,
>> >   constraint pk_Contacts primary key (id)
>> > ) ;
>> > 
>> > When I try and run it I get:
>> > 
>> > *SQL query:*
>> > 
>> > CREATE TABLE contacts(
>> > 
>> > id int default 10 NOT NULL ,
>> > firstname varchar default 40 NULL ,
>> > lastname varchar default 40,
>> > created datetime,
>> > modified datetime,
>> > CONSTRAINT pk_Contacts PRIMARY KEY ( id ) );
>> > 
>> > 
>> > 
>> > *MySQL said: *Documentation
>> > <http://dev.mysql.com/doc/refman/5.0/en/error-returns.html>
>> > 
>> > #1064 - You have an error in your SQL syntax; check the manual that
>> > corresponds to your MySQL server version for the right syntax to use
>> > near 'default 40 NULL,
>> >   lastname                  varchar default 40,
>> >   created    ' at line 3
>> > 
>> > 
>> > Does anyone know how I can fix this?  I know that I am not putting the
>> > info into the uml correctly but am not sure what and how to correct. 
>> > Also I am using phpmyadmin is there a better tool for running the
>> > scripts that are created.
>> > 
>> > Thanks
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@... <mailto:users-unsubscribe@...>
>> For additional commands, e-mail: users-help@... <mailto:users-help@...>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: Mysql Syntax

2007-03-09T11:55:13Z

> I did not put in the default key word and am not sure how I got them in there.

tedia2sql puts it there automatically when you place unrecognized values
in the value field. Examples of recognized values are "not null" and
"auto_increment". Anything that tedia2sql doesn't recognize as a valid
keyword for a column is interpreted as being the column's default value.

>
> Thanks for the help.
>
>
> On Fri, 2007-03-09 at 11:37 -0500, Mike Ginou wrote:
>> Robert,
>>
>> I created a very simple diagram that covers the basic schema you have
>> shown below.
>>
>> I think you wanted to make the columns varchar(40) (variable character
>> fields with a maximum length of 40). To do that you simply specify the
>> length in parentheses as part of the datatype.
>>
>> Mike
>>
>> Robert Fulcher wrote:
>> > I have a single table and trying to get the hang of building tables in
>> > dia and them exporting them to mysql. I can't get a single table to go
>> > over and am not sure what I am doing wrong. It comes down to sql syntax
>> > that is created by tedia2sql (based on what I put in the uml model).
>> > Here is what I get:
>> >
>> > tiadia2sql output:
>> >
>> > create table contacts (
>> > id int default 10 not null,
>> > firstname varchar default 40 NULL,
>> > lastname varchar default 40,
>> > created datetime,
>> > modified datetime,
>> > constraint pk_Contacts primary key (id)
>> > ) ;
>> >
>> > When I try and run it I get:
>> >
>> > *SQL query:*
>> >
>> > CREATE TABLE contacts(
>> >
>> > id int default 10 NOT NULL ,
>> > firstname varchar default 40 NULL ,
>> > lastname varchar default 40,
>> > created datetime,
>> > modified datetime,
>> > CONSTRAINT pk_Contacts PRIMARY KEY ( id ) );
>> >
>> >
>> >
>> > *MySQL said: *Documentation
>> > <http://dev.mysql.com/doc/refman/5.0/en/error-returns.html>
>> >
>> > #1064 - You have an error in your SQL syntax; check the manual that
>> > corresponds to your MySQL server version for the right syntax to use
>> > near 'default 40 NULL,
>> > lastname varchar default 40,
>> > created ' at line 3
>> >
>> >
>> > Does anyone know how I can fix this? I know that I am not putting the
>> > info into the uml correctly but am not sure what and how to correct.
>> > Also I am using phpmyadmin is there a better tool for running the
>> > scripts that are created.
>> >
>> > Thanks
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@... <mailto:users-unsubscribe@...>
>> For additional commands, e-mail: users-help@... <mailto:users-help@...>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: Mysql Syntax

2007-03-09T10:45:06Z

Mike,

Thanks I will give it a try tonight. I did not put in the default key word and am not sure how I got them in there.

Thanks for the help.

On Fri, 2007-03-09 at 11:37 -0500, Mike Ginou wrote:

Robert,

I created a very simple diagram that covers the basic schema you have
shown below.

I think you wanted to make the columns varchar(40) (variable character
fields with a maximum length of 40). To do that you simply specify the
length in parentheses as part of the datatype.

Mike

Robert Fulcher wrote:
> I have a single table and trying to get the hang of building tables in
> dia and them exporting them to mysql.  I can't get a single table to go
> over and am not sure what I am doing wrong.  It comes down to sql syntax
> that is created by tedia2sql (based on what I put in the uml model). 
> Here is what I get:
> 
> tiadia2sql output:
> 
> create table contacts (
>   id                        int default 10 not null,
>   firstname                 varchar default 40 NULL,
>   lastname                  varchar default 40,
>   created                   datetime,
>   modified                  datetime,
>   constraint pk_Contacts primary key (id)
> ) ;
> 
> When I try and run it I get:
> 
> *SQL query:*
> 
> CREATE TABLE contacts(
> 
> id int default 10 NOT NULL ,
> firstname varchar default 40 NULL ,
> lastname varchar default 40,
> created datetime,
> modified datetime,
> CONSTRAINT pk_Contacts PRIMARY KEY ( id ) );
> 
> 
> 
> *MySQL said: *Documentation
> <http://dev.mysql.com/doc/refman/5.0/en/error-returns.html>
> 
> #1064 - You have an error in your SQL syntax; check the manual that
> corresponds to your MySQL server version for the right syntax to use
> near 'default 40 NULL,
>   lastname                  varchar default 40,
>   created    ' at line 3
> 
> 
> Does anyone know how I can fix this?  I know that I am not putting the
> info into the uml correctly but am not sure what and how to correct. 
> Also I am using phpmyadmin is there a better tool for running the
> scripts that are created.
> 
> Thanks
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Re: Mysql Syntax

2007-03-09T10:27:51Z

In MySQL you can't just declare a column "varchar" it must have a max length. Try "varchar(64)" or whatever length you think is maximal.

#1064 - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'default 40 NULL,
lastname varchar default 40,
created ' at line 3

--
timeless(ness)

Re: Mysql Syntax

2007-03-09T08:37:26Z

Robert,

I created a very simple diagram that covers the basic schema you have
shown below.

I think you wanted to make the columns varchar(40) (variable character
fields with a maximum length of 40). To do that you simply specify the
length in parentheses as part of the datatype.

Mike

Robert Fulcher wrote:

> I have a single table and trying to get the hang of building tables in
> dia and them exporting them to mysql. I can't get a single table to go
> over and am not sure what I am doing wrong. It comes down to sql syntax
> that is created by tedia2sql (based on what I put in the uml model).
> Here is what I get:
>
> tiadia2sql output:
>
> create table contacts (
> id int default 10 not null,
> firstname varchar default 40 NULL,
> lastname varchar default 40,
> created datetime,
> modified datetime,
> constraint pk_Contacts primary key (id)
> ) ;
>
> When I try and run it I get:
>
> *SQL query:*
>
> CREATE TABLE contacts(
>
> id int default 10 NOT NULL ,
> firstname varchar default 40 NULL ,
> lastname varchar default 40,
> created datetime,
> modified datetime,
> CONSTRAINT pk_Contacts PRIMARY KEY ( id ) );
>
>
>
> *MySQL said: *Documentation
> <http://dev.mysql.com/doc/refman/5.0/en/error-returns.html>
>
> #1064 - You have an error in your SQL syntax; check the manual that
> corresponds to your MySQL server version for the right syntax to use
> near 'default 40 NULL,
> lastname varchar default 40,
> created ' at line 3
>
>
> Does anyone know how I can fix this? I know that I am not putting the
> info into the uml correctly but am not sure what and how to correct.
> Also I am using phpmyadmin is there a better tool for running the
> scripts that are created.
>
> Thanks

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

db.dia (1K) Download Attachment

Re: Mysql Syntax

2007-03-09T08:19:06Z

There is certainly an error in the tedia2sql output. As the error
message indicates, the NULL as part of the firstname column definition
should not be there. Additionally the default clauses are definitely
confusing. Do you really want those, or are they just artifacts of
tedia2sql being confusing?

What *should* the script look like?

Mike

Robert Fulcher wrote:

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

Mysql Syntax

2007-03-09T05:44:45Z

I have a single table and trying to get the hang of building tables in dia and them exporting them to mysql. I can't get a single table to go over and am not sure what I am doing wrong. It comes down to sql syntax that is created by tedia2sql (based on what I put in the uml model). Here is what I get:

tiadia2sql output:

create table contacts (
id                        int default 10 not null,
firstname                 varchar default 40 NULL,
lastname                  varchar default 40,
created                   datetime,
modified                  datetime,
constraint pk_Contacts primary key (id)
) ;

When I try and run it I get:

SQL query:

CREATE TABLE contacts(

id int default 10 NOT NULL ,
firstname varchar default 40 NULL ,
lastname varchar default 40,
created datetime,
modified datetime,
CONSTRAINT pk_Contacts PRIMARY KEY ( id ) );

MySQL said:

#1064 - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'default 40 NULL,
  lastname                  varchar default 40,
created    ' at line 3

Does anyone know how I can fix this? I know that I am not putting the info into the uml correctly but am not sure what and how to correct. Also I am using phpmyadmin is there a better tool for running the scripts that are created.

Thanks