Thanks Arnar! I´ll prefer to take this off the list since it is only
slightly related to SQLAlchemy.
On Jun 26, 2:28 am, "Arnar Birgisson" <[EMAIL PROTECTED]> wrote:
> On 6/25/07, voltron <[EMAIL PROTECTED]> wrote:
>
>
>
> > Thank you very much for your feedback guys! I was very worried the
> > w
> > http://www.evolt.org/article/Four_ways_to_work_with_hierarchical_
> >data/17/4047/index.html
>
> I have to say I've seen better writeups on this topic - so be
> warned :)
that looks very much like '1st 5 things i found about recursive data'.
> Choosing a strategy for storing hierarchical data
On 6/25/07, voltron <[EMAIL PROTECTED]> wrote:
>
> Thank you very much for your feedback guys! I was very worried the
> whole day. I did some research and found this:
> http://www.evolt.org/article/Four_ways_to_work_with_hierarchical_data/17/4047/index.html
I have to say I've seen better writeups
Thank you very much for your feedback guys! I was very worried the
whole day. I did some research and found this:
http://www.evolt.org/article/Four_ways_to_work_with_hierarchical_data/17/4047/index.html
This shows different methods of storing hierarchical data, but I just
did not like the mind b
On Jun 25, 5:54 pm, voltron <[EMAIL PROTECTED]> wrote:
> 1. Convert the JSON object to Python code using simplejson, pickle the
> result and store in a binary field?
> 2. Store the JSON object as a string in a string field?
I'd go with no. 2 unless you need to manipulate the object in Python
code
id make tables to store the expression components and their
relationships distinctly.
then again, im looking for cool things to write blog posts about.
short answer: put it in a text-based field, JSON is essentially text.
--~--~-~--~~~---~--~~
You received this
