Linking Outgoing message in the Database Router with the Database message

[fredcido]

When using Database Router as rapidsms router, at the backend_preparation, link the database message object with the Outgoing message, making possible to retrieve the message saved using the message object.

Now when you use:

from rapidsms import router
...
outgoing_message = router.send('Testing message', connections)
# Now you can get the database messages and transmissions
print outgoing_message.database_message.status
outgoing_message.database_message.transmissions.all()

[coveralls]

Coverage increased (+0.01%) when pulling d243f06 on catalpainternational:feature/database_message into 50292bd on rapidsms:develop.

[coveralls]

Coverage increased (+0.006%) to 89.297% when pulling 6dc3b3b on catalpainternational:feature/database_message into bdb3cf4 on rapidsms:develop.

[coveralls]

Coverage increased (+0.006%) to 89.297% when pulling 6dc3b3b on catalpainternational:feature/database_message into bdb3cf4 on rapidsms:develop.

[raphaelmerx]

@vkurup Any objections to merging this? Let me know. FYI this would let us ditch our RapidSMS fork living at https://github.com/catalpainternational/rapidsms/

[vkurup]

No strong objections, but I'm not very familiar with this section of the code. Would it be possible (and not too difficult) to add a unit test for the new behavior?

[coveralls]

Coverage increased (+0.006%) to 89.297% when pulling 0cd7b15 on catalpainternational:feature/database_message into bdb3cf4 on rapidsms:develop.

[raphaelmerx]

I added test_database_message_sent. It uses the link from rapidsms.messages.outgoing.OutgoingMessage to rapidsms.router.db.models.Message, and checks that the database message has the right properties after being sent.

[vkurup]

Excellent, thank you! 🚀