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 wrote:
> On Feb 28, 10:05 am,
On Feb 28, 10:05 am, Tim 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 wrote:
> > > Try appending the custom location to the beginning
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 wrote:
> > Try appending the custom location to the beginning of your PYTHONPATH.
>
> > Sincerely,
> > And
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 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 wrote:
>
>> hi,
>>
On Feb 25, 4:00 pm, Andre Terra wrote:
> On Fri, Feb 25, 2011 at 5:28 PM, Tim 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
Try appending the custom location to the beginning of your PYTHONPATH.
Sincerely,
Andre Terra
On Fri, Feb 25, 2011 at 5:28 PM, Tim 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/
6 matches
Mail list logo