Re: [Websyntax-core] Syntax Datatypes, Relationships dropdown and Context problems

[Adrian C. <ad...@da...>]

Hi Nyk, Sandy, core,

Thanks very much for getting back to me.

Re our problem with deleted datatypes reappearing: I've looked through our
data objects and our db fields and there's no mention of the offending
datatype that I could find.

Re our problem with the relationships dropdown not appearing when it should
in dbasis: We have updated from CVS in the past few days and have also
checked the typesfield table and it uses 'is_unique' not just 'unique'.

Re our problem with Context login not working: Context has also been updated
from CVS.

Can you suggest other ways we can try to isolate and correct these problems
other than deleting and reinstalling it all again?

Regards,

Adrian

Regards,

Adrian



----- Original Message -----
From: "Nyk Cowham" <nc...@fo...>
To: "Adrian Columb" <ed...@da...>
Cc: "Randum Ian" <ia...@ra...>; "Websyntax-Core@Lists. Sourceforge.
Net" <web...@li...>
Sent: Wednesday, 14 May 2003 8:39
Subject: RE: [Websyntax-core] Syntax Datatypes, Relationships dropdown and
Context problems


> > > > Firstly, when I log in to dbasis, then go to 'data', then select
> > > > 'organisation' from
> > > > the dropdown menu, then click 'add record' I get the following
error:
> > > >
> > > > Fatal error: mysql error: [1146: Table 'pxdb.organisationtypes'
doesn't
> > > > exist] in EXECUTE("SHOW COLUMNS FROM organisationtypes") in
> > > > /home/danceportal/www/dbasis/includes/errorhandler.inc.php on line
77
> > > >
> > > > That error reffers to the 'organisationtypes' datatype that I had
> > > > previously created in the datatypes section of dbasis, and then
> > subsequently
> > > > deleted when I realised it wasn't needed. Should allow us to delete
> > > > datatypes without it getting messed up like that? How can we fix it
when
> > it
> > > > does?
> > >
> > > Normatively it should delete all references to a table that has been
> > deleted, but positively it probably isn't doing that currently.
> > > Anyhoo, you need to remove any reference to the deleted table from
your
> > datatype definition (you probably have a field defined that
> > > is using that table - or maybe it is a field defined in dbfields.
> >
> > As we don't fully understand fully how the database works we'd rather
not
> > mess with it on that level. Can that be fixed so it deletes the
correclty?
>
> It is wise not to try modify the database directly. It is not a big
priority for me to fix usability issues with DBasis simply
> because it is planned for a complete rewrite as a desktop client app. In
the meantime, it is incumbent on the developer to make sure
> that objects do not contain links to pick tables that have been deleted.
>
> > > > Secondly, when I go to the 'objects' section and try to create a
field
> > in a
> > > > datatype in that is a relationship, the relationships dropdown menu
> > doesn't
> > > > display the list of relationship types (which are defined in the
> > > > Relationships section of dbasis) However, when I try to edit one of
the
> > > > fileds that is predefined as a relationship the dropdown list of
> > > > Relationships shows up just fine.
> > >
> > > This seems to be a new bug that has formed. Probably something to do
with
> > session persistance. I will put it in the bug tracker.
> >
> > Cool - can you tell me roughly when do you think that wll be fixed?
>
> Actually I spoke too soon - it turns out it isn't a bug at all. I
replicated the problem on a site I had recently upgraded, but I
> realized that I hadn't upgraded DBasis from the CVS too. This problem
should go away if you update DBasis from CVS. This is due to a
> change in the database schema (renaming the typesfields.unique attribute
to typesfields.is_unique). PxDB, DBasis and Context should
> all be updated from CVS to be compatible with each other.
>
> thanks to Sandy for helping to clarify this!
>
> > > > Thirdly, we can't log in to context with the default
username/password
> > > > details even though we haven't changed the details.
> > >
> > > Don't know why that should happen. Seems fine on the new instances
that I
> > have installed recently.
> >
> > It doesn't work for us, though it did work previously.
>
> Again, I think you need to update Context from CVS to be compatible with
the new API files (PxDB).
>
> > Please keep me updated if you have any new info about these problems.
> >
> > Regards,
> >
> > Adrian
> >
> > >
> > > Nyk Cowham, Systems Architect
> > > Forum One Communications
> > > http://www.forumone.com/
> > > Communicate Collaborate Change the world
> > >
> > >
> >
> >
>
>