I side with David when it comes to databases. They suck! Just my own
opinion.
So what about the people who don’t want to define validations and stuff
in the database, but still want to be DRY.
I really hate how the schema is separate from my models. I kind of like
how Django defines the table attributes in the model. I was think about
trying something like that in Rails.
You could define the attributes in the model and run a special generator
that creates a migration from the schema.
Any ideas? I’m just brian storming right now.
I really hate how the schema is separate from my models. I kind of like
how Django defines the table attributes in the model. I was think about
trying something like that in Rails.
You could define the attributes in the model and run a special generator
that creates a migration from the schema.
It’d be interesting to talk with some Django developers - from both
small and large projects - to see what works well for them.
Does anyone know some Django users we can interrogate?
Cheers
Nic
Josh P. wrote:
I side with David when it comes to databases. They suck! Just my own
opinion.
Huh?!? Much better than using text files…
Joe
Joe R. wrote:
Josh P. wrote:
I side with David when it comes to databases. They suck! Just my own
opinion.
Huh?!? Much better than using text files…
And they scale a lot better than large XML files 
Paper tape could be an option…
that’d be great against unemployment! pay people for writing your data
to
paper, search records etc… the human database… sounds like magic to
me
2006/8/8, Dr Nic [email protected]:
Paper tape could be an option…
–
Posted via http://www.ruby-forum.com/.
Rails mailing list
[email protected]
http://lists.rubyonrails.org/mailman/listinfo/rails
–
Michael S. [email protected]
www.stellar-legends.de - Weltraum-Browsergame im Alpha-Stadium