I have (tried running migrations), although I didn't change my models and I'm
not sure if I did it after or before the problem started.
You're probably right though, if the current database has issues but not the
new one, the old one might have somehow been corrupted... It's probably a good
: "No such table" error, with different tablename as in query
Hi,
@Matthew: I've just tried with a blank database, and everything appeared to
work perfectly. I couldn't reproduce the bug I'm seeing now. The database
structure looks identical though; in both cases the table name is
"fina
Hi,
*@Matthew: *I've just tried with a blank database, and everything appeared
to work perfectly. I couldn't reproduce the bug I'm seeing now. The
database structure looks identical though; in both cases the table name is
"finance_transaction", not "main.finance_transactions".
*@Michal: *I'm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Mon, Oct 08, 2018 at 10:29:30AM -0400, Michel Lavoie wrote:
> Hi Matthew,
>
> Thank you for the suggestion, but as I mentioned the error is not limited
> to my views.py; it's also present in the auto generated admin page.
> Basically in the
[mailto:django-users@googlegroups.com] On
Behalf Of Michel Lavoie
Sent: Monday, October 8, 2018 9:30 AM
To: django-users@googlegroups.com
Subject: Re: "No such table" error, with different tablename as in query
Hi Matthew,
Thank you for the suggestion, but as I mentioned the error is not lim
-users@googlegroups.com [mailto:
> django-users@googlegroups.com] *On Behalf Of *Michel Lavoie
> *Sent:* Sunday, October 7, 2018 6:17 AM
> *To:* Django users
> *Subject:* "No such table" error, with different tablename as in query
>
>
>
> Hi,
>
>
>
> I've just upgra
Sent: Sunday, October 7, 2018 6:17 AM
To: Django users
Subject: "No such table" error, with different tablename as in query
Hi,
I've just upgrade my Django installation from 1.11 to 2.0, and then to 2.1, and
am now getting a weird bug with one of my applications. Whenever I try to
exec
Hi,
I've just upgrade my Django installation from 1.11 to 2.0, and then to 2.1,
and am now getting a weird bug with one of my applications. Whenever I try
to execute a view that either deletes or saves a transation in my "finance"
app, I get the following error:
OperationalError at
I don't think that sould be possible to change real table name "on the
fly". If I'm not mistaken, that kind of attribute is used by model's meta
class during class creation process to populate the django model cache,
which in turn only occurs during the django configuration step.
2017-07-13 14:08
Hi I encounter same problem as your, do you already got the solution? Any
help will be appreciated, thank you~
On Saturday, November 14, 2015 at 1:40:21 AM UTC+7, evil...@gmail.com wrote:
>
> Hello.
> I've got the same model in two projects and want to copy data from one to
> another using
Thank YOU!!!
On Thursday, November 5, 2009 at 10:58:55 AM UTC+2, BlueBird wrote:
>
>
> Ok, I found a way around the problem, in case anyone ever has the same
> problem. If you specify TEST_DATABASE_NAME in your settings, it will
> force sqllite to use a file database instead of in-memory
On Sun, Nov 15, 2015 at 12:04 AM, wrote:
> Thanks for the answer.
> What do you suggest to use instead of this ugly method, raw sql?
>
Would it make sense to serialize a ModelDatabaseA object (perhaps into JSON
or a standard Python dict) and use that to populate/create a
Thanks for the answer.
What do you suggest to use instead of this ugly method, raw sql?
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Thanks for the answer.
What do you suggest to use instead of this ugly method, raw sql?
суббота, 14 ноября 2015 г., 17:59:51 UTC+3 пользователь Tim Graham написал:
>
> I'm not sure that type of monkeypatching of Model._meta.db_table is meant
> to be supported. You could try to bisect Django's
I'm not sure that type of monkeypatching of Model._meta.db_table is meant
to be supported. You could try to bisect Django's commit history to find
the commit that changed the behavior. My guess it that it might have to do
with some internal caching such that your monkeypatch no longer has any
Hello.
I've got the same model in two projects and want to copy data from one to
another using model meta 'db_table' option:
my_model_original_table_name = MyModel._meta.db_table
MyModel._meta.db_table = 'old_project_table_name'
old_objects =
On Saturday, March 1, 2014 3:29:01 PM UTC-4:30, Omar Acevedo wrote:
>
> Hello, I'm having an issue in/with Django, which is on a shared hosting,
> and I'm using virtualenv and fastcgi. (<- saying this, just in case it
> helps in something)
>
> I'm getting
> "OperationalError at /admin/
> no
Hello, I'm having an issue in/with Django, which is on a shared hosting,
and I'm using virtualenv and fastcgi. (<- saying this, just in case it
helps in something)
I'm getting
"OperationalError at /admin/
no such table: auth_user"
after entering my credentials (username & pw) that were set
On 24 oct, 21:52, BlueBird wrote:
> Hi,
>
> I've got a strange behavior. My application is split between a web
> frontend and a backend which use the DB to exchange tasks and results.
>
> The problem is with the backend. It's just a regular program,
> accessing the DB to
Hi,
I've got a strange behavior. My application is split between a web
frontend and a backend which use the DB to exchange tasks and results.
The problem is with the backend. It's just a regular program,
accessing the DB to fetch tasks, completing them and then storing the
result in a DB. The
O.K.
Thanks.
I will try that.
On Sep 14, 11:36 am, Bill Freeman wrote:
> Make DATABASE_NAME an absolute path.
>
>
>
> On Mon, Sep 14, 2009 at 12:11 AM, AIM wrote:
>
> > HI,
>
> > When I browse to
> >http://127.0.0.1:8000/mysite/Start/
>
> > I get
Make DATABASE_NAME an absolute path.
On Mon, Sep 14, 2009 at 12:11 AM, AIM wrote:
>
> HI,
>
> When I browse to
> http://127.0.0.1:8000/mysite/Start/
>
> I get the following error:
>
> OperationalError at /mysite/Start/
>
> no such table: wiki_page
>
> Request Method:
On Mon, Sep 14, 2009 at 12:11 AM, AIM wrote:
>
> HI,
>
> When I browse to
> http://127.0.0.1:8000/mysite/Start/
>
> I get the following error:
>
> OperationalError at /mysite/Start/
>
> no such table: wiki_page
>
> Request Method: GET
> Request URL:
HI,
When I browse to
http://127.0.0.1:8000/mysite/Start/
I get the following error:
OperationalError at /mysite/Start/
no such table: wiki_page
Request Method: GET
Request URL:http://127.0.0.1:8000/mysite/Start/
Exception Type: OperationalError
Exception Value:
no such
mmm!... That's interesting
The dbshell says: "Error: You appear not to have the 'sqlite3' program
installed or on your path."
Like i said, with the runserver everything is fine... that's weird
I added the sqlite3 app dir to the path env-var in the OS but the same
error raises in "manage.py
On Jul 29, 3:54 am, marcoshernandez wrote:
> Im having this error in my application (both admin models and my app
> models) I'm almost certain that has to be something with Apache-
> mod_wsgi not finding the files... but I just can't find the origin of
> the error...
>
Yup. Everything's fine with the django development server, the error
raises in Apache
(Sorry about the double reply but i thought it'll be better if the
community keeps track of the information, in sake of the shared
knowledge ;) )
On Jul 28, 10:56 pm, Luke Seelenbinder
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Did you run manage.py syncdb in your project folder?
And are the apps in your settings.py?
Luke Seelenbinder
marcoshernandez wrote:
> Im having this error in my application (both admin models and my app
> models) I'm almost certain that has to be
Im having this error in my application (both admin models and my app
models) I'm almost certain that has to be something with Apache-
mod_wsgi not finding the files... but I just can't find the origin of
the error...
complete traceback next:
Environment:
Request Method: GET
Request URL:
On 5/2/2009 8:32 AM, tekion wrote:
> No, I ended up removing the db and recreating it via manage.py
> syncdb. it works after this.
>
> Next time I will log into SQL lite and check it out.
>
> I am curious why running "manage.py syncdb" didn't work until I blow
> away the db and re-run it.
Is
No, I ended up removing the db and recreating it via manage.py
syncdb. it works after this.
Next time I will log into SQL lite and check it out.
I am curious why running "manage.py syncdb" didn't work until I blow
away the db and re-run it.
On May 2, 10:56 am, George Song
On 5/2/2009 6:02 AM, tekion wrote:
> Exception Type: OperationalError at /play_django/page/start/save/
> Exception Value: no such table: mywiki_page_tags
Did you log into SQLite and see if that table exists?
--
George
--~--~-~--~~~---~--~~
You received this
Folks, I am following a tutorial. I am getting the following error
even after I ran manage.py syncdb:
Traceback:
File "C:\Python26\lib\site-packages\django\core\handlers\base.py" in
get_response
92. response = callback(request, *callback_args,
**callback_kwargs)
File
Malcolm,
I've posted a new ticket and assigned it to you at:
http://code.djangoproject.com/ticket/9188
I look forward to hearing from you.
Thanks again!
Christian
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Thanks for your quick reply. I will submit a bug report.
Thanks!
Christian
On Sep 22, 9:45 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> On Mon, 2008-09-22 at 18:22 -0700, cfobel wrote:
> > Hello,
>
> > I'm encountering anerrorwhen performing a lookup that spans
> > relationships. The
On Mon, 2008-09-22 at 18:22 -0700, cfobel wrote:
> Hello,
>
> I'm encountering an error when performing a lookup that spans
> relationships. The query is as follows:
>
> myitems =
> MyItem.objects_all.exclude(user__somemodel__created__gte=(datetime.now()
> - timedelta(days=3)))
>
> With the
Hello,
I'm encountering an error when performing a lookup that spans
relationships. The query is as follows:
myitems =
MyItem.objects_all.exclude(user__somemodel__created__gte=(datetime.now()
- timedelta(days=3)))
With the following (stripped) models:
class MyItem(models.Model):
user =
37 matches
Mail list logo