Author: KAM.covad
Posted: 2009-04-30 03:59:26 Link
What we need is an easy migration to PostgreSQL from VFP. Unattended =
installation from CD and a replacement for INSERT INTO FROM NAME, =
GATHER, etc
Then it would be easier to migrate to something like Python if necessary =
some day.
*********************************
Below is Joshua Drake's take on Oracle purchasing Sun:
I see a large possibility of mass migration from MySQL by non web =
applications.=20
The obvious choice is PostgreSQL because of the BSD license and the =
maturity of the software.
In conclusion I expect that MySQL in two years likely won't exist except =
on the most tertiary level. Most new projects will be developed in=20
either PostgreSQL, Firebird or one of the forks (MariaDB, Drizzle).
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
Author: Ted Roche
Posted: 2009-04-30 07:51:28 Link
On Thu, Apr 30, 2009 at 3:59 AM, KAM.covad
<a_gmail_noSpam@kenmcginnis.com> wrote:
> What we need is an easy migration to PostgreSQL from VFP. Unattended installation from CD and a replacement for INSERT INTO FROM NAME, GATHER, etc
>
> Then it would be easier to migrate to something like Python if necessary some day.
>
If only it were that easy :)
I worked on the migration of a large commercial web site, in
hand-coded VFP, from direct DBF manipulation to calling client-server
code. It required examining and recoding not just all the standard SQL
INSERT
--
Ted Roche
Ted Roche & Associates, LLC
Author: Ted Roche
Posted: 2009-04-30 07:55:03 Link
On Thu, Apr 30, 2009 at 7:51 AM, Ted Roche <tedroche@gmail.com> wrote:
aCK! Stupid send key...
>
> If only it were that easy :)
>
> I worked on the migration of a large commercial web site, in
> hand-coded VFP, from direct DBF manipulation to calling client-server
> code. It required examining and recoding not just all the standard SQL
> INSERT...
UPDATE and DELETE, but also REPLACE, APPEND, SCAN, LOCATE/CONTINUE,
SEEK, etc., etc.
Most of the available frameworks have the ability to switch their use
of views or CursorAdaptors from local to remote, but there's still a
lot of fine-tuning to be done.
And then there are the issues of cleaning up the data: handling empty
fields that need to be NULL in the target, converting dates to
datetimes (and back), and so forth.
It's non-trivial. Usually not very exciting work, but resource
intensive. Think of it as a full-employment plan.
--
Ted Roche
Ted Roche & Associates, LLC
Author: Gilbert M. Hale
Posted: 2009-04-30 07:55:39 Link
> It required examining and recoding not just all the standard SQL
> INSERT
"All you have to do is..." The 6 most dangerous words in our industry!
Gil
> -----Original Message-----
> From: profoxtech-bounces@leafe.com [mailto:profoxtech-
> bounces@leafe.com] On Behalf Of Ted Roche
> Sent: Thursday, April 30, 2009 7:51 AM
> To: profoxtech@leafe.com
> Subject: Re: [NF] MySQL > PostgreSQL was Joke (yes, it's computer-
> related!
>
> On Thu, Apr 30, 2009 at 3:59 AM, KAM.covad
> <a_gmail_noSpam@kenmcginnis.com> wrote:
> > What we need is an easy migration to PostgreSQL from VFP. Unattended
> installation from CD and a replacement for INSERT INTO FROM NAME,
> GATHER, etc
> >
> > Then it would be easier to migrate to something like Python if
> necessary some day.
> >
>
> If only it were that easy :)
>
> I worked on the migration of a large commercial web site, in
> hand-coded VFP, from direct DBF manipulation to calling client-server
> code. It required examining and recoding not just all the standard SQL
> INSERT
>
> --
> Ted Roche
> Ted Roche & Associates, LLC
>
[excessive quoting removed by server]
Author: Grigore Dolghin
Posted: 2009-04-30 08:09:13 Link
I am sorry, but I highly doubt MySQL will go away in near future.
On Thu, Apr 30, 2009 at 10:59 AM, KAM.covad
<a_gmail_noSpam@kenmcginnis.com> wrote:
> What we need is an easy migration to PostgreSQL from VFP. Unattended inst=
allation from CD and a replacement for INSERT INTO FROM NAME, GATHER, etc
>
> Then it would be easier to migrate to something like Python if necessary =
some day.
>
> *********************************
> Below is Joshua Drake's take on Oracle purchasing Sun:
> I see a large possibility of mass migration from MySQL by non web applica=
tions.
>
> The obvious choice is PostgreSQL because of =A0the BSD license and the ma=
turity of the software.
>
> In conclusion I expect that MySQL in two years likely won't exist except
> on the most tertiary level. Most new projects will be developed in
> either PostgreSQL, Firebird or one of the forks (MariaDB, Drizzle).
>
> http://planet.postgresql.org/
>
>
> --- StripMime Report -- processed MIME parts ---
> multipart/alternative
> =A0text/plain (text body -- kept)
> =A0text/html
> ---
>
[excessive quoting removed by server]
Author: Gilbert M. Hale
Posted: 2009-04-30 08:17:11 Link
> I am sorry, but I highly doubt MySQL will go away in near future.
>
No need to be "sorry", I hope MySQL has a great run of it. VFP has had =
a
great run of it, and is still kicking in a lot of places. And it is not
open source, and is under "soft assault" from within M$. I think MySQL =
will
prove to be very resilient. But I am still glad I chose PostgreSQL for =
my
large scalable back end (to use with VFP of course). Less grief =
involved.
Gil
> -----Original Message-----
> From: profoxtech-bounces@leafe.com [mailto:profoxtech-
> bounces@leafe.com] On Behalf Of Grigore Dolghin
> Sent: Thursday, April 30, 2009 8:09 AM
> To: profoxtech@leafe.com
> Subject: Re: [NF] MySQL > PostgreSQL was Joke (yes, it's computer-
> related!
>=20
> I am sorry, but I highly doubt MySQL will go away in near future.
>=20
> On Thu, Apr 30, 2009 at 10:59 AM, KAM.covad
> <a_gmail_noSpam@kenmcginnis.com> wrote:
> > What we need is an easy migration to PostgreSQL from VFP. Unattended
> installation from CD and a replacement for INSERT INTO FROM NAME,
> GATHER, etc
> >
> > Then it would be easier to migrate to something like Python if
> necessary some day.
> >
> > *********************************
> > Below is Joshua Drake's take on Oracle purchasing Sun:
> > I see a large possibility of mass migration from MySQL by non web
> applications.
> >
> > The obvious choice is PostgreSQL because of =A0the BSD license and =
the
> maturity of the software.
> >
> > In conclusion I expect that MySQL in two years likely won't exist
> except
> > on the most tertiary level. Most new projects will be developed in
> > either PostgreSQL, Firebird or one of the forks (MariaDB, Drizzle).
> >
> > http://planet.postgresql.org/
> >
> >
> > --- StripMime Report -- processed MIME parts ---
> > multipart/alternative
> > =A0text/plain (text body -- kept)
> > =A0text/html
> > ---
> >
[excessive quoting removed by server]
Author: Leland F. Jackson, CPA
Posted: 2009-04-30 09:29:23 Link
There is no crystals ball for peering into the future, and some weight
must be given to the fact the outlook expressed about MySQL in the
article and links I provided, are coming from the point of view of
members of the PostgreSQL community, which could be a little slanted.
Still, the future of PostgreSQL looks bright to me, but I know Larry
Ellison see PostgreSQL as more of a threat to Oracle, than even MySQL;
because, the PostgreSQL community has been actively working on making
Oracle databases easily convertible to PostgreSQL databases.
You might look in the contrib directory of PostgreSQL to see if there
are any scripts that could be use to help move VFP databases to
PostgreSQL, but as Ted pointed out, you're likely to suffer some major
headache regardless of any scripts found. You will need to unpack the
PostgreSQL source code to get to the contrib directory, (eg script
contributed from various sources to do various things).
Regards,
LelandJ
Grigore Dolghin wrote:
> I am sorry, but I highly doubt MySQL will go away in near future.
>
> On Thu, Apr 30, 2009 at 10:59 AM, KAM.covad
> <a_gmail_noSpam@kenmcginnis.com> wrote:
>> What we need is an easy migration to PostgreSQL from VFP. Unattended installation from CD and a replacement for INSERT INTO FROM NAME, GATHER, etc
>>
>> Then it would be easier to migrate to something like Python if necessary some day.
>>
>> *********************************
>> Below is Joshua Drake's take on Oracle purchasing Sun:
>> I see a large possibility of mass migration from MySQL by non web applications.
>>
>> The obvious choice is PostgreSQL because of the BSD license and the maturity of the software.
>>
>> In conclusion I expect that MySQL in two years likely won't exist except
>> on the most tertiary level. Most new projects will be developed in
>> either PostgreSQL, Firebird or one of the forks (MariaDB, Drizzle).
>>
>> http://planet.postgresql.org/
>>
>>
>> --- StripMime Report -- processed MIME parts ---
>> multipart/alternative
>> text/plain (text body -- kept)
>> text/html
>> ---
>>
[excessive quoting removed by server]
Author: Leland F. Jackson, CPA
Posted: 2009-04-30 10:39:04 Link
PostgreSQL really couldn't be consider too great a threat to Oracle.
Oracle is in a whole other league than PostgreSQL. Oracle is
principally owned by Larry Ellision, but even I have a tiny ownership
interest in Oracle, as Oracle is a publically traded Company traded over
NASDAQ (eg symbol: ORCL).
Regards,
LelandJ
Leland F. Jackson, CPA wrote:
> There is no crystals ball for peering into the future, and some weight
> must be given to the fact the outlook expressed about MySQL in the
> article and links I provided, are coming from the point of view of
> members of the PostgreSQL community, which could be a little slanted.
>
> Still, the future of PostgreSQL looks bright to me, but I know Larry
> Ellison see PostgreSQL as more of a threat to Oracle, than even MySQL;
> because, the PostgreSQL community has been actively working on making
> Oracle databases easily convertible to PostgreSQL databases.
>
> You might look in the contrib directory of PostgreSQL to see if there
> are any scripts that could be use to help move VFP databases to
> PostgreSQL, but as Ted pointed out, you're likely to suffer some major
> headache regardless of any scripts found. You will need to unpack the
> PostgreSQL source code to get to the contrib directory, (eg script
> contributed from various sources to do various things).
>
> Regards,
>
> LelandJ
>
> Grigore Dolghin wrote:
>> I am sorry, but I highly doubt MySQL will go away in near future.
>>
>> On Thu, Apr 30, 2009 at 10:59 AM, KAM.covad
>> <a_gmail_noSpam@kenmcginnis.com> wrote:
>>> What we need is an easy migration to PostgreSQL from VFP. Unattended installation from CD and a replacement for INSERT INTO FROM NAME, GATHER, etc
>>>
>>> Then it would be easier to migrate to something like Python if necessary some day.
>>>
>>> *********************************
>>> Below is Joshua Drake's take on Oracle purchasing Sun:
>>> I see a large possibility of mass migration from MySQL by non web applications.
>>>
>>> The obvious choice is PostgreSQL because of the BSD license and the maturity of the software.
>>>
>>> In conclusion I expect that MySQL in two years likely won't exist except
>>> on the most tertiary level. Most new projects will be developed in
>>> either PostgreSQL, Firebird or one of the forks (MariaDB, Drizzle).
>>>
>>> http://planet.postgresql.org/
>>>
>>>
>>> --- StripMime Report -- processed MIME parts ---
>>> multipart/alternative
>>> text/plain (text body -- kept)
>>> text/html
>>> ---
>>>
[excessive quoting removed by server]
Author: MB Software Solutions General Account
Posted: 2009-04-30 12:12:26 Link
KAM.covad wrote:
> What we need is an easy migration to PostgreSQL from VFP. Unattended
installation from CD and a replacement for INSERT INTO FROM NAME,
GATHER, etc
>
> Then it would be easier to migrate to something like Python if necessary
some day.
That's one of the reasons I switched to using MySQL as a backend for my
VFP apps about 4-5 years ago...I knew the new tools (especially open
source) would work with it. My idea was to have a rewrite done in Dabo,
Python, whatever, that would use the same backend database as my VFP app
was using so that the client-server app could then be changed over to a
web app much easier than just cold-turkey, using a cut-over approach
piece by piece instead of just all at once. Also wanted mobile phone
apps to be able to access same database (on web) with this approach.
Everyone coming to the same watering hole for this app. That's my goal.
--
Mike Babcock, MCP
MB Software Solutions, LLC
President, Chief Software Architect
Author: MB Software Solutions General Account
Posted: 2009-04-30 12:23:20 Link
Grigore Dolghin wrote:
> I am sorry, but I highly doubt MySQL will go away in near future.
It won't. Even if it does, your existing stuff will still continue to
work just fine. They can't kaibosh (sp?) the previously existing stuff.
--
Mike Babcock, MCP
MB Software Solutions, LLC
President, Chief Software Architect