Fool-proof access to a database for security

  • * All access through stored procedures

    * A single attribute with no other configuration

    * Interface is: Load, Store, Delete, LoadAll, LoadList (LoadList has a parameter for an alternate SP to be called)

    See attached images for example.

  • Is there a question here ?

    Jayanth Kurup[/url]

  • Request for comments, I suppose.

  • The Persistence.DLL and some useful SQL Server SPs/Function are attached.

  • If your looking for comments on the code behind

    try catch block and validations come to min.

    At database side date format and timezone info could be useful.

    You could use some styles for the layout

    and possibly handle the valiadtion using jquery.

    Jayanth Kurup[/url]

  • Jayanth_Kurup (9/9/2015)


    If your looking for comments on the code behind

    try catch block and validations come to min.

    At database side date format and timezone info could be useful.

    You could use some styles for the layout

    and possibly handle the valiadtion using jquery.

    It throws informational errors from the database, so I don't think many try/catches are necessary.

    Date format and timezone info is interesting. I'd have to think about the right place for that specification.

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply