PDA

View Full Version : 2256 does not start: prepare_cached failed



mherger
2005-02-28, 00:28
When starting svn with the existing revision 2256 .slimserversql.db I get
the following error:

DBD::SQLite::db prepare_cached failed: no such column: disc(1) at dbdimp.c
line 263 at /home/mh/eclipse/SVN/CPAN/Ima/DBI.pm line 391.
DBD::SQLite::db prepare_cached failed: no such column: disc(1) at dbdimp.c
line 263 at /home/mh/eclipse/SVN/CPAN/Ima/DBI.pm line 391.

Removed the db file and it started just fine.

--

Michael

-----------------------------------------------------------
Help translate SlimServer by using the
SlimString Translation Helper (http://www.herger.net/slim/)

Dan Sully
2005-02-28, 10:52
* Michael Herger shaped the electrons to say...

>When starting svn with the existing revision 2256 .slimserversql.db I get
>the following error:
>
>DBD::SQLite::db prepare_cached failed: no such column: disc(1) at dbdimp.c
>line 263 at /home/mh/eclipse/SVN/CPAN/Ima/DBI.pm line 391.
>DBD::SQLite::db prepare_cached failed: no such column: disc(1) at dbdimp.c
>line 263 at /home/mh/eclipse/SVN/CPAN/Ima/DBI.pm line 391.
>
>Removed the db file and it started just fine.

Hmm.. that's no good. It should have triggered an automatic rebuild.

Has anyone else had this happen to them?

-D
--
On second thought, let's not go to Camelot. It is a silly place.

kdf
2005-02-28, 11:10
Quoting Dan Sully <dan (AT) slimdevices (DOT) com>:

> * Michael Herger shaped the electrons to say...
>
> >When starting svn with the existing revision 2256 .slimserversql.db I get
> >the following error:
> >
> >DBD::SQLite::db prepare_cached failed: no such column: disc(1) at dbdimp.c
> >line 263 at /home/mh/eclipse/SVN/CPAN/Ima/DBI.pm line 391.
> >DBD::SQLite::db prepare_cached failed: no such column: disc(1) at dbdimp.c
> >line 263 at /home/mh/eclipse/SVN/CPAN/Ima/DBI.pm line 391.
> >
> >Removed the db file and it started just fine.
>
> Hmm.. that's no good. It should have triggered an automatic rebuild.
>
> Has anyone else had this happen to them?

sadly, I had already wiped mine to test/fix bug870 when I did the update. I had
forgotten that those changes had been made. Failing any other input, I'll try
to checkout an earlier version tonight and test it.

-kdf

Gregory Hamilton
2005-02-28, 11:48
It worked for me.


On Mon, 28 Feb 2005 10:10:45 -0800, kdf <slim-mail (AT) deane-freeman (DOT) com> wrote:
> Quoting Dan Sully <dan (AT) slimdevices (DOT) com>:
>
> > * Michael Herger shaped the electrons to say...
> >
> > >When starting svn with the existing revision 2256 .slimserversql.db I get
> > >the following error:
> > >
> > >DBD::SQLite::db prepare_cached failed: no such column: disc(1) at dbdimp.c
> > >line 263 at /home/mh/eclipse/SVN/CPAN/Ima/DBI.pm line 391.
> > >DBD::SQLite::db prepare_cached failed: no such column: disc(1) at dbdimp.c
> > >line 263 at /home/mh/eclipse/SVN/CPAN/Ima/DBI.pm line 391.
> > >
> > >Removed the db file and it started just fine.
> >
> > Hmm.. that's no good. It should have triggered an automatic rebuild.
> >
> > Has anyone else had this happen to them?
>
> sadly, I had already wiped mine to test/fix bug870 when I did the update. I had
> forgotten that those changes had been made. Failing any other input, I'll try
> to checkout an earlier version tonight and test it.
>
> -kdf
>

kdf
2005-02-28, 14:17
Quoting Dan Sully <dan (AT) slimdevices (DOT) com>:

> * Michael Herger shaped the electrons to say...
>
> >When starting svn with the existing revision 2256 .slimserversql.db I get
> >the following error:
> >
> >DBD::SQLite::db prepare_cached failed: no such column: disc(1) at dbdimp.c
> >line 263 at /home/mh/eclipse/SVN/CPAN/Ima/DBI.pm line 391.
> >DBD::SQLite::db prepare_cached failed: no such column: disc(1) at dbdimp.c
> >line 263 at /home/mh/eclipse/SVN/CPAN/Ima/DBI.pm line 391.
> >
> >Removed the db file and it started just fine.
>
> Hmm.. that's no good. It should have triggered an automatic rebuild.
>
> Has anyone else had this happen to them?

I just gave this a quick run at lunch break on a windows machine with a db from
last week. It gives the same error. --d_sql doesn't seem to get a chance to
give any output.

-kdf