keep original key on row

morganrallen commented 10 years ago

Keeping the original key on the row will prevent a possible recreation of the row on change.

juliangruber commented 10 years ago

why would the row be recreated?

morganrallen commented 10 years ago

If you db.put later, using row._key (which has been changed if you used a binary key) it won't be detected as a change event and will create a new row.

On Wed, Nov 27, 2013 at 12:14 PM, Julian Gruber notifications@github.comwrote:

why would the row be recreated?

— Reply to this email directly or view it on GitHubhttps://github.com/juliangruber/level-list/pull/7#issuecomment-29416625 .

http://ithoughtyouweretherobot.com Metal and Wire

http://nolonelyguineapigs.com/ Wandering and Rambling

http://morglog.org Old and Neglected.

-----BEGIN PGP PUBLIC KEY BLOCK----- Version: OpenPGP.js v.1.20121007 Comment: http://openpgpjs.org

xsBNBFG3btUBB/9+/WJNOSIuc/praKPaPOweqXV5s7PGRD+HAnNWF/19YAY3 AFtfeoelhhY4sMJoobTaJzcZojznZ1kl/7UuuYCnbJO3Z9kaSMVrVxEZMSLe YmW8Hc4ZsTnl9f05DQFy8ABpAvMLmXJQXh63BbfzjFqNbSWQfLhrubSM2Elq xmN6EsmRyAuEeYlSnal+Di2MlViohpCbbagE2D6AZTUECIamTib6+DuLG4XO b4GGKHR9TXu2qS1VH6hqcvdEz2MDE5OqZzAnBgcF2dvcOdTk9gAOoR1T+qKj IJtg2X0ETbxcPqEXQoXE8VrxN0MLT5JQKTg26+csU4P2w0rEWsUsJombABEB AAHNJU1vcmdhbiBBbGxlbiA8bW9yZ2FucmFsbGVuQGdtYWlsLmNvbT7CwFwE EAECABAFAlG3btwJEG9pFLKaVEfeAAD7hwf+K8LN/kfgi8GTRLiTcuM+hSbm uAeiBY+VaJIQFLzoFlt8A0hBlLNPFNNmUDxdPrMErdHgZ7HtJW/6RANuBTti 5hr3EBguH1GQyK7BbUqJGvaEX4UNRej3uyX3ufXDsIB/3NsKaTyyu+SO0+Hv Cn2DwmlfSXcPhoarx6Turizn/WwgtTN3tqrMWxxiCKWydLH5xYuz+23BLMdc oF/zkbF+7ddFhmyfiFh4Ej9//tsfwPj2cACU3uLTrcwCo7IxUtkrqMF/fhlm LEqjhzDDjq9v7GNWb/5xB2xgTaucJ7/ljuS8nPlZqwCI8NlTgSqC8nyVLyjS yVtOzkItcS0UqyW1Mg== =V/Ia -----END PGP PUBLIC KEY BLOCK-----

juliangruber commented 10 years ago

aaah gotcha, yeah row._key should stay untouched

juliangruber commented 10 years ago

released as 0.11.1

juliangruber / level-list

keep original key on row #7