On 06/22/2011 03:02 AM, Roy Smith wrote:
> In article <4e012e8d$0$23682$426a3...@news.free.fr>,
> News123 wrote:
>
>
> I don't see any reason you couldn't use the Model layer by itself, if
> you want to. It pretty much stands on its own.
Thanks a lot for confirming,
I have now my small exam
On 06/22/2011 03:04 AM, Ian Kelly wrote:
>>
>> So I need at least a little more to make my script work.
>
> There's a bit of magic in the way Django finds things, and I think
> you'll still need to keep the basic structure of a Django project --
> models should be in a "models.py" file located in
It seems I found a solution (refer to end of this tessage).
Not sure though if there are any drawbacks or if this method of working
could cause any other issues.
On 06/22/2011 02:42 AM, News123 wrote:
> On 06/22/2011 01:51 AM, News123 wrote:
>> Hi,
>>
>> I have a small application running on a
In article <4e012e8d$0$23682$426a3...@news.free.fr>,
News123 wrote:
> Hi,
>
> I have a small application running on a host without web server and
> without any need for django except its ORM accessing data bases without
> explicitely writing sql queries.)
You would do much better to ask this q
On Tue, Jun 21, 2011 at 6:42 PM, News123 wrote:
> ###
> If running myapp.py I get following output:
>
> yes this line is executed
> Traceback (most recent call last):
> File "./myapp.py", line 11, in
> class Mini(models.Model):
> File
> "/opt/my_py
On 06/22/2011 01:51 AM, News123 wrote:
> Hi,
>
> I have a small application running on a host without web server and
> without any need for django except its ORM accessing data bases without
> explicitely writing sql queries.)
>
> I assume there's many libraries (SQL Alchemy or others), which cou
Hi,
I have a small application running on a host without web server and
without any need for django except its ORM accessing data bases without
explicitely writing sql queries.)
I assume there's many libraries (SQL Alchemy or others), which could do
this job. and which migh have less overhead tha
