Thanks yall! @Baz: I work for a University, we have to store more about student than they probably know about themselves. lol
On May 14, 3:34 pm, garrettjohnson <[email protected]> wrote: > I am sure this has been asked before, but I could not pin point a > thread that already talked about. If there is one, feel free to just > point me on my way! > > 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. > > For simplicities sake... an example might be: you need to design a > Gateway for a User table. But the user table has 30 columns for some > reason or another, and one of those columns is something secure that > we are not allowed to select out of the table on a regular basis (no > getting around that). > > So, when I write my method, getUser()... I might need 4 or 5 of those > attributes that is returned, rarely do I need the secure ones, once > and a while I need all of them. > > What is really the best, most efficient way to handle these types of > situations? ( re-doing the table is not an option... :-) ) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
