fP's MySQL capabilities?

[Bill Campbell]

On Wed, Jul 25, 2012, Paul McNary wrote:
>Bill Campbell wrote:
>> On Tue, Jul 24, 2012, Paul McNary wrote:
>> ...
>> 
>>> I have been evaluating it for several months. It is what I needed and
>>> wanted.
>> 
>>> You have a mySQL table and want to use it in the same way you use a native
>>> filePro table from within filePro. Define screens, reports, processing, and
>>> all works fine. Updating, adding new records, deleting all works as I
>>> expected it to. I have not tried playing with filePro auto indexes. There
>>> are some limitations documented. One time manual indexes, doesn't appear to
>>> have any limitations in the filePro context.
>> 
>>> You do have the ODBC limits of 254 columns(fields) and inability to
>>> directly using Text/Image (Blob) fields. 999 character field length limit.
>>> I can deal with these in other ways if I need them.
>> 
>> If that's the case, could this be used with Postgres?
>
>I had wished for PostgreSQL to start with, too.
>
>It doesn't work at this time but should be doable in the future
>from what I see.

I'm not an ODBC Maven, but I would think that it wouldn't be all
that difficult.  After all, Postgresql is far more standards
compliant than MySQL (and not tainted by Oracle's ownership).

Bill
-- 
INTERNET:   bill at celestial.com  Bill Campbell; Celestial Software LLC
URL: http://www.celestial.com/  PO Box 820; 6641 E. Mercer Way
Voice:          (206) 236-1676  Mercer Island, WA 98040-0820
Fax:            (206) 232-9186  Skype: jwccsllc (206) 855-5792

Calling theft "Wealth Redistribution" can never make it right.
	http://www.lewrockwell.com/huff/huff25.html