Monday, February 28, 2011

Re: sqlite path

Make sure the directory containing your sqlite database is writable by the user your web server is running as.  sqlite occasionally creates some temporary files in the same directory side-by-side your actual sqlite file.

Brian

On Mon, Feb 28, 2011 at 10:45 AM, Tim <jtim.arnold@gmail.com> wrote:
On Feb 28, 10:05 am, Tim <jtim.arn...@gmail.com> wrote:
> On Feb 26, 9:25 am, spa...@gmail.com wrote:
>
>
>
>
>
>
>
>
>
> > Have you tried updating the DB path in settings.py and creating a new db
> > file?
>
> > On Sat, Feb 26, 2011 at 2:30 AM, Andre Terra <andrete...@gmail.com> wrote:
> > > Try appending the custom location to the beginning of your PYTHONPATH.
>
> > > Sincerely,
> > > Andre Terra
>
> > > On Fri, Feb 25, 2011 at 5:28 PM, Tim <jtim.arn...@gmail.com> wrote:
>
> > >> hi,
> > >> I'm using Django 1.2.3 and I have a new sqlite (3.7.5) installed in a
> > >> custom location.
> > >> There is an old sqlite (3.6.23.1) installed in /usr/local/bin/.
>
> > >> How do I tell Django to use the new sqlite? I'm on FreeBSD 8.0.
>
> > >> thanks,
> > >> --Tim Arnold
>
> > >> --
> > >> 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, send email to
> > >> django-users+unsubscribe@googlegroups.com.
> > >> For more options, visit this group at
> > >>http://groups.google.com/group/django-users?hl=en.
>
> > >  --
> > > 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, send email to
> > > django-users+unsubscribe@googlegroups.com.
> > > For more options, visit this group at
> > >http://groups.google.com/group/django-users?hl=en.
>
> > --http://spawgi.wordpress.com
> > We can do it and do it better.
>
> hi, I converted my original mysql database to sqlite3. Firefox sqlite
> extension can view the database and it looks okay.  It looks like the
> Django settings are okay to me--here they are:
>
> DATABASES = {
>     'default': {
>         'ENGINE': 'django.db.backends.sqlite3',
>         'NAME': '/Apps/web/myproject.sqlite',
>         'USER': '',
>         'PASSWORD': '',
>         'HOST': '',
>         'PORT': '',
>    }}
>
> And here are the dir permissions of /Apps/web:
>
> drwxrwxrwx  4 tiarno  wheel     4096 Feb 25 14:54 ./
> drwxr-xr-x  8 tiarno  wheel     4096 Feb 23 17:24 ../
> drwxrwxrwx  5 tiarno  wheel     4096 Feb 25 15:16 django/
> drwxr-xr-x  2 tiarno  wheel     4096 Sep 17 15:45 home/
> -rwxrwxrwx  1 tiarno  wheel  1588224 Feb 25 13:51 myproject.sqlite*
>
> I run validate and get '0 errors found'. I run syncdb and get this:
>
>  python manage.py syncdb
> Traceback (most recent call last):
>   File "manage.py", line 11, in <module>
>     execute_manager(settings)
>   File "/usr/local/lib/python2.7/site-packages/django/core/management/
> __init__.py", line 438, in execute_manager
>     utility.execute()
>   File "/usr/local/lib/python2.7/site-packages/django/core/management/
> __init__.py", line 379, in execute
>     self.fetch_command(subcommand).run_from_argv(self.argv)
>   File "/usr/local/lib/python2.7/site-packages/django/core/management/
> base.py", line 191, in run_from_argv
>     self.execute(*args, **options.__dict__)
>   File "/usr/local/lib/python2.7/site-packages/django/core/management/
> base.py", line 220, in execute
>     output = self.handle(*args, **options)
>   File "/usr/local/lib/python2.7/site-packages/django/core/management/
> base.py", line 351, in handle
>     return self.handle_noargs(**options)
>   File "/usr/local/lib/python2.7/site-packages/django/core/management/
> commands/syncdb.py", line 55, in handle_noargs
>     tables = connection.introspection.table_names()
>   File "/usr/local/lib/python2.7/site-packages/django/db/backends/
> __init__.py", line 498, in table_names
>     return self.get_table_list(cursor)
>   File "/usr/local/lib/python2.7/site-packages/django/db/backends/
> sqlite3/introspection.py", line 51, in get_table_list
>     ORDER BY name""")
>   File "/usr/local/lib/python2.7/site-packages/django/db/backends/
> util.py", line 15, in execute
>     return self.cursor.execute(sql, params)
>   File "/usr/local/lib/python2.7/site-packages/django/db/backends/
> sqlite3/base.py", line 200, in execute
>     return Database.Cursor.execute(self, query, params)
> django.db.utils.DatabaseError: disk I/O error
>
> thanks for any ideas,
> --Tim

More info. This isn't a django issue after all. I just tried a simple
select * using the sqlite shell and got a disk io error. If I move the
database to my home directory, the select works, so there's something
weird going on with the mounted disk where my django app lives (a
netapp device).

sorry for the noise,
--Tim

--
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, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.




--
Brian Bouterse
ITng Services

--
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, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.

No comments:

Post a Comment