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
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
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
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
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
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
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
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
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
... 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
10 matches
Mail list logo
