In reality that happens every once in a while, correct? If not you have another problem.
On Sat, Mar 12, 2016 at 9:33 PM, < [email protected]> wrote: > On 2016-03-11 17:18, Stephen Russell wrote: > >> Field widths shouldn't make any difference, you do you varchar(50) or >> nvarchar(50) or (100) already don't you for the data outside of State? >> >> In all of my code the UI data is defined by the received data from the >> backend. >> > > > I'm not talking about the front end UI. I'm talking about when you guys > make a field 25 characters large (for example) than it is currently. Your > stored procedure parameters have to be updated to reflect the length beyond > the existing setting. That's where Oracle's parameters are better than SQL > Server: you can reference a field name (synonym) rather than hardcoding > any width. > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/CAJidMYKO3ZQKerNcZgGK0Cd8LLamvNNhX64c=24wf49sbhh...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
