Thank you.
This is a very important piece of information / advice
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To
On Mon, Jun 16, 2008 at 12:41 PM, Pepsi330ml <[EMAIL PROTECTED]> wrote:
>
> I'm interested to know also whether there is any adv in using anyone
> of the ORM.
> Using the Django ORM will provide ease of use.
> But is there a major adv to use Object or Alchemy over the Django ORM?
I'm interested to know also whether there is any adv in using anyone
of the ORM.
Using the Django ORM will provide ease of use.
But is there a major adv to use Object or Alchemy over the Django ORM?
Russ,
You mentioned:
"There's nothing stopping you from using SQLObject or SQLAlchemy in
I'm wondering - are there any performance related reasons to switch from
Django ORM to say sqlalchemy?
Why does this discussion reoccur every once in a while if there is nothing
to gain?
Are there other Good Reasons (tm) to switch?
Oscar
On Fri, Jun 13, 2008 at 8:49 AM, James Bennett <[EMAIL
On Fri, Jun 13, 2008 at 1:15 AM, Pepsi330ml <[EMAIL PROTECTED]> wrote:
> i shall go read more about SqlObject then.
If you're planning to use Django, and if you do not already have a
very strong attachment to another ORM, consider just using the one
that comes with Django. It will make your life
oh...ok.
i shall go read more about SqlObject then.
The syntax is v close to Django ORM, tat's y i got myself mixed up.
There are different when i compare all the codes side by side.
The syntax for the declaration of the table is similar but
Django ORM use syncdb to create the table in the
If all you did was install MySQLdb and Django then yes.
-- Horst
On Fri, Jun 13, 2008 at 8:02 AM, Pepsi330ml <[EMAIL PROTECTED]> wrote:
> meaning all along i had been using Django ORM?
> >
>
--~--~-~--~~~---~--~~
You received this message because you are
meaning all along i had been using Django ORM?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group,
>
> one of the installation steps for Django is to install MySQLdb or
> psycopgl.
> These are sqlobject.
No, they are not. Those are the "connectors" used by python to connecto to
either MySQL or PostrgrSQL. You need them whether you use SQLObject,
SQLAlchemy or just to access the DB
humm...
one of the installation steps for Django is to install MySQLdb or
psycopgl.
These are sqlobject.
Therefore, i curious why they made such recommendation.
There should be a gd reason to use them.
--~--~-~--~~~---~--~~
You received this message because you
wanted some advice and opinion frm ppl that had use django with either
one.
I'm v new to django. Thus hoping to gather some experience here first.
Thanks for the help
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
On Fri, Jun 13, 2008 at 10:33 AM, Pepsi330ml <[EMAIL PROTECTED]> wrote:
>
> In the Django Tutorial and Django Book, all the codes example was
> using SQLObject.
erm... no. None of the code examples use SQLObject. They all use
Django's SQL ORM (Object-Relation Model). SQLObject and SQLAlchemy are
Well, you can use both anyway
On Fri, Jun 13, 2008 at 10:03 PM, Pepsi330ml <[EMAIL PROTECTED]> wrote:
>
> In the Django Tutorial and Django Book, all the codes example was
> using SQLObject.
>
> Is there a specific reason for using Django with SQLObject instead of
> SQLAlchemy?
>
> >
>
In the Django Tutorial and Django Book, all the codes example was
using SQLObject.
Is there a specific reason for using Django with SQLObject instead of
SQLAlchemy?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
14 matches
Mail list logo
