[FX.php List] Performance hit for unpopulated fields on layouts?

[Dale Bengston]

Hi Jonathan,

Even un-populated fields add overhead to the data being pulled from a  
layout. How many fields total? Are we talking 100 or 10, half of  
which would be empty?

MySQL does not have the same "problem," because the data pulled from  
MySQL is not tied to a physical layout like it is with FileMaker.

Dale

On Aug 24, 2007, at 9:43 PM, Jonathan Schwartz wrote:

> Hi Folks,
>
> I'm working on a project where I will allow clients to build their  
> own fx.php powered web pages by having them selecting from a list  
> of available fmp fields in a database.  In order to provide  
> flexibility, there might be twice as many fields on a layout than  
> the user might select.  The system will then build the fx.php page  
> from the selected fields. The unused fields would remain on the  
> layout.
>
> The question I have is regarding the performance hit.  If the  
> unused fields remain on the layout, but stay unpopulated (no data),  
> would the performance suffer?
>
> Just out of curiosity, would this same scenario cause a problem in  
> MySQL?
>
> Thanks,
>
> Jonathan
>
>
>
>
> -- 
> Jonathan Schwartz
> Exit 445 Group
> jonathan at exit445.com
> http://www.exit445.com
> 415-381-1852
> _______________________________________________
> FX.php_List mailing list
> FX.php_List at mail.iviking.org
> http://www.iviking.org/mailman/listinfo/fx.php_list