Hi guys,
I apologize for the confusing title.
I'm still confused on using the models in a m2m relationship. Suppose
I have the models below from the tutorials on the django site:
class Author(models.Model):
name = models.CharField(max_length=50)
email = models.EmailField()
def __uni
You don't even need to tell Django what
encoding your database uses: that is handled transparently."
All is clear and the sky is blue now.
Thank you Karen and Malcolm!
On 12月12日, 午後12:13, "Karen Tracey" wrote:
> On Thu, Dec 11, 2008 at 10:02 PM, I.A wrote:
>
> >
Hi,
I'm wondering the correct way to save unicode data in MySQL through
django's models.
The application I'm building reads a raw email and then stores the
text data into the database. I process the email like so:
import email
mess822 = email.message_from_string(email_raw_data)
mail_unicode_data
Hi,
I'm writing an application that recieves a file from an outside source
(not through a view though) which is written to the tmp directory and
then writing it into the db through the FileField. Obviously the file
must also be written to a path which can be retrieved later by just
calling .path
a mysql database? That may be the source of the trouble.
> IIRC, some versions of MySQL, depending on the inner database, don't
> support transactions.
>
> -Zeroth
>
> On Nov 29, 6:56 pm, "I.A" <[EMAIL PROTECTED]> wrote:
>
> > hi guys,
>
> > i
hi guys,
i'm wondering how transaction really works with django models. i've
gone through the documentation in
http://docs.djangoproject.com/en/dev/topics/db/transactions/?from=olddocs
but it doesn't work for me.
this is a sample of my code. not that this code is being used in the
backend and d
6 matches
Mail list logo