Stored procedures in ORM parameters moving around

4 posts, 0 answers
  1. Trevor
    Trevor avatar
    5 posts
    Member since:
    Jul 2011

    Posted 21 Jun 2012 Link to this post

    Hi,

    We're slowly but surely switching over our existing stored procedures to use ORM and LINQ but something that has become a rather bit of a pain is that if we make changes to a stored procedure and delete and re-add it the stored procedures parameters sorting changes. For example:

    StoredProcedure(int x, int y, int z) becomes after re-adding StoredProcedure(int y, int z, int x)

    It also seems to ignore the stored procedures scripts parameter order.

    Updating seems to be maintaining the correct order though.

    It's causing quite a pain with rewriting and rechecking parameters.
  2. Greg
    Greg avatar
    44 posts
    Member since:
    Jun 2012

    Posted 22 Jun 2012 Link to this post

    For me it seems the parameters are always in reverse alphabetical order (by parameter name), but the fact stands that they're not in db order. This is actually a serious problem, not just a usability issue. See http://www.telerik.com/community/forums/orm/databases/parameter-order-is-incorrect-when-calling-oracle-stored-procedures.aspx
  3. DevCraft banner
  4. PetarP
    Admin
    PetarP avatar
    754 posts

    Posted 25 Jun 2012 Link to this post

    Hi Greg and Trevor,

     Indeed we have recently found a problem with the internal diff merge algorithm that is visible during update from database.  
    A possible workaround should be to delete the procedure in question and reimport it from the database rather than update the existing one.
    Please do let me know if that works for you. Note that this is a temporary workaround until a fix for this is provided.

    Kind regards,
    Petar
    the Telerik team
    OpenAccess ORM Q2'12 Now Available! Get your hands on all the new stuff.
  5. PetarP
    Admin
    PetarP avatar
    754 posts

    Posted 26 Jun 2012 Link to this post

    Hi Greg and Trevor,

     I am writing this to let you know that this is fixed now and the fix will be available in the upcoming service pack.
    We are sorry for any inconvenience this might have caused.

    Regards,
    Petar
    the Telerik team
    OpenAccess ORM Q2'12 Now Available! Get your hands on all the new stuff.
Back to Top