Andrew Dunstan wrote:
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
Shachar,
> I have a bunch of perl scripts, as well as one user-defined type, for
> porting from SQL Server. Where should I place these?
Give us a few days. We'll be announcing the opening of the new projects site
soon (like, wednesday).
Regrettably, the perfect feature for this sort of thing,
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 reas
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
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 t
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 writ
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 dump
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
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 con
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
mysqld
On Fri, 16 Apr 2004, Christopher Kings-Lynne wrote:
> > I always ran one of the 2 scripts (can't remember which one) and after that
> > started checking the dump file, because there were things that didn't get
> > changed correctly[1].
> >
> > [1]: I always remember the first conversion I did.
I always ran one of the 2 scripts (can't remember which one) and after that
started checking the dump file, because there were things that didn't get
changed correctly[1].
[1]: I always remember the first conversion I did. I found out that MySQL
accepted dates like 30/2/2000 or 0-0-.
Very o
El Mié 14 Abr 2004 22:22, Christopher Kings-Lynne escribió:
> > ... 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 t
... 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 mysqldum
On Wed, 14 Apr 2004, Bruce Momjian wrote:
> > I'd be happy to take the lead as maintainer of my2pg. But, I want to move it
> > to pgFoundry (due for launch as soon as I get my other 10 super-urgent tasks
> > out of the way) , and take it out of /contrib. I feel pretty strongly
> > that it wil
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
Bruce,
> 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.
I've already set up a category "conversion tools" on pgFoundry, and my idea
was one project per targe
Marc G. Fournier wrote:
> On Wed, 14 Apr 2004, Bruce Momjian wrote:
>
> > > I'd be happy to take the lead as maintainer of my2pg. But, I want to move it
> > > to pgFoundry (due for launch as soon as I get my other 10 super-urgent tasks
> > > out of the way) , and take it out of /contrib. I fe
Josh Berkus wrote:
> Tom,
>
> > Hmm ... seems like the big question is not "where to keep them" but
> > "who's gonna maintain them" ... without active maintenance they're
> > just dead bits wherever they're stored, because MySQL and Postgres
> > are both moving targets.
> >
> > These tools are a n
Tom,
> Hmm ... seems like the big question is not "where to keep them" but
> "who's gonna maintain them" ... without active maintenance they're
> just dead bits wherever they're stored, because MySQL and Postgres
> are both moving targets.
>
> These tools are a not insignificant part of our Plan f
Josh Berkus <[EMAIL PROTECTED]> writes:
> I'm thinking it's time to remove the "MySQL" conversion tools from the
> PostgreSQL source tree and put them somewhere they might be maintained.
> I've just done some testing, and neither one works with current versions of
> MySQLdump.
Hmm ... seems l
Folks,
I'm thinking it's time to remove the "MySQL" conversion tools from the
PostgreSQL source tree and put them somewhere they might be maintained.
I've just done some testing, and neither one works with current versions of
MySQLdump.
--
-Josh Berkus
Aglio Database Solutions
San Francis
22 matches
Mail list logo
