Re: MidCOM and its further adaption to new Midgard versions - AKA Midgard core quality
Henri Bergius <henri.bergius-ZpG/[email protected]> Mon, 13 Feb 2006 14:25:38 +0200
| Newsgroups | gmane.comp.web.midgard.devel |
|---|---|
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Feb 13, 2006, at 12:08, Piotras wrote: > As above , it only exists in 1.7.3 > 1.7.4 is postponed due to not confirmed (100%) issue with midcom's > root topic and prefix. The bug about the prefix problem in MidCOM is still marked "new": http://midcom.tigris.org/issues/show_bug.cgi?id=357 > I need to change internal TIMESTAMP type which is DATETIME in fact > anyway. Wouldn't the simple solution here be to use "int" as field type in MgdSchemas in the cases where components would just want to use timestamps instead of full datetimes? > Piotras /Bergie Henri Bergius Consultant Partner, Nemein henri.bergius-ZpG/[email protected] Midgard CMS www.midgard-project.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFD8HrCNkT8k497k9IRAn9tAJwOkgau5yBJ+h7/BqHy/D0N8kt8LwCfXiK2 PT03ZzYDcSfl5Fm2B413VqM= =Lkga -----END PGP SIGNATURE-----