Hey Freddy,
Do you mean this as a more generic way of using model-data/object in product-specific solutions?
Psuedo code:
select dbo.tsf_get_icon_data('customer.svg')
select dbo.tsf_get_transl_plural('customer_address')
-- or in procedure style
exec tsf_get_icon_data 'customer.svg'
exec tsf_get_transl_plural'customer_address'
Not sure if this is technically feasible but I can understand the benefit of this. Maybe another way would be to have a more easy way of creating a function table or view that supplies this model data in your product database rather than having to manually create it.
Mark Jongeling wrote:
Hey Freddy,
Do you mean this as a more generic way of using model-data/object in product-specific solutions?
Psuedo code:
select dbo.tsf_get_icon_data('customer.svg')
select dbo.tsf_get_transl_plural('customer_address')
-- or in procedure style
exec tsf_get_icon_data 'customer.svg'
exec tsf_get_transl_plural'customer_address'
Not sure if this is technically feasible but I can understand the benefit of this. Maybe another way would be to have a more easy way of creating a function table or view that supplies this model data in your product database rather than having to manually create it.
I would prefer a function style approach, and probably a TVF or view because of performance reasons.