On Tue, Sep 2, 2008 at 12:37 AM, Jon Loyens <[EMAIL PROTECTED]> wrote:
>
> Hi guys,
>
> I have a small project coming up that I think having some sort of
> schema evolution facilities will be handy on. I was wondering what
> the current and best project choices for sche
Hi guys,
I have a small project coming up that I think having some sort of
schema evolution facilities will be handy on. I was wondering what
the current and best project choices for schema evolution are? I was
leaning towards django-evolution until I saw a post from Russell
saying that he
Thanks for all the valuable feedback guys, I went ahead and got Django
Evolution up and running and I'll see what I think.
This has been one thing that has really pained me in the switch from
Rails to Django. Though I totally understand, since Rails doesn't
enforce foreign key constraints in the
SmileyChris wrote:
> On Nov 26, 1:03 pm, LorenDavie <[EMAIL PROTECTED]> wrote:
>
>> Not sure if SmileyChris is this guy, but I've had good success with
>> this project:
>>
>> http://www.aswmc.com/dbmigration/
>>
>
> As Mike H said, dbmigration is his project (my DBEvolution project did
> s
On Nov 26, 1:03 pm, LorenDavie <[EMAIL PROTECTED]> wrote:
> Not sure if SmileyChris is this guy, but I've had good success with
> this project:
>
> http://www.aswmc.com/dbmigration/
As Mike H said, dbmigration is his project (my DBEvolution project did
some of the "automatically generated migrati
On 11/27/07, Massimiliano Ravelli <[EMAIL PROTECTED]> wrote:
>
> On 25 Nov, 10:21, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> > What is the recommended method to do this right now, what are you all
> > using, just plain SQL? Basically, I'm looking for the best solution to
> > this problem an
On 25 Nov, 10:21, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> What is the recommended method to do this right now, what are you all
> using, just plain SQL? Basically, I'm looking for the best solution to
> this problem and would like to know what the community recommends.
I can't raccomand
_demo.mpeg
~10 minutes. the audio quality sucks, (i'm no AV guy), but it gives you
a good overview. :)
derek
[EMAIL PROTECTED] wrote:
> I'm aware of a number of different schema evolution (Rails style
> migration) tools that exist, most notably the ones listed at
>
-Magee" <[EMAIL PROTECTED]>
> wrote:
>
>> On Nov 25, 2007 6:21 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>>
>>
>>
>>
>>> I'm aware of a number of different schema evolution (Rails style
>>> migration) tools t
The other "schema-evolution-ng" code is very dead. I don't have time
to maintain patches against Django anymore, and the patches I no
longer even use my own schema evolution code - it's fallen far out of
sync with Django's SVN head.
FYI - it basically just did what Dere
"Russell Keith-Magee" <[EMAIL PROTECTED]>
wrote:
> On Nov 25, 2007 6:21 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
>
>
> > I'm aware of a number of different schema evolution (Rails style
> > migration) tools that exist, most notably the on
On Nov 25, 2007 6:21 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> I'm aware of a number of different schema evolution (Rails style
> migration) tools that exist, most notably the ones listed at
> http://code.djangoproject.com/wiki/SchemaEvolution
>
> While t
I'm aware of a number of different schema evolution (Rails style
migration) tools that exist, most notably the ones listed at
http://code.djangoproject.com/wiki/SchemaEvolution
While there seems to be two branches dealing with schema evolution one
doesn't seem to have been touched i
branch and here:
http://code.djangoproject.com/wiki/SchemaEvolutionDocumentation
additionally, the latest changes from the trunk (r5787) have been merged
into the schema-evolution branch, so you won't lose any recent updates
by giving it a shot.
obviously, this is an area with a l
>
> I installed schema-evolution and everything seemed to be fine... when
> i try to run it with:
>
> python manage.py sqlevolve app_name (obviously app_name is not my app
> name :P)
>
> I get the following:
>
> BEGIN;
> Traceback (most re
Hello!
I don't know if this is the right place to a little problem I have
with this...
I installed schema-evolution and everything seemed to be fine... when
i try to run it with:
python manage.py sqlevolve app_name (obviously app_name is not my app
name :P)
I get the following:
added postgres unit tests to the schema-evolution branch. also fixed a
bug where constraint lookups in postgres broke after a model rename.
thanks,
derek
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"D
you
> start looking at doing data conversion as part of the migration
> process
we do handle at least some sequential changes. for example: renaming a
column while you're renaming the table it's in. and in the future work
section i talk about how data conversion would work
On 7/31/07, Derek Anderson <[EMAIL PROTECTED]> wrote:
> testing and documentation (plus two minor bug fixes) are checked into
> the schema-evolution branch:
>
> tests/modeltests/schema_evolution/models.py
> docs/schema-evolution.txt
Documentation should
testing and documentation (plus two minor bug fixes) are checked into
the schema-evolution branch:
tests/modeltests/schema_evolution/models.py
docs/schema-evolution.txt
> because I suspect the existing test framework will require some
> modifications to enable models
understandable. i do have both, but not integrated into django's
framework. when i finish such, would you suggest a patch posted to the
list, or attached to a bug report? (if the latter, a new bug or is
there a schema evolution bug already in discussion?)
danke,
derek
Russell Keith-
two reasons
that this hasn't been merged (or taken particularly seriously by the
core developers):
- No tests.
- No documentation.
I agree that schema evolution would be a valuable addition to Django.
However, if you (or anyone else) is serious about getting this into
trunk, adding a c
ngo-proper.
Thanks,
Derek
Derek Anderson wrote:
> Hey all,
>
> I've ported my schema evolution work from my SoC project last summer to
> Django v0.96. To use it, download the patch below, and run the
following:
>
> $ cd //site-packages/django/
> $ pa
ite a bit now and am surprised some sort of this hasn't been merged
yet, so i figured i'd bring it up to date and re-release.
daev wrote:
> It's great! I have my own schema evolution solution here
> http://code.google.com/p/django-schemaevolution/. But yours s
It's great! I have my own schema evolution solution here
http://code.google.com/p/django-schemaevolution/. But yours seems to
be more powerful.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django us
Hey all,
I've ported my schema evolution work from my SoC project last summer to
Django v0.96. To use it, download the patch below, and run the following:
$ cd //site-packages/django/
$ patch -p1 < ~//django_schema_evolution-v096patch.txt
It should output the following:
patching f
Hi all,
Does anyone know what the plans for the schema evolution branch are? Can
we expect to see its ideas and code in 1.0?
I ask as having to write a patch runner to update live schemas is the
only part of working with Django that is an annoyance :)
Mike
Hi,
I am writing an app where I will occasionally need to change my db
schema. I am not an SQL expert, and would like to confine myself to
python and django db APIs if possible (don't want to go through raw
SQL or db engine specific code). After some googling I found django's
schema
"Ramiro Morales" <[EMAIL PROTECTED]> writes:
> On 2/10/07, David Abrahams <[EMAIL PROTECTED]> wrote:
>>
>> Whatever django bugs may be lurking asid, I need to move forward with
>> my project ASAP so I'd really appreciate it if someone could give me a
>> few hints about how to evolve my existing D
On 2/10/07, David Abrahams <[EMAIL PROTECTED]> wrote:
>
> Whatever django bugs may be lurking asid, I need to move forward with
> my project ASAP so I'd really appreciate it if someone could give me a
> few hints about how to evolve my existing DB (which was created
> without the primary_key=True
"yary" <[EMAIL PROTECTED]> writes:
> IIRC, Django's admin can't handle a field with null=True and
> blank=False (which is a bit of a shame...) Try adding blank=True to
> your model's field?
Read my latest post and you'll see that I have tried that. It works,
but only if I explicitly specify the
IIRC, Django's admin can't handle a field with null=True and
blank=False (which is a bit of a shame...) Try adding blank=True to
your model's field?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" gro
David Abrahams <[EMAIL PROTECTED]> writes:
> My models.py is enclosed. It doesn't have any special dependencies.
> Would you mind trying to reproduce the problem?
>
>> Try creating a smaller project with a trimmed
>> down model -- doing the standard "remove stuff until it starts working
>> or you
Malcolm Tredinnick <[EMAIL PROTECTED]> writes:
> On Sat, 2007-02-10 at 03:34 -0500, David Abrahams wrote:
>>
>> In my attempt to use
>>
>>ForeignKey(Track, null=True)
>>
>> When I actually tried to use a null Track value, I got:
> [...traceback snipped...]
>>
>> ProgrammingError at /
On Sat, 2007-02-10 at 03:34 -0500, David Abrahams wrote:
>
> In my attempt to use
>
>ForeignKey(Track, null=True)
>
> When I actually tried to use a null Track value, I got:
[...traceback snipped...]
>
> ProgrammingError at /admin/program/session/15/
> ERROR: invalid input syntax
In my attempt to use
ForeignKey(Track, null=True)
When I actually tried to use a null Track value, I got:
Traceback (most recent call last):
File "/usr/lib/python2.4/site-packages/django/core/handlers/base.py" in
get_response
77. response = callback(request, *callback_args, **cal
ranch, or for
> Victor's changes getting rolled into the schema evolution branch? I've
> volunteered to put some work into this on the other discussion but am
> not sure what the next steps are or who will make those decisions.
At the moment, the ball is in Victor's court - he has
If nobody want's to champion the code, I can volunteer ~3-5 hours a
week to work on this stuff. My own team needs schema evolution in the
long run anyway - so it's well worth my time to make sure this
eventually gets back to trunk.
I can devote about the same time to it perhaps a b
On 29-Dec-06, at 9:22 AM, Matthew Flanagan wrote:
Victor, have you got a ticket open with your patch? It would be worth
opening one so that other people could try it out while you are
waiting for commit access to be granted.
victor i would suggest you directly mail jacob kaplan-moss with you
27;s to champion the code, I can volunteer ~3-5 hours a
> week to work on this stuff. My own team needs schema evolution in the
> long run anyway - so it's well worth my time to make sure this
> eventually gets back to trunk.
>
> I won't be able to do too much until the new
nt, but barely.
>
> The current codebase emits an SQL file with all the SQL statements to
> evolve the database, There's no provision to save the version
> anywhere, but that would be simple to do.
>
> If nobody want's to champion the code, I can volunteer ~3-5 hours a
> w
On 2006-12-24, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
>
> On 12/24/06, Todd O'Bryan <[EMAIL PROTECTED]> wrote:
>> What's the quality of the Schema Evolution code from last summer?
>
> Not done.
>
>> Is it
>> at all usable?
> No.
&g
Thanks, Ned.
That seems like a very effective way to do things. It also seems
fairly complicated (I have no idea where I would even start with
creating an evolution function, or getting the app to check for it on
startup). How much work did it take you to set up the infrastructure
to do someth
This seems a lot like what was supposed to happen in the SoC solution
(at least according to what was posted on the Wiki).
Derek seemed to do a very good job with the analysis and writing of
functional specs, but I think Victor Ng's approach is slightly
different.
Honestly, I haven't had time t
This is the method I've used in a few projects, and am now using with
Django in Tabblo:
1) You add a sequentially-increasing number called the schema number to
your code. Any time the models change in a way that changes the db
schema, this number is incremented.
2) A table is added to the d
On 12/24/06, Todd O'Bryan <[EMAIL PROTECTED]> wrote:
What's the quality of the Schema Evolution code from last summer?
Not done.
Is it
at all usable?
No.
Is it fixable?
Yes.
Is anyone else worried that Google won't
be so keen to give Django coders they've spe
h, with
> re-inputting data for testing once you modify a model?
ready made scripts - run outside django
What's the quality of the Schema Evolution code from last summer? Is it
at all usable? Is it fixable? Is anyone else worried that Google won't
be so keen to give Django coders th
On 24-Dec-06, at 9:01 AM, Aaron Jacobs wrote:
2. if you are not worried about data loss run sqlreset - or better,
drop the database, create it and run syncdb
3. if you alter a model, run sqlall, examine the out put to see what
statements django wants and put them in manually
These two are fi
On 24-Dec-06, at 8:50 AM, ringemup wrote:
Yeah, I'm good with syncdb when adding a model, it's when I
add/remove/change a field that problems occur.
Sqlreset sounds convenient... how do you deal, though, with
re-inputting data for testing once you modify a model?
ready made scripts - run o
On 12/23/06, ringemup <[EMAIL PROTECTED]> wrote:
Yeah, I'm good with syncdb when adding a model, it's when I
add/remove/change a field that problems occur.
Sqlreset sounds convenient... how do you deal, though, with
re-inputting data for testing once you modify a model?
This is becoming a F
On 12/23/06, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote:
2. if you are not worried about data loss run sqlreset - or better,
drop the database, create it and run syncdb
3. if you alter a model, run sqlall, examine the out put to see what
statements django wants and put them in manually
These
Yeah, I'm good with syncdb when adding a model, it's when I
add/remove/change a field that problems occur.
Sqlreset sounds convenient... how do you deal, though, with
re-inputting data for testing once you modify a model?
--~--~-~--~~~---~--~~
You received this
On 21-Dec-06, at 2:14 AM, ringemup wrote:
In the meantime, I'm interested in picking up some ideas: how do you
deal with changing database structures as you develop a Django app?
1. if you just add a new model - run syncdb and it automatically gets
added
2. if you are not worried about da
Hello all --
I'm aware that there are long-term plans to provide for schema
evolution in Django (much like RoR's "Migrations".
In the meantime, I'm interested in picking up some ideas: how do you
deal with changing database structures as
Hi, sorry for the long delay in replying. Holiday season and work
craziness is getting in the way of writing free software - which is
really the fun part isn't it? ;)
On 12/17/06, Steve Hutton <[EMAIL PROTECTED]> wrote:
> Ways in which my schema evolution code sucks:
>
On 2006-12-11, Victor Ng <[EMAIL PROTECTED]> wrote:
>
> I've got a rough version of schema evolution working now.
>
> The basic implementation is what the SoC project was trying to do.
[...]
> I honestly think it's a *bad* solution to the problem. I've
> merging into the trunk.
I see, 44 test cases sound like a good start.
> The code is *messy*. Writing schema evolution went hand in hand with
> me learning how Django's schema generation worked.
[...]
> If someone wants to open up commit access on the django branch for
> s
On 2006-12-15, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
> Either way, the ultimate goal would be to convince Adrian that the
> branch is stable, get him to take a look at it, and merge the branch
> into the trunk. Adrian is pretty busy, so I'm guessing he would be
> looking for some communi
On 2006-12-17, Victor Ng <[EMAIL PROTECTED]> wrote:
>
> FYI - the schema evolution code submitted from the SoC project doesn't
> work, so keeping it up to date is a moot point. There have been
> several posts from people trying to use it where the SoC version of
> the
FYI - the schema evolution code submitted from the SoC project doesn't
work, so keeping it up to date is a moot point. There have been
several posts from people trying to use it where the SoC version of
the schema evolution code just halts.
The implementation in my patch is basically a com
On 12/15/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> On 12/15/06, Waylan Limberg <[EMAIL PROTECTED]> wrote:
> > No mention of the cross-platform path files? I would say they are
> > easier to edit (comment/uncomment a line in a file) than symlink and
> > as they are a python feature (not an
On 12/15/06, Waylan Limberg <[EMAIL PROTECTED]> wrote:
> No mention of the cross-platform path files? I would say they are
> easier to edit (comment/uncomment a line in a file) than symlink and
> as they are a python feature (not an OS feature) they work on any OS.
Hey Waylan,
A patch to the doc
On 12/14/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> I've added some more instructions to the "Using branches" part of our
> documentation. Let me know if this helps.
>
> http://www.djangoproject.com/documentation/contributing/#using-branches
>
> Adrian
>
No mention of the cross-platform p
elease candidate.
The call for testing should be made by the champion; unless I've
missed a post, I don't think this has happened. The branch hasn't been
touched for 2 months, but I don't know if this is because the work is
done, or because Derek Anderson (the SOC participant r
n controversial or
>> does it follow a community consensus?
>
> There was discussion about the general problem of schema evolution
> before the SOC project was started. The discussion was started by
> Jacob, and other committers (Luke and Malcolm) weighed in at the time,
> along wi
nth, so it
> should apply cleanly to trunk.
Victor, thanks very much for your efforts on this. I will be starting
a new project soon and would like to test schema evolution.
Can you explain the differences between your patch and the schema
evolution branch itself? Are you proposi
that
it already had implemented nearly all of what I wanted. There
are still the two aforementioned issues that are solved in
branches (row-level permissions and schema evolution), but it
looks like those will come down the pike and eventually merge
with the trunk. Thanks!
-tkc
--~--~-
tch to your own copy of trunk.
Is there a problem that I'm not seeing? I'm quite sure that all the
code that my patch modifies hasn't been touched in over a month, so it
should apply cleanly to trunk.
vic
On 12/14/06, Todd O'Bryan <[EMAIL PROTECTED]> wrote:
>
> I kn
On 12/14/06, Tim Chase <[EMAIL PROTECTED]> wrote:
> Now I'd like to toy with both the Schema Evolution and the
> row-level user privs branches.
>
> Are there any "best practices" tips for swapping among them for
> testing/experimenting? Preferably without caus
On 12/14/06, Tim Chase <[EMAIL PROTECTED]> wrote:
> Are there any "best practices" tips for swapping among them for
> testing/experimenting? Preferably without causing /too/ much
> damage. :)
I can only speak to Unix-based systems, but what I've done with lots
of things of this nature is write a
> If you don't use Schema Evolution, you shouldn't be affected."
>
> I'd really like to try it, but I don't have time to keep up to date with
> two branches.
Early on, I naively just did the generic install of Django which
put it in the usual system-wide
I know the company line on the SOC Schema Evolution code is that it will
be integrated into the trunk after enough people have tested it, but I
think this creates a chicken and egg problem. People aren't going to use
it until it's in trunk and it won't be in trunk until enough
If anyone wants to poke at our schema evolution code you should be
able to apply this patch attached.
It's mostly working. The bugs I know about are:
1) M2M fields can't be repointed at new tables properly
2) there's some weird quirk with modifying null and db_index at the
same t
e general problem of schema evolution
before the SOC project was started. The discussion was started by
Jacob, and other committers (Luke and Malcolm) weighed in at the time,
along with many other interested onlookers. The resulting design is on
the wiki.
Assuming that the implementation matches t
On 2006-12-11, Victor Ng <[EMAIL PROTECTED]> wrote:
> Hi Russ,
>
> I've got a rough version of schema evolution working now.
>
> The basic implementation is what the SoC project was trying to do.
[...]
> On 12/3/06, Russell Keith-Magee <[EMAIL PROTECTED]> wr
On 12/10/06, Victor Ng <[EMAIL PROTECTED]> wrote:
>
> Hi Russ,
>
> I've got a rough version of schema evolution working now.
...
> I honestly think it's a *bad* solution to the problem. I've been
> looking at sqlalchemy and the 'migrate' proj
Ilias Lazaridis wrote:
> http://lazaridis.com/core/eval/index.html
Your phone contact is not working. I get the impression you're only a scam.
Michael
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users"
> Again, can we just let this thread die? Per the Wikipedia entry on
> him, Ilias has been banned from posting to this list.
This does not feel right. Though I understand the reasons that may have
led the admins to this decision, it's always a failure when a community
cannot evolve a way to handl
On 6/5/06, Jeroen Ruigrok van der Werven <[EMAIL PROTECTED]> wrote:
> I didn't know Wikipedia administered this list? Sure, the entry does
> point out he has had a few problems on the mailinglists, a lot owing
> up to his own behaviour. However, see below.
The Wikipedia article is not the authori
On 6/5/06, James Bennett <[EMAIL PROTECTED]> wrote:
> Again, can we just let this thread die? Per the Wikipedia entry on
> him, Ilias has been banned from posting to this list.
I didn't know Wikipedia administered this list? Sure, the entry does
point out he has had a few problems on the mailingl
On 6/5/06, Jeroen Ruigrok van der Werven <[EMAIL PROTECTED]> wrote:
> Ilias, could you stop replying to every single email and just ignore
> ad hominems? Thanks.
> And to the rest, could you please focus on purely the technical
> content instead of polluting the list with unnecessary replies?
Aga
cursory glance of evolve.py shows that some preliminary work has
been done on the schema evolution. How much of that of the above is
useful/workable? I readily admit this is not quite my cup of tea.
--
Jeroen Ruigrok van der Werven
--~--~-~--~~~---~--~~
You receiv
of your questions.
>
> Based on this, you should have a better rating about me, especially when
> knowing my private situation (or at least some indicators).
>
> -
>
> You are the Student which will execute the "Google Summer of Code"
> Project, which will implement the &
n (or at least some indicators).
-
You are the Student which will execute the "Google Summer of Code"
Project, which will implement the "Schema Evolution Support for Django",
http://code.djangoproject.com/wiki/SchemaEvolution
May I ask you to point my to a resource which shows
Guys,
I don't know who this guy is, or why everyone hates him (and I don't
want to know, so don't take this as an invitation to tell me).
But it seems to me that if he is a troll then you all have played into
his hands by posting a bunch of off topic slurs against him, resulting
in our mai
i believe it's time for...
___
/| /| | |
||__|| | Please don't |
/ O O\__ feed |
/ \ the trolls
Brett Parker wrote:
> On Mon, Jun 05, 2006 at 03:00:17PM +0300, Ilias Lazaridis wrote:
>> James Bennett wrote:
>>> Can we declare this thread closed now,
>> or course not.
>>
>> In topic posts subjecting the schema evolution support are of course
>> we
On Mon, Jun 05, 2006 at 03:00:17PM +0300, Ilias Lazaridis wrote:
>
> James Bennett wrote:
> > Can we declare this thread closed now,
>
> or course not.
>
> In topic posts subjecting the schema evolution support are of course
> welcome.
Other than you, which se
James Bennett wrote:
> Can we declare this thread closed now,
or course not.
In topic posts subjecting the schema evolution support are of course
welcome.
> and ask that anyone who wishes to play with Ilias do so off-list?
>
> My inbox thanks you in advance.
For anyone who wish
Can we declare this thread closed now, and ask that anyone who wishes
to play with Ilias do so off-list?
My inbox thanks you in advance.
--
"May the forces of evil become confused on the way to your house."
-- George Carlin
--~--~-~--~~~---~--~~
You received
;s something that makes me lose my temper, it's someone telling
> me what I can and cannot say.
I just remind you that your writings are off-topic.
This is a technical topic, subjecting a simple schema evolution support
that I've implemented for django:
htt
> "This Project is Committed to Users of Open Source Products. It tries to
> save their time,
...while wasting the developers' one, right. :-|
> "The weaknesses of the Open Source Product, the Code Base, the producing
> Project, the surounding Community and the Leadership are transparently
> pr
Brett Parker wrote:
> On Mon, Jun 05, 2006 at 01:30:10PM +0300, Ilias Lazaridis wrote:
>> Tom Tobin wrote:
>>> On 6/4/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
>>>> I've create a simple Schema Evolution Support for Django and I am
>>>> wor
; for wanting to dismiss you because of it.
>
>> I've _implemented_ as simple schema evolution for django, which I need
>> for a personal project with a _deadline_.
>
> And based on your past behaviours, that might just be a result of you
> trying to become an even b
On Mon, Jun 05, 2006 at 01:30:10PM +0300, Ilias Lazaridis wrote:
>
> Tom Tobin wrote:
> > On 6/4/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
> >> I've create a simple Schema Evolution Support for Django and I am
> >> working to created a
..]
>>
>> This starts to become ridiculous.
>
> What do you expect?
That people focus on the technical nature of this thread and the results.
> To be honest I actually think some of the things on the page [1] you
> posted may be usable.
I've implemente
Tom Tobin wrote:
> On 6/4/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
>> I've create a simple Schema Evolution Support for Django and I am
>> working to created a Django Quickstart, which will allow even
>> unexperienced users to see a django site running w
tekNico wrote:
>> Your comments are very welcome.
>
> Wow, man (or whatever you are), you're something. :-)
>
> You actually cite your detractors on your own pages (see bottom of
> http://case.lazaridis.com/multi/wiki/DjangoAudit , and of
> http://lazaridis.com/core/eval/index.html ).
"This Pro
> Your comments are very welcome.
Wow, man (or whatever you are), you're something. :-)
You actually cite your detractors on your own pages (see bottom of
http://case.lazaridis.com/multi/wiki/DjangoAudit , and of
http://lazaridis.com/core/eval/index.html ).
Maybe you actually *mean* something,
On 6/4/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
>
> I've create a simple Schema Evolution Support for Django and I am
> working to created a Django Quickstart, which will allow even
> unexperienced users to see a django site running within their browsers.
Ilias Lazar
1 - 100 of 105 matches
Mail list logo
