[FX.php List] SQL strings transformed to FX.php functions

[Steve Hannah]

I share Greg's sentiments about practicality.  It seems that a  
perfect and complete solution is impossible but it still is possible  
to construct a partial solution that, coupled with some design  
constraints on the database, could be very effective.  A limited  
solution would work with greatest common divisors of the 2 types of  
database.  The problem with joins could be remedied in 2 ways:
1) Disallow joins
2) Predefine supported joins in the database.  Ie: Figure out which  
join operations will be needed when the database is designed, and  
create the appropriate relationships to support the join operations.   
If an unsupported join is attempted, and exception could be thrown.

Steve
On 8-Dec-05, at 10:23 AM, Greg Dykema wrote:

> On Dec 7, 2005, at 11:27 AM, DC wrote:
>
>> ...
>> Build a transformation layer that would translate SQL statements  
>> into a series of FX.php function calls and PHP array manipulations  
>> to spit back the same format array that you would get if you were  
>> talking directly to a SQL engine (probably modeled after MySQL).
>> ...
>> Does anyone have any thoughts on this? The ultimate goal is just  
>> to be able to use any PHP framework on top of FMP without building  
>> new databases in some SQL database. Basically, as a plugin to  
>> FX.php it would make FMP a viable backend for any number of PHP  
>> projects.
>>
>
> Most interesting SQL queries are going to involve joins. The only  
> way to efficiently implement a join in FileMaker is to use  
> relationships, and to support arbitrary queries you'd need a way to  
> define relationships on the fly, as well as build layouts using  
> related fields on the fly. Doesn't sound practical even if it were  
> possible.
>
>
>
> greg
>
> _______________________________________________
> FX.php_List mailing list
> FX.php_List at mail.iviking.org
> http://www.iviking.org/mailman/listinfo/fx.php_list
>
>