The ideal option (in my opinion) would be to create a view of only the
subset of columns you are more likely to use; however if that is not an
option you could also create 2 or more gateway objects that refer to the
same table, kinda mimicking the concept of a view, but at code level.
Gateway A will deal only with the subset of columns on your most frequent
use cases, Gateway B could deal with the secure columns (or whatever
combination) and then a gateway C to deal with the entire table (if you
actually need to get everything).
Oscar



On Thu, May 14, 2009 at 1:26 PM, Baz <[email protected]> wrote:

> I had a similar situation but not with secure columns (I'd love to actually
> know what that means?) but where a column was a huge, slow blob of text that
> I didn't need 99% of the time and would add lots of load if it were there.
> You can have an optional argument to include those columns or not:
> <cfargument name="IncludeSecureColumns" default="false" /> and then just
> CFIF inside the SELECT statement.
>
> Baz
>
>
>
> On Thu, May 14, 2009 at 12:46 PM, Steve Bryant <
> [email protected]> wrote:
>
>>
>> You might look into creating a View of the table. Most databases
>> support this and it would allow you to create a view of the table
>> that doesn't have the secure columns. Then you could just code
>> against that view instead of against the table directly.
>>
>> Steve
>>
>> At 02:34 PM 5/14/2009, garrettjohnson wrote:
>> >I am wondering how others deal with when it comes to designing a
>> >Gateway, but the table it models has A LOT of columns and maybe some
>> >secure columns.
>>
>>
>>
>>
>
> >
>


-- 
Oscar Arevalo
http://www.oscararevalo.com

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"CFCDev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/cfcdev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to