Save it on sqllite

[Alvarz]

How can I save the multi key dict on sqlite db?

[formiaczek]

It's build using dictionaries and you could use pickle module to dump/load it. Even simpler would be to store it as a string, i.e. you could try to use it's __str__ and __init__ that takes a dictionary to restore it. It might although be useful to make multi_key_dict json-serializable (it is not at the moment).

[Alvarz]

It might although be useful to make multi_key_dict json-serializable (it is not at the

That would be awsome for what I need.
If I store it as a string as you said, I would be able to make search directly from the db as I do on the multi_key_dict?

[formiaczek]

Oh, If you mean to migrate content of multi_key_dict and make db work as if it were multi_key_dict? I'm not sure. Mind that multi_key_dict, once populated, should allow you to retrieve items with expected constant (O(1)) time (as a standard dict() which multi_key_dict is build on). Now if you wanted to use the DB to store / restore the multi_key_dict (e.g. as a persistent storage), but later wanted to use multi_key_dict object - it will give you that speed (just remember to back-it-up on exit etc). If, however, you wished to keep the interface of multi_key_dict and have the underlying storage in the DB, that depends on how you implement it: possibly using composite index?. I guess if the later is your goal (and not just a persistent storage of multi_key_dict) implementing it in the DB should work better than re-creating multi_key_dict (O(n)) fetched from DB every time you need to use multi_key_dict (especially if you only then need to search for one (or few) items), although it might still make sense - all depends on your use-case. Could you elaborate more on what exactly you're trying to achieve?

[formiaczek]

(BTW: allowing the storage to be DB seems like a nice feature for a multi-key-dict, really, and it's not there, but that doesn't mean it can't be ;) )

[Alvarz]

OK let tell you what I'm trying to do, I have a multi_key_dict, each entry has 2 or 3 keys and at least 3 values, i.e

dict["meat", "salsa"] = ["hamburguer", "barbecue", "stew"]

if I search for "meat" It will return "hamburguer" or "barbecue" or "stew" randomly and if I search for "salsa" It must do the same, in that way it works smoothly and I love it. But when start to growing up the diccionary, it' will use a lot of memory and my app will have a poor performance, that's why I want to store the dict on sqlite db and then make de search directly from there

By the way excuse my terrible english, I really speak spanish

[formiaczek]

OK, I think I get it now. Indeed it looks like you'd like to use multi_key_dict as an abstraction layer to access data in a database. It sounds like a neat idea, but multi_key_dict does not support this at the moment. It is merely a data structure (like dict, but extended). I'm not an expert in databases, but I'm not sure if, if you need to use database, you don't really need to look into something specific to them (e.g. Object-oriented DB, or maybe just abstract your requirements using SQLAlchemy). Maybe multi_key_dict could do this -it sounds like a nice thing to be added, and I might try to put something together to try the idea but feel free to contribute if you feel like it!

By the way excuse my terrible english, I really speak spanish

No worries, English is not my native, but I can know only very basic Spanish and if I tried to explain the above in Spanish - it would be horrible (if not impossible to do :))

[Alvarz]

Thanks I will dig on a way to do it as you said!

El mié 08/06/2016, 2:17 a.m., Lukasz Forynski notifications@github.com
escribió:

OK, I think I get it now. Indeed it looks like you'd like to use
multi_key_dict as an abstraction layer to access data in a database. It
sounds like a neat idea, but multi_key_dict does not support this at the
moment. It is merely a data structure (like dict, but extended). I'm not an
expert in databases, but I'm not sure if, if you need to use database, you
don't really need to look into something specific to them (e.g.
Object-oriented DB, or maybe just abstract your requirements using
SQLAlchemy). Maybe multi_key_dict could do this -it sounds like a nice
thing to be added, and I might try to put something together to try the
idea but feel free to contribute if you feel like it!

By the way excuse my terrible english, I really speak spanish
No worries, English is not my native, but I can know only very basic
Spanish and if I tried to explain the above in Spanish - it would be
horrible (if not impossible to do :))

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#16 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AHW1NDCRBh4Ylha_IBpHpKq5Sguhtamhks5qJl5bgaJpZM4Iu6J4
.