On 10/26/05, Michael T. Dean <[EMAIL PROTECTED]> wrote:
> Byron Poland wrote:
>
> >I had to compile from SVN to get the protocol on my
> >frontend (ubuntu) (Which I also use as a slave backend to commflag and
> >transcode) to match up with the backend (knoppmyth R5A22) so they
> >very well could b
Byron Poland wrote:
I had to compile from SVN to get the protocol on my
frontend (ubuntu) (Which I also use as a slave backend to commflag and
transcode) to match up with the backend (knoppmyth R5A22) so they
very well could be different versions. I just located the source for
the knoppmyth ve
Bruce Markey wrote:
Byron Poland wrote:
On 10/26/05, Michael T. Dean <[EMAIL PROTECTED]> wrote:
Byron Poland wrote:
On 10/26/05, Michael T. Dean <[EMAIL PROTECTED]> wrote:
Byron Poland wrote:
Here is the relevant part of my backend log on on startup:
2005-10-26 15:02:15.804 Using runt
On 10/26/05, Bruce Markey <[EMAIL PROTECTED]> wrote:
> Byron Poland wrote:
> > On 10/26/05, Michael T. Dean <[EMAIL PROTECTED]> wrote:
> >> Byron Poland wrote:
> >>
> >>> On 10/26/05, Michael T. Dean <[EMAIL PROTECTED]> wrote:
> >>>
> >>>
> Byron Poland wrote:
>
> > Here is the releva
Byron Poland wrote:
On 10/26/05, Michael T. Dean <[EMAIL PROTECTED]> wrote:
Byron Poland wrote:
On 10/26/05, Michael T. Dean <[EMAIL PROTECTED]> wrote:
Byron Poland wrote:
Here is the relevant part of my backend log on on startup:
2005-10-26 15:02:15.804 Using runtime prefix = /usr
QSett
On 10/26/05, Michael T. Dean <[EMAIL PROTECTED]> wrote:
> Byron Poland wrote:
>
> >On 10/26/05, Michael T. Dean <[EMAIL PROTECTED]> wrote:
> >
> >
> >>Byron Poland wrote:
> >>
> >>>Here is the relevant part of my backend log on on startup:
> >>>
> >>>2005-10-26 15:02:15.804 Using runtime prefix = /
Byron Poland wrote:
On 10/26/05, Michael T. Dean <[EMAIL PROTECTED]> wrote:
Byron Poland wrote:
Here is the relevant part of my backend log on on startup:
2005-10-26 15:02:15.804 Using runtime prefix = /usr
QSettings::sync: filename is null/empty
2005-10-26 15:02:15.953 New DB connection,
On 10/26/05, Michael T. Dean <[EMAIL PROTECTED]> wrote:
> Byron Poland wrote:
>
> >Here is the relevant part of my backend log on on startup:
> >
> >2005-10-26 15:02:15.804 Using runtime prefix = /usr
> >QSettings::sync: filename is null/empty
> >2005-10-26 15:02:15.953 New DB connection, total: 1
Byron Poland wrote:
Here is the relevant part of my backend log on on startup:
2005-10-26 15:02:15.804 Using runtime prefix = /usr
QSettings::sync: filename is null/empty
2005-10-26 15:02:15.953 New DB connection, total: 1
2005-10-26 15:02:15.991 Setting Lock for Database Schema upgrade. If
you
On 10/26/05, Kevin Kuphal <[EMAIL PROTECTED]> wrote:
> Michael T. Dean wrote:
>
> > Kevin Kuphal wrote:
> >
> >> Sounds like a DB update was missed. If you do not have the basename
> >> field in your DB, execute this SQL statement against it:
> >>
> >> ALTER TABLE recorded ADD COLUMN basename varc
Michael T. Dean wrote:
Kevin Kuphal wrote:
Sounds like a DB update was missed. If you do not have the basename
field in your DB, execute this SQL statement against it:
ALTER TABLE recorded ADD COLUMN basename varchar(128) NOT NULL DEFAULT;
and then, once it is in your database, run this:
On 10/26/05, Michael T. Dean <[EMAIL PROTECTED]> wrote:
> Byron Poland wrote:
>
> >On 10/26/05, Kevin Kuphal <[EMAIL PROTECTED]> wrote:
> >
> >
> >>Byron Poland wrote:
> >>
> >>
> >>
> >>>Since upgrading my backend to Knoppmyth R5A22, all of the recordings
> >>>I've made are missing the basename, p
Byron Poland wrote:
On 10/26/05, Kevin Kuphal <[EMAIL PROTECTED]> wrote:
Byron Poland wrote:
Since upgrading my backend to Knoppmyth R5A22, all of the recordings
I've made are missing the basename, progstart, and progend fields (ie
they are blank). this causes jobs like commercial fl
Kevin Kuphal wrote:
Sounds like a DB update was missed. If you do not have the basename
field in your DB, execute this SQL statement against it:
ALTER TABLE recorded ADD COLUMN basename varchar(128) NOT NULL DEFAULT;
and then, once it is in your database, run this:
UPDATE recorded SET basen
On 10/26/05, Kevin Kuphal <[EMAIL PROTECTED]> wrote:
> Byron Poland wrote:
>
> >Since upgrading my backend to Knoppmyth R5A22, all of the recordings
> >I've made are missing the basename, progstart, and progend fields (ie
> >they are blank). this causes jobs like commercial flagging to fail.
> >If
Byron Poland wrote:
Since upgrading my backend to Knoppmyth R5A22, all of the recordings
I've made are missing the basename, progstart, and progend fields (ie
they are blank). this causes jobs like commercial flagging to fail.
If I fill in the missing data manually into the tables, things work
16 matches
Mail list logo
