and the table ‘was not there’ because it was created within a transaction that
was rolled back because of the error
> On 2 May 2021, at 2:23 pm, Graham Eddy wrote:
>
> found it: duplicate entry in user.extensions.gw1000_schema
>
> i was under the impression that that schema was used only when
found it: duplicate entry in user.extensions.gw1000_schema
i was under the impression that that schema was used only when the database is
created, but that is incorrect: the schema is also used in —rebuild-daily
> On 2 May 2021, at 12:28 pm, Graham Eddy wrote:
>
> my weewx-gw1000.conf
i don’t know how to reproduce it (so many changes, as vince pointed out). i was
hoping someone had seen it before: maybe a default value going astray
it is worth a first-pass inspection, but no more than that if i can’t reproduce
it or not seen elsewhere. summary of problem statement would be
It's a new feature, so there may well be a problem. Unfortunately (or,
maybe fortunately!) I am unable to replicate it. I dropped a couple
columns, renamed a column, then dropped the daily summary. I then rebuilt
it uneventfully.
If you can walk me through an example, maybe I can replicate your
> You are changing so much
i am trying a different split of data between two drivers (one database into
two), where both have data in columns in one database
> (why ?)
you don’t jump a gap in two hops
> in a seemingly random order
the sequence is logical to me: make a copy for second driver,
On Saturday, May 1, 2021 at 8:24:12 AM UTC-7 graha...@gmail.com wrote:
> * i copied producton weewx.sdb to dev/test (different host)
> weewx-gw1000.sdb,
> * in which i dropped lots of columns and renamed others (using
> wee_database —drop-columns and —rename-column respectively)
> * then i
