That's not right at all. If you have a complex app with a complex model that actually does stuff to your raw data, rather than just spit it out - you will want to go through transfer to have all that logic, rather than duplicate it in another place. If, on the other hand, you are building a report, that has very little to do with your model, requires complex SQL and aggregates, has tons of rows and then just spits em out - then you certainly don't want to use transfer. Where it gets touchy is if you have a complex query but still need the logic from your model, then it is your judgement call whether its more beneficial to pigeon hole it into TQL (and therefore not duplicate your model logic) or go straight sql and duplicate your model logic.
Baz On Wed, Jun 24, 2009 at 8:56 PM, jarthel <[email protected]> wrote: > > I work for a university (so we get special pricing on Oracle) and I > highly highly doubt we would be moving to another DB vendor in the > near/distant feature. > > from what I can see the only benefit to me is on security > (injections). though I have to weigh that up VS the usefulness of > Oracle's built-in features. > > Thanks everyone for the reply. > > > > --~--~---------~--~----~------------~-------~--~----~ Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer You received this message because you are subscribed to the Google Groups "transfer-dev" 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/transfer-dev?hl=en -~----------~----~----~----~------~----~------~--~---
