Re: [GENERAL] [HACKERS] Remove MySQL Tools from Source?

2004-04-18 Thread Andrew Dunstan
Christopher Kings-Lynne said:
 But you would have to assign the copyright to them 

 If someone is going to make money from my code, I prefer it to be me,
 or  at least that everyone has a chance to do so rather than just one
 company.

 Well, then for the same reason we should write a Perl script that
 connects to MySQl and dumps in PGSql format.

 I think it's silly to try and read a MySQL dump and convert it - let's
 just dump straight from the source.

 Josh - I'm kind of keen to make this happen...


You might want to check out the DBIx::DB_Schema module at
http://search.cpan.org/~ivan/DBIx-DBSchema-0.23/DBSchema.pm

cheers

andrew



---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster


Re: [GENERAL] [HACKERS] Remove MySQL Tools from Source?

2004-04-18 Thread Shachar Shemesh
Tom Lane wrote:

These tools are a not insignificant part of our Plan for World
Domination ;-) so it would be good if somebody stepped up to the
plate and volunteered to take care of 'em.  Anybody?
 

Which brings me to another question

I have a bunch of perl scripts, as well as one user-defined type, for 
porting from SQL Server. Where should I place these?

Inside the PG source seemswrong. Then again, gborg does not seem to 
be accepting new projects at the moment. I can put them on 
sourceforge/berlios etc, and ask for a link, if you like.

 Shachar

--
Shachar Shemesh
Lingnu Open Source Consulting
http://www.lingnu.com/
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
   (send unregister YourEmailAddressHere to [EMAIL PROTECTED])


Re: [GENERAL] [HACKERS] Remove MySQL Tools from Source?

2004-04-18 Thread Andrew Dunstan


Shachar Shemesh wrote:

Tom Lane wrote:

These tools are a not insignificant part of our Plan for World
Domination ;-) so it would be good if somebody stepped up to the
plate and volunteered to take care of 'em.  Anybody?
 

Which brings me to another question

I have a bunch of perl scripts, as well as one user-defined type, for 
porting from SQL Server. Where should I place these?

Inside the PG source seemswrong. Then again, gborg does not seem 
to be accepting new projects at the moment. I can put them on 
sourceforge/berlios etc, and ask for a link, if you like.




The replacement for gborg should be available within a few days.

cheers

andrew

---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
 subscribe-nomail command to [EMAIL PROTECTED] so that your
 message can get through to the mailing list cleanly


Re: [GENERAL] [HACKERS] Remove MySQL Tools from Source?

2004-04-18 Thread Andrew Dunstan


Andrew Dunstan wrote:

Christopher Kings-Lynne said:
 

But you would have to assign the copyright to them 

If someone is going to make money from my code, I prefer it to be me,
or  at least that everyone has a chance to do so rather than just one
company.
 

Well, then for the same reason we should write a Perl script that
connects to MySQl and dumps in PGSql format.
I think it's silly to try and read a MySQL dump and convert it - let's
just dump straight from the source.
Josh - I'm kind of keen to make this happen...

   

You might want to check out the DBIx::DB_Schema module at
http://search.cpan.org/~ivan/DBIx-DBSchema-0.23/DBSchema.pm
And this also looks cool - I just came across it searching for something 
else:

http://sqlfairy.sourceforge.net/

cheers

andrew

 



---(end of broadcast)---
TIP 8: explain analyze is your friend


Re: [GENERAL] [HACKERS] Remove MySQL Tools from Source?

2004-04-17 Thread Jan Wieck
Christopher Kings-Lynne wrote:

... on projects.postgresql.org, or similar.They really aren't 
doing any good in /contrib.

I've already set up a category conversion tools on pgFoundry, and 
my idea was one project per target system.


I reckon that by far the best way to do a mysql2pgsql converter is to 
just modify mysqldump C source code to output in postgresql format! 


... and contribute it to MySQL :-)

Jan

--

#==#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.  #
#== [EMAIL PROTECTED] #


---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
 joining column's datatypes do not match


Re: [GENERAL] [HACKERS] Remove MySQL Tools from Source?

2004-04-17 Thread Andrew Dunstan


Jan Wieck wrote:

Christopher Kings-Lynne wrote:

... on projects.postgresql.org, or similar.They really aren't 
doing any good in /contrib.

I've already set up a category conversion tools on pgFoundry, and 
my idea was one project per target system.


I reckon that by far the best way to do a mysql2pgsql converter is to 
just modify mysqldump C source code to output in postgresql format! 


... and contribute it to MySQL :-)

But you would have to assign the copyright to them 

If someone is going to make money from my code, I prefer it to be me, or 
at least that everyone has a chance to do so rather than just one company.

cheers

andrew

---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
   (send unregister YourEmailAddressHere to [EMAIL PROTECTED])


Re: [GENERAL] [HACKERS] Remove MySQL Tools from Source?

2004-04-17 Thread Christopher Kings-Lynne
But you would have to assign the copyright to them 

If someone is going to make money from my code, I prefer it to be me, or 
at least that everyone has a chance to do so rather than just one company.
Well, then for the same reason we should write a Perl script that 
connects to MySQl and dumps in PGSql format.

I think it's silly to try and read a MySQL dump and convert it - let's 
just dump straight from the source.

Josh - I'm kind of keen to make this happen...

Chris

---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings


Re: [GENERAL] [HACKERS] Remove MySQL Tools from Source?

2004-04-16 Thread Josh Berkus
Scott,

 the sad thing is that while MySQL implemented a -ansi switch that 
 supposedly turns on ansi compliance, it only fixes about 1/2 of all the 
 non-compliance issues.  Yet another half-implemented feature... :)

Plus they completely broke ansi-compliance with the latest version of 
mysqldump, which is what I'm struggling with.   To quote one of the 
developers on #mysql:
Oh, that's not really a bug, it only affects ANSI mode.

However, Perl is superb at pattern-matching, so I've patched for it ...

-- 
-Josh Berkus
 Aglio Database Solutions
 San Francisco


---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]


Re: [GENERAL] [HACKERS] Remove MySQL Tools from Source?

2004-04-14 Thread Tom Lane
Josh Berkus [EMAIL PROTECTED] writes:
 And what to do with the other db conversion tools?  Seems they should be
 kept together.

 ... on projects.postgresql.org, or similar.They really aren't doing any 
 good in /contrib.

Fair enough.  They're not tightly tied to the backend, so I see no
strong reason to keep 'em in contrib rather than as independent
projects.

regards, tom lane

---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
  joining column's datatypes do not match


Re: [GENERAL] [HACKERS] Remove MySQL Tools from Source?

2004-04-14 Thread Christopher Kings-Lynne
... on projects.postgresql.org, or similar.They really aren't doing any 
good in /contrib.

I've already set up a category conversion tools on pgFoundry, and my idea 
was one project per target system.
I reckon that by far the best way to do a mysql2pgsql converter is to 
just modify mysqldump C source code to output in postgresql format!

Chris

---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster