Storing realm objects using Kotlin extensions











up vote
2
down vote

favorite












I am a Java Android Developer and I'm approaching Kotlin.



I have defined the following class:



open class Player : RealmObject() {
...
}


And I defined the following two extensions, one for the generic RealmObject class and one for the specific Player class:



fun RealmObject.store() {
Realm.getDefaultInstance().use { realm ->
realm.beginTransaction()
realm.copyToRealmOrUpdate(this)
realm.commitTransaction()
}
}

fun Player.store(){
this.loggedAt = Date()
(this as RealmObject).store()
}


What I want is if I call .store() on any RealmObject object, the RelamObject.store() extension will be called BUT if i call .store() on a Player instance the extension that will be called will be Player.store().
(No problem for now)
I don't want to copy paste the same code, i love to write less reuse more.
So i need that internally the Player.store() will call the generic RealmObject.store()



I got it. The code I wrote up there is actually working as expected :D



Is this the good way? Or there is some better way?










share|improve this question
















bumped to the homepage by Community 8 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.



















    up vote
    2
    down vote

    favorite












    I am a Java Android Developer and I'm approaching Kotlin.



    I have defined the following class:



    open class Player : RealmObject() {
    ...
    }


    And I defined the following two extensions, one for the generic RealmObject class and one for the specific Player class:



    fun RealmObject.store() {
    Realm.getDefaultInstance().use { realm ->
    realm.beginTransaction()
    realm.copyToRealmOrUpdate(this)
    realm.commitTransaction()
    }
    }

    fun Player.store(){
    this.loggedAt = Date()
    (this as RealmObject).store()
    }


    What I want is if I call .store() on any RealmObject object, the RelamObject.store() extension will be called BUT if i call .store() on a Player instance the extension that will be called will be Player.store().
    (No problem for now)
    I don't want to copy paste the same code, i love to write less reuse more.
    So i need that internally the Player.store() will call the generic RealmObject.store()



    I got it. The code I wrote up there is actually working as expected :D



    Is this the good way? Or there is some better way?










    share|improve this question
















    bumped to the homepage by Community 8 mins ago


    This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.

















      up vote
      2
      down vote

      favorite









      up vote
      2
      down vote

      favorite











      I am a Java Android Developer and I'm approaching Kotlin.



      I have defined the following class:



      open class Player : RealmObject() {
      ...
      }


      And I defined the following two extensions, one for the generic RealmObject class and one for the specific Player class:



      fun RealmObject.store() {
      Realm.getDefaultInstance().use { realm ->
      realm.beginTransaction()
      realm.copyToRealmOrUpdate(this)
      realm.commitTransaction()
      }
      }

      fun Player.store(){
      this.loggedAt = Date()
      (this as RealmObject).store()
      }


      What I want is if I call .store() on any RealmObject object, the RelamObject.store() extension will be called BUT if i call .store() on a Player instance the extension that will be called will be Player.store().
      (No problem for now)
      I don't want to copy paste the same code, i love to write less reuse more.
      So i need that internally the Player.store() will call the generic RealmObject.store()



      I got it. The code I wrote up there is actually working as expected :D



      Is this the good way? Or there is some better way?










      share|improve this question















      I am a Java Android Developer and I'm approaching Kotlin.



      I have defined the following class:



      open class Player : RealmObject() {
      ...
      }


      And I defined the following two extensions, one for the generic RealmObject class and one for the specific Player class:



      fun RealmObject.store() {
      Realm.getDefaultInstance().use { realm ->
      realm.beginTransaction()
      realm.copyToRealmOrUpdate(this)
      realm.commitTransaction()
      }
      }

      fun Player.store(){
      this.loggedAt = Date()
      (this as RealmObject).store()
      }


      What I want is if I call .store() on any RealmObject object, the RelamObject.store() extension will be called BUT if i call .store() on a Player instance the extension that will be called will be Player.store().
      (No problem for now)
      I don't want to copy paste the same code, i love to write less reuse more.
      So i need that internally the Player.store() will call the generic RealmObject.store()



      I got it. The code I wrote up there is actually working as expected :D



      Is this the good way? Or there is some better way?







      object-oriented android extension-methods kotlin






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Aug 3 '17 at 16:31









      200_success

      127k15148412




      127k15148412










      asked Aug 3 '17 at 16:18









      Gianni Genovesi

      111




      111





      bumped to the homepage by Community 8 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







      bumped to the homepage by Community 8 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
























          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote













          It's not a direct answer to your technical question, which you seem to have answered.



          I'm not sure that the Player.loggedAt field should be set when store() is called. We only see a very small fraction of your app, but maybe that could be set somewhere else more naturally. From the name, it seems maybe it should be set when the Player is created, or recreated from the DB.






          share|improve this answer





















            Your Answer





            StackExchange.ifUsing("editor", function () {
            return StackExchange.using("mathjaxEditing", function () {
            StackExchange.MarkdownEditor.creationCallbacks.add(function (editor, postfix) {
            StackExchange.mathjaxEditing.prepareWmdForMathJax(editor, postfix, [["\$", "\$"]]);
            });
            });
            }, "mathjax-editing");

            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "196"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fcodereview.stackexchange.com%2fquestions%2f172004%2fstoring-realm-objects-using-kotlin-extensions%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            0
            down vote













            It's not a direct answer to your technical question, which you seem to have answered.



            I'm not sure that the Player.loggedAt field should be set when store() is called. We only see a very small fraction of your app, but maybe that could be set somewhere else more naturally. From the name, it seems maybe it should be set when the Player is created, or recreated from the DB.






            share|improve this answer

























              up vote
              0
              down vote













              It's not a direct answer to your technical question, which you seem to have answered.



              I'm not sure that the Player.loggedAt field should be set when store() is called. We only see a very small fraction of your app, but maybe that could be set somewhere else more naturally. From the name, it seems maybe it should be set when the Player is created, or recreated from the DB.






              share|improve this answer























                up vote
                0
                down vote










                up vote
                0
                down vote









                It's not a direct answer to your technical question, which you seem to have answered.



                I'm not sure that the Player.loggedAt field should be set when store() is called. We only see a very small fraction of your app, but maybe that could be set somewhere else more naturally. From the name, it seems maybe it should be set when the Player is created, or recreated from the DB.






                share|improve this answer












                It's not a direct answer to your technical question, which you seem to have answered.



                I'm not sure that the Player.loggedAt field should be set when store() is called. We only see a very small fraction of your app, but maybe that could be set somewhere else more naturally. From the name, it seems maybe it should be set when the Player is created, or recreated from the DB.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Aug 8 '17 at 19:27









                toto2

                5,1771019




                5,1771019






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Code Review Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    Use MathJax to format equations. MathJax reference.


                    To learn more, see our tips on writing great answers.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fcodereview.stackexchange.com%2fquestions%2f172004%2fstoring-realm-objects-using-kotlin-extensions%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    404 Error Contact Form 7 ajax form submitting

                    How to know if a Active Directory user can login interactively

                    Refactoring coordinates for Minecraft Pi buildings written in Python