Persist arrays properly about barricane-db

[chrisdew]

Hi, I'm busy with http://www.barricane.com/2011/03/05/uk-internet-startup-week.html for the next couple of weeks.

I'll investigate and fix in two weeks' time.

Thanks for the bug report,

Chris.

[joshmarinacci]

no prob. So far I'm enjoying the library. It's made my life a lot easier. The biggest help would probably be a more full featured sample.

-ju
On Apr 21, 2011, at 1:12 AM, chrisdew wrote:

Hi, I'm busy with http://www.barricane.com/2011/03/05/uk-internet-startup-week.html for the next couple of weeks.

I'll investigate and fix in two weeks' time.

Thanks for the bug report,

Chris.

Reply to this email directly or view it on GitHub:
#2 (comment)

Blasting forth in three part harmony!

[chrisdew]

The cause of the problem is that BarricaneDB is based on defineSetter (which intercepts object alterations).

This does not work the same on Arrays. A partial fix would involve overriding the prototype's push, pop, shift, etc. and asking the application programmer to use a.set(1, 'a') instead of a[1] = 'a'. This is not very palatable. Let me know if you can think of a solution.

This problem is likely to exist on other mutable, non-object, 'native' types. e.g. 'Date' may have a similar issue.

[chrisdew]

http://stackoverflow.com/questions/2449182/getter-setter-on-javascript-array/2449735#2449735

[chrisdew]

Hi, I've had a further look into this, and there is a possible hack, but nothing nice.

Hack: create an explicit 'save' method on each object, which must be called after an array is modified.

I'm happy to do this. Will it solve your problem?

All the best,

Chris.

[chrisdew]

Hi Josh,

Could you reply to the question above, please, if you would like me to resolve this issue?

Thanks,

Chris.

[joshmarinacci]

I understand arrays better now. I think there isn't a good solution so you can just close out the bug. thanks for trying!
On May 19, 2011, at 6:53 AM, chrisdew wrote:

Hi Josh,

Could you reply to the question above, please, if you would like me to resolve this issue?

Thanks,

Chris.

Reply to this email directly or view it on GitHub:
#2 (comment)

Blasting forth in three part harmony!

[chrisdew]

Closed as 'no good solution found'.