>> It's really not tedious at all. All permissions are assigned
>> to roles. Which there are only a few per application. So
>> thats really all you have to manage aside from assigning
>> roles to the users.
>
> What if you switch from Oracle to SQL Server, aren't you now in for some
> reworking of your application?
Yes, but you have to rework your data access layer anyway if you
are using stored procedures or advanced SQL.
> Seems like if you minimized the dependency of
> platform to the application, portability would be easier and more flexible;
> unless you were positive that the platform was not going to change or you
> were open to altering the app...
But minimizing isn't the same as doing away with it. Don't get me
wrong, I am all for writing SQL as portable as possible and
harassing vendors to implement the standard, but not at all cost.
Writing portable SQL to me means not using || as an OR operator,
not using double quotes as a string delimiter and not omitting a
FROM line.
It doesn't mean not using functionality where it makes sense.
Jochem
--
I don't get it
immigrants don't work
and steal our jobs
- Loesje
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
