On 8/4/07, Derek Anderson <[EMAIL PROTECTED]> wrote:
Hi Derek;
First off - let me apologize - my comments were not intended to be
harsh or derogatory.
You have done some great work here, and I don't want to give you the
impression that your efforts are not appreciated and valued.
However, your
hey, i will be able to send you my patch on monday.
the generic idea is to attach LIMIT as if the backend supported it and
at query execution time replace it with TOP.
OFFSET can be handled by nested queries but i did not have enough time
to finish that.
(i.e.
http://groups.google.com/group/djan
Hi Jeremy, thanks for the info,
I meant mssql, sorry.
the issue with object_id is that mssql can not insert an integer PK
into a TEXT field.
so how should it be handled then if the field type can not be changed?
peter
On Aug 3, 9:02 pm, "Jeremy Dunck" <[EMAIL PROTECTED]> wrote:
> On 8/3/07
Brantley Harris wrote:
> Your
> philosophy seems to be, "Those problems are spiky edge cases", but I
> think the hope was they would be solved as well, or at least put on
> track for a solution later on.
more like "low-hanging-most-useful-fruit first" :) everyone agrees
that there will never b
On 8/3/07, pk11 <[EMAIL PROTECTED]> wrote:
> - django's admin log model object_id's type is changed from text to
> integer (is there a reason why object_id is declared as textfield?)
object_id is whatever the arbitrary model's PK is, and you can't
assume it's an integer in the general case. The
2007/8/4, Brantley Harris <[EMAIL PROTECTED]>:
> ps. Did you ever see my long-ago proposal?
> (http://code.djangoproject.com/wiki/SchemaEvolutionProposal)
Hi Brantley, you have written very nice proposal, I like it!
Your evolutions are python equivalent of Rails migrations, but have
better syntax
Excelent. Please send me your patch so I take a look at it.
I finish today a implementation of LIMIT so I'm interested in how you
solve it.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group
Hi,
mamcx schrieb:
> I have finalize a beta code for the LIMIT mimic for Sql server, but
> wonder if all the test cases are running.
>
> When I run runtest this is show:
>
> Ran 2 tests in 0.109s
>
> OK
>
> I don't think is normal...
>
> I'm running this under a windows box, but for comparin
I have finalize a beta code for the LIMIT mimic for Sql server, but
wonder if all the test cases are running.
When I run runtest this is show:
Ran 2 tests in 0.109s
OK
I don't think is normal...
I'm running this under a windows box, but for comparing, what is the
correct output of this?
--~
hey all,
we are also using django with pymssql/mssql, in addition to your work,
we changed:
- django's admin log model object_id's type is changed from text to
integer (is there a reason why object_id is declared as textfield?)
- pymssql is changed to allow unicode strings
- simulate limit with
Yes...
I'm waitting to see if the actual pathc for pymssql is enough or still
need more work for do a single submit...
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this grou
OK.. I gave it a shot.. not really satisfied with the patch yet, but
it's a start. Feel free to suggest improvements (or submit a better,
or extended, patch) if need be.
Here's the ticket http://code.djangoproject.com/ticket/5076
Hope everyone has a great friday!
Regards,
Daniel
--~--~-
Russell is being to harsh, I say great work.
But I don't think he's necessarily incorrect. Basically, the trouble
is that your solution doesn't really solve the bigger problems. Your
philosophy seems to be, "Those problems are spiky edge cases", but I
think the hope was they would be solved as
On 8/3/07, Marty Alchin <[EMAIL PROTECTED]> wrote:
> Ah, but sickness must be put into perspective. You have no idea.
Ha!
Right you are -- I'm the sick one here, it appears :)
Sorry for the derail; carry on.
Jacob
--~--~-~--~~~---~--~~
You received this message
On Fri, Aug 03, 2007 at 01:09:28PM -0500, Jacob Kaplan-Moss wrote:
> On 8/3/07, Marty Alchin <[EMAIL PROTECTED]> wrote:
> > I'd add .py to that list, if it gets done this way.
>
> Wait - are you using Django templates to generate *Python*?
>
> That's... just... *sick*.
No, that's just meta-progr
On 8/3/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
> Wait - are you using Django templates to generate *Python*?
Actually, no. But since Django uses Django templates to generate (bits
of) Django[1] code, I thought it might be worth specifying.
> That's... just... *sick*.
Ah, but sickness m
On 8/3/07, Marty Alchin <[EMAIL PROTECTED]> wrote:
> I'd add .py to that list, if it gets done this way.
Wait - are you using Django templates to generate *Python*?
That's... just... *sick*.
Jacob
--~--~-~--~~~---~--~~
You received this message because you are s
On 8/3/07, Derek Anderson <[EMAIL PROTECTED]> wrote:
> is there a way to get runtests.py to run the tests for multiple backends
> at a time? right now i'm just editing my settings.py file manually each
> time, and wanted to check before i wrote my own script. :)
I posted mine here: http://www.d
Cobbling a script to run with different settings is probably the
easiest way. I have a buildbot environment on a virtual machine that I
have doing that sort of testing, but it's distributed out and probably
not what you want to copy. Deep under the covers, it relies on pulling
in explicit config f
hey all,
is there a way to get runtests.py to run the tests for multiple backends
at a time? right now i'm just editing my settings.py file manually each
time, and wanted to check before i wrote my own script. :)
thanks,
derek
--~--~-~--~~~---~--~~
You receiv
On 8/3/07, Tom Tobin <[EMAIL PROTECTED]> wrote:
> Hmm ... that could work; we'd just need a reasonable whitelist. .txt
> is the obvious case; I'm trying to think of others (typical
> configuration files, etc.). Off the top of my head, I'd add .conf,
> .ini, and the regex ^\..*rc$ -- can anyone c
Russell Keith-Magee wrote:
> - The 'aka' approach has some serious flaws.
for the scenario you give the aka approach (or any formatting of
model+existing_schema+rename_metadata) works just fine. i detail how
(with working examples and sql output) here:
http://kered.org/blog/2007-08-03/schema-
On 8/2/07, Simon Willison <[EMAIL PROTECTED]> wrote:
>
> On Aug 1, 7:56 pm, "Tom Tobin" <[EMAIL PROTECTED]> wrote:
> > Set autoescaping on by default for anything ending in ``.html`` (and,
> > perhaps, ``.htm``), and off otherwise.
>
> I've been thinking about this a bit, and it seems like it could
> Can you please file a ticket so we don't loose this?
Ticket filed:
http://code.djangoproject.com/ticket/5075
Cheers
Thejaswi Puthraya
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To
On 8/3/07, Thejaswi Puthraya <[EMAIL PROTECTED]> wrote:
> When I try to use the manage.py sql command I get a weird
> error. (Looks like the oracle backend is still not unicode
> compatible.)
Can you please file a ticket so we don't loose this?
Thanks,
Jacob
--~--~-~--~~--
Hey Mamcx --
On 8/2/07, mamcx <[EMAIL PROTECTED]> wrote:
> I submit a ticket with patchs for enable a new backend, so we can have
> a clean direction from the ado_mssql confusion of tickets.
Lookin' good -- keep up the good work!
I know you're very much in the early stages of this, so I'll hold
I have Django SVN version 5788 and just installed cx_Oracle version
4.3.1.
When I try to use the manage.py sql command I get a weird
error. (Looks like the oracle backend is still not unicode
compatible.)
Here is the output that I get:
Traceback (most recent call last):
File "manage.py", lin
On 8/3/07, SmileyChris <[EMAIL PROTECTED]> wrote:
> Keeping documentation up should be rather high priority. This ticket
> has been sitting for a while untouched. Some love, anyone?
D'oh! I keep getting distracted before looking into this. Thanks for
the prod; I'll fix it as soon as I get to work
On 7/13/07, David Larlet <[EMAIL PROTECTED]> wrote:
> * About users, how can I handle django users' permissions? John
> Sutherland had already done some work on django-crudapi [1] and it
> could be interesting to allow this access control.
Good question. I would subclass one of the authentication
Keeping documentation up should be rather high priority. This ticket
has been sitting for a while untouched. Some love, anyone?
http://code.djangoproject.com/ticket/4853
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Grou
Hi Adam,
On Fri, Aug 03, Adam Schmideg wrote:
>
> Hi,
>
> I implemented a csv serializer/deserializer. I tried to figure out
> how I can contribute to django with it, reading
> http://www.djangoproject.com/documentation/contributing/#submitting-patches
> but the process was not quite clear to
Hi,
I implemented a csv serializer/deserializer. I tried to figure out
how I can contribute to django with it, reading
http://www.djangoproject.com/documentation/contributing/#submitting-patches
but the process was not quite clear to me. Shall I open a ticket for
it, and post a patch? Could yo
On Aug 3, 11:34 am, Michael Radziej <[EMAIL PROTECTED]> wrote:
> On Fri, Aug 03, Niels wrote:
> > On Aug 3, 11:10 am, Michael Radziej <[EMAIL PROTECTED]> wrote:
> > > This actually adds some documentation for any reviewer. 'safe' means:
> > > "Hey, I haven't simply forgot escaping, I meant it!"
>
Michael Radziej wrote:
> To make this clear, I'll provide an example:
>
Thanks! That's cleared it up.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to
On Fri, Aug 03, Ivan Sagalaev wrote:
>
> Michael Radziej wrote:
> > {% autoescape %} always needs an {% endautoescape %}, generating a node
> > during template parsing. Everything between {% autoescape %} and {%
> > endautoescape %} is put in its subnode list.
> >
> > If a VariableNode is below
Michael Radziej wrote:
> {% autoescape %} always needs an {% endautoescape %}, generating a node
> during template parsing. Everything between {% autoescape %} and {%
> endautoescape %} is put in its subnode list.
>
> If a VariableNode is below an {% autoescape on %} in the template node tree,
>
On Fri, Aug 03, Niels wrote:
> On Aug 3, 11:10 am, Michael Radziej <[EMAIL PROTECTED]> wrote:
> > This actually adds some documentation for any reviewer. 'safe' means:
> > "Hey, I haven't simply forgot escaping, I meant it!"
>
> Jacob used the word 'raw' here, which is indeed a more appropriate
On Aug 3, 11:10 am, Michael Radziej <[EMAIL PROTECTED]> wrote:
> On Thu, Aug 02, James Bennett wrote:
>
...
> > From the descriptions above -- of using the autoescape toggle in a
> > base template to inherit through to every child template -- it seems
> > that the only logical thing is for it to n
On Thu, Aug 02, James Bennett wrote:
>
> On 8/2/07, Todd O'Bryan <[EMAIL PROTECTED]> wrote:
> > Can this possibly be right? If I want to include a single variable that
> > includes some HTML (such as {{ form.as_table }}), do I have to turn off
> > auto-escaping for everything else in the page?
>
Coincidentally, I mostly recently encountered this problem with form
character encoding an hour ago when I tried to use the International
Phonetic Alphabet in a comment on Ian Bicking's blog post[1] about
how to pronounce Django :-)
(note: at time of writing, Ian hadn't approved my comment
40 matches
Mail list logo
