[FX.php List] FM Scripts vs. PHP

[Gjermund Gusland Thorsen]

Try with 200 childrecords, 2 records will not have any effect either way...

ggt667

On 10/25/07, Joel Shapiro <jsfmp at earthlink.net> wrote:
> hmm...
> I'm just developing something now where I edit two fields -- each one
> is in a different child record -- via a layout on the one parent
> record so I only hit the DB once.  I haven't tested for speed but it
> seemed like it would be quicker than hitting for each child record.
>
> maybe I should do some speed tests if I really want to know... (ugh)
> or maybe I'm putting too much weight into perfect optimization when
> the difference is minimal ;-)
>
> -Joel
>
>
> On Oct 25, 2007, at 10:54 AM, Gjermund Gusland Thorsen wrote:
>
> > When receiveing data from FileMaker I use relationships, when I write
> > to FileMaker I use mulitple queries.
> >
> > ggt667
> >
> > On 10/25/07, Joel Shapiro <jsfmp at earthlink.net> wrote:
> >> Thanks d,d,&ggt
> >>
> >> Dale: Out of curiosity -- & because I don't know MySQL yet -- if you
> >> don't use related fields are you hitting the database additional
> >> times (e.g. once for parent, once for related children)?  I'd thought
> >> the conventional wisdom here was that it's faster to get everything
> >> in one hit off one layout -- at least w/ FMP.
> >>
> >> -Joel
> >>
> >>
> >> On Oct 25, 2007, at 12:27 AM, Gjermund Gusland Thorsen wrote:
> >>
> >>> The answer lays in maintenance, if the php task and the ScriptMaker
> >>> task can bring maintenance issues, make both in FileMaker if
> >>> possible.
> >>>
> >>> If not make one script for each medium.
> >>>
> >>> ggt667
> >>>
> >>> On 10/25/07, Dale Bengston <dbengston at preservationstudio.com> wrote:
> >>>> Derrick is dead on: it depends. There are certainly cases with our
> >>>> existing clients where we are tapping into a process that invoke
> >>>> complex scripts that are part of a client-server installation. In
> >>>> such cases, it doesn't make sense to replicate the process in PHP.
> >>>>
> >>>> On the other hand, we are doing all new development so that it
> >>>> can be
> >>>> switched between FMP and MySQL. This means no related fields on
> >>>> layouts and no native FMP scripts. It's amazing how much faster
> >>>> data
> >>>> retrieval is without any related fields on a layout.
> >>>>
> >>>> So for us, it's a matter of how tied to FMP we want to be. Since we
> >>>> choose to support more than one data source, we do as much as
> >>>> possible in PHP. But in certain cases for existing FMP clients,
> >>>> it's
> >>>> easier (and cheaper) to tap into the existing scripting.
> >>>>
> >>>> Dale
> >>>>
> >>>> PS I concur with everyone who's commented about the pre v7 use
> >>>> of FMP
> >>>> scripting from the web: it is ugly. On the other hand, I used to
> >>>> do a
> >>>> lot of stuff with AppleScript and v6 from the web. Ah, those
> >>>> were the
> >>>> days.
> >>>>
> >>>>
> >>>> On Oct 24, 2007, at 9:04 PM, Derrick Fogle wrote:
> >>>>
> >>>>> On Oct 24, 2007, at 7:34 PM, Joel Shapiro wrote:
> >>>>>> Anybody else care to pipe in?
> >>>>>
> >>>>> As always, it depends what you're doing. If your operations are
> >>>>> mostly native FM with only a small web-based presence, sticking
> >>>>> with FM is probably the best choice. But I can't recommend
> >>>>> using FM
> >>>>> scripting, or even FM at all, if you're good with PHP and your
> >>>>> operations are primarily web-based.
> >>>>>
> >>>>> FWIW, I use FM8SA one one machine, and Apache/PHP on a nearly
> >>>>> identical 2nd machine (both XServes). Processing data in PHP is so
> >>>>> much faster than processing data in FM, it's not even funny. I'm
> >>>>> competent enough with both FM and PHP, and I invariably fetch the
> >>>>> minimum raw data required out of FM with as few actual
> >>>>> interactions
> >>>>> with FM as possible, and do any processing needed for output to a
> >>>>> browser with PHP.
> >>>>>
> >>>>> I can see where, if you want to update a whole bunch of FM records
> >>>>> with a single web submit, you will find a point where
> >>>>> processing in
> >>>>> FM will be faster than processing in PHP, simply because of the
> >>>>> time overhead of getting data in and out of FM. But I would
> >>>>> question any web application that modified a whole bunch of
> >>>>> records
> >>>>> with a single web submit.
> >>>>>
> >>>>> Derrick Fogle
> >>>>> derrick at fogles.net
> >>>>> _______________________________________________
> >>>>> FX.php_List mailing list
> >>>>> FX.php_List at mail.iviking.org
> >>>>> http://www.iviking.org/mailman/listinfo/fx.php_list
> >>>>
> >>>> _______________________________________________
> >>>> FX.php_List mailing list
> >>>> FX.php_List at mail.iviking.org
> >>>> http://www.iviking.org/mailman/listinfo/fx.php_list
> >>>>
> >>> _______________________________________________
> >>> FX.php_List mailing list
> >>> FX.php_List at mail.iviking.org
> >>> http://www.iviking.org/mailman/listinfo/fx.php_list
> >>
> >> _______________________________________________
> >> FX.php_List mailing list
> >> FX.php_List at mail.iviking.org
> >> http://www.iviking.org/mailman/listinfo/fx.php_list
> >>
> > _______________________________________________
> > FX.php_List mailing list
> > FX.php_List at mail.iviking.org
> > http://www.iviking.org/mailman/listinfo/fx.php_list
>
> _______________________________________________
> FX.php_List mailing list
> FX.php_List at mail.iviking.org
> http://www.iviking.org/mailman/listinfo/fx.php_list
>