Re: More 1.8 stuff

> It seems neither make install nor datagard creates /etc/midgard/conf.d:

Yes, I was to add this today but I am a bit confused.

midgard-data or midgard-core?
Creating conf.d and schema dir in core adds a bit of pain for binary packages.
On the other hand creating these dirs with midgard-data while you want to use only
midgard-schema for example doesn't make sense at all.

So , I see one of these two solutions:

1. Create these dirs in core and force binary packages to have additional
package like midgard-tools.
2. Move all command line tools to midgard-data.

> #2  0x404fd02a in midgard_schema_lookup_member_property
> (schema=0x8091f37, type=0x8091f70 "\034", field=0x405100df "dbtype",
> prop=0x405100df "dbtype") at src/mgdschema.c:244
> #3  0x40506b06 in midgard_object_create_storage (object=0x809c3d8) at
> src/query.c:340

That's my fault. I dropped almost all midgard_schema_lookup_xxx in favour
of midgard reflection.

Will be fixed monday at noon ;)

> My configfile "local" looks like this:
> Type=Mysql
> Host=
> Name=midgard
> Username=midgard
> Password=midgard
> Encoding=utf-8
> Blobdir=/opt/lampp/var/lib/midgard/blobs/midgard/
> Schema=
> Logfile=/opt/lampp/logs/midgard.log
> #Loglevel=message
> Dbcreate=yes
> Dbupdate=yes

I do not recommend dbupdate to be set to true. As long as you do not have database
backup. I am not sure if MgdObjects schema define any non standard dbtypes.

Piotras