Hi Chi,
It's possible that you may get your request by way of Marc Tamlyn's
Kickstarter project - I can't confirm that bitmap fields are specifically
on todo list, but there PostgreSQL has some native representation for bit
types, so it's possible it might be on his radar.
If it turns out BitFiel
Having worked with both, I'd like to put in a vote for Jasmine over QUnit.
Unit test is a Java construct which can feel out of place in Python, never
mind JS. I find QUnit clunky and difficult to write, whereas jasmine (as a
behavioural tool) is pleasant to write and likely comes closer to the kind
> On 04/16/2014 07:20 PM, Russell Keith-Magee wrote:
>
> 2) Is there anything that can save us from the Node.js kudzu? :-)
Yes. Removing JavaScript from Django. :-)
JSHint requires Node.js and running automated JavaScript tests
typically requires Node.js and PhantomJS.
Node.js is pretty easy to
Hi,
Is it possible to add a bitmask field to allow multiple choices for small
set of options in lieu of ManyToManyField?
For some cases, ManyToManyField is overkill. e.g. Select several days of
week to indicate open days for stores while 7 boolean fields are too
frustrated.
Benefits to these
The first solution is definitly the worst, if you make integration tests
you already have a "long running" test suite (especially with over 20-30
models).
initial_data fixtures having a problem, if you change your database the
initial_data will change over time, which is somehow bad to integrate
Ah yes, flushing, I forgot we did that for lesser DBs.
I can think of several solutions:
- Run the entire migration set every time you flush the database. This is,
obviously, not practicable.
- Re-introduce initial_data fixtures; I'd rather not, as these require
constant upkeep and interact badl
The case is really simple and i think its definitely that would block the
release.
First off, I have a model:
from django.db import models
# Create your models here.
class SimpleModel(models.Model):
name = models.CharField(max_length=10)
Then I will make some migrations:
# encoding: utf8
f
The problem might be that initial data is loaded after each database
flush, but the same isn't true for migrations. If we want to have RunSQL
as a complete replacement for initial data, then we need to have some
way to mark data loading "migrations" to be loaded after each database
flush. Of co
