Hi Tom,
The answer was ment to be the second last line of my previous message:
> The database was initially created on v.3.9.1 and extended by 2 columns
with wee_database under 4.0.0b6.
Was this th information you were asking for?
I'll take a look at the new type of extension in the meantime...
Thanks a lot,
Bernhard :-)
PS: sorry for accidentially answering by email previously...
Am Dienstag, 11. Februar 2020 17:36:52 UTC+1 schrieb Tom Keffer:
>
> V4.0 introduces a new way to specify a schema, although the old way is
> still supported.
>
> The "wview" schema uses the old way.
>
> The "wview_extended" schema uses the new way. How to extend it is
> documented in the new version of the customizing guide. See the section
> "Adding a new type to the database".
>
> You used an old-style addition on the new-style schema wview_extended.
> That's why it didn't work.
>
> But, you didn't answer my question. Did you create the new database using
> V4.0.0b11, or an earlier version, which, perhaps, contained the bug?
>
> Cheers,
>
> -tk
>
>
> On Tue, Feb 11, 2020 at 8:28 AM Bernhard R. <bernh...@gmail.com
> <javascript:>> wrote:
>
>> Hi Tom,
>>
>> I redefined the schema in a user extension (user.sunduration) like this:
>> *schema_with_sunshine_time* = schemas.wview.schema + [('sunshine_time',
>> 'REAL')] + [('sunshine_int', 'INTEGER')]
>>
>> and use this schema in weewx.conf:
>> # The schema defines the structure of the database.
>> # It is *only* used when the database is created.
>> ##### schema = schemas.wview_extended.schema
>> schema = user.sunduration.*schema_with_sunshine_time*
>>
>> When I now naively try to redefine the extended schema (following the
>> defaults) in my user extension like that
>>
>> import schemas.wview_extended
>> schema_with_sunshine_time = schemas.wview_extended.schema +
>> [('sunshine_time', 'REAL')] + [('sunshine_int', 'INTEGER')]
>>
>> wee_database would fail with error:
>>
>> TypeError: unsupported operand type(s) for +: 'dict' and 'list'
>>
>>
>> The database was initially created on v.3.9.1 and extended by 2 columns
>> with wee_database under 4.0.0b6.
>>
>> Does this narrow it down a bit, is there some additional info I can
>> supply, to help tracinf this?
>>
>> Thanks for all your efforts so far,
>>
>> Bernhard :-)
>>
>>
>> Am Montag, 10. Februar 2020 23:52:09 UTC+1 schrieb Tom Keffer:
>>>
>>> Hmmm, I thought this was fixed in commit
>>> https://github.com/weewx/weewx/commit/ba096b752493134442b222c5c4fa4b49bcef1d84,
>>>
>>> now four months ago. Have you generated the new database using V4.0.0b11,
>>> or an earlier version, which, perhaps, contained the bug?
>>>
>>> Also, can you take a look in your weewx.conf and see what type of schema
>>> you have? This will look something like:
>>>
>>> [DataBindings]
>>>
>>> [[wx_binding]]
>>> ...
>>> # The schema defines the structure of the database.
>>> # It is *only* used when the database is created.
>>> schema = schemas.wview_extended.schema
>>>
>>>
>>>
>>> On Mon, Feb 10, 2020 at 10:33 AM Bernhard R. <bernh...@gmail.com> wrote:
>>>
>>>> Hi there,
>>>>
>>>> I guess, I stumbled over a regression somewhere between 4.0.0b6 and
>>>> 4.0.0b11.
>>>>
>>>> if I do
>>>> wee_database /etc/weewx/weewx.conf --drop-daily
>>>> and afterwards
>>>> wee_database /etc/weewx/weewx.conf --rebuild-daily
>>>>
>>>> then table *archive_day_wind* is NOT created anymore when using weewx
>>>> 4.0.0.b11
>>>> also letting weewx create the statistics upon start (after dropping
>>>> them once again) will not create this table either.
>>>>
>>>> However, the table still seems to be referenced by the included default
>>>> skins, resulting in errors upon cheetahgenerator runs.
>>>>
>>>> When I revert to version 4.0.0b6 and repeat the process, the table
>>>> archive_day_wind is created just fine.
>>>>
>>>> Is this intentional (and the skin templates need to be adjusted
>>>> accodingly) or is this a regression?
>>>>
>>>> anyways, Thanks for the great work done so far,
>>>>
>>>> Bernhard :-)
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "weewx-development" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to weewx-de...@googlegroups.com.
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/weewx-development/b245c089-33f8-45ac-bf5e-80f3ed62c75e%40googlegroups.com
>>>>
>>>> <https://groups.google.com/d/msgid/weewx-development/b245c089-33f8-45ac-bf5e-80f3ed62c75e%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>> --
>> You received this message because you are subscribed to the Google Groups
>> "weewx-development" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to weewx-de...@googlegroups.com <javascript:>.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-development/e916b4b8-17dc-44e7-986c-d773cedf5183%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/weewx-development/e916b4b8-17dc-44e7-986c-d773cedf5183%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>
--
You received this message because you are subscribed to the Google Groups
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to weewx-development+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-development/6c91272a-0553-4c3d-bb88-73b85a001d76%40googlegroups.com.
