My operation steps:
Change a table's PK from column A to column B, where A's directus_fields.special = uuid, and B is also a FK.
Drop column A.
Remove all records related to column A in Directus meta tables, like directus_fields.
Restart Directus.
In Directus GUI, navigate to the table and click on one row.
The "Page not found" error shows up, but no error in console where Directus is running.
Could anyone give me some hints about where could go wrong?
Thanks!
This doesn't exactly look like a stack overflow question, but sounds like it should be a bug report on the repository.
Related
I have imported data table to my cytoscape map for the following continuous mapping accorging to values. After some time, I have imported another data table and then deleted the previous one. The original data are not present in either the node or edge table but I still can see the names of the original columns when selecting column for continuous mapping i. g. for size or colour. Moreover, this warning appears: "The current table does not have the selected column. Please select another column." Do you know how to solve this so that I no longer see the names when these columns are not even in the table?
I would be grateful for any ideas.
I have tried to delete the data table and import the data again but it didn't help. I have also tried to clone current network and import data to the new map, but the old names are still present in the column selection.
Do you know how to solve this so that I no longer see the names when these columns are not even in the table?
I would be grateful for any ideas.
A couple points and then a couple suggestions:
The style is going to "remember" the selected column name, even if you delete it since it doesn't know what to change it to. It will add a warning icon mentioning that the column is missing. You have to choose a new column (or reload the missing column) to address that issue. [I think you know this already, but just stating for completeness :)]
The pulldown list of column names should be updated when you delete table columns. This does indeed sound like a bug.
Are you running the latest Cytoscape 3.9.1?
Have you tried selecting another style and then returning back to this style? That might "refresh" the column name list.
Have you tried saving/restoring the session?
I am using SQL Server and for some reason when I added a record it does not show up in the database. It has skipped the number and has saved the information somewhere but I am unable to view it in the table. If I use the login and password everything still works. Why would this happen? Now that I add another record it has moved on to the next number but for some reason row 73 does not show but is stored. Can anyone tell me what causes this or why it may happen when it still is using all the information from what was entered correctly.
Since you find your row when searching by id it must be there.
In edit mode the table is not always displayed in order of the ids but by in order of insertion of rows. I experienced this problem myself just like you. Then I queried with "ORDER BY ID" and found everything in place.
Hope that helps anybody experiencing the same problem when using the GUI.
I know this is a repost, I have done my research on everything possible and I couldn't find anything to assist nor help me with my current problem. No matter how many times I re-create my Query or Form, I just can't seem to get it to work correctly. if I run my Query, I will get the correct information displayed, but when it comes to adding information through a custom form I made, I get this error -> "cannot add records join key of table not in recordset".
My current Query, incase you wanted to see. I only access vendorNoID from the vendor table. I require all the information from the rest of the tables.
I am able to enter information in this form for tbl_address and tbl_addressType, but I get the error for vendor / purchaseOrder. Any reason whats causing this?!?!
Any advice will be greatly appreciated
The selected value of the vendor combobox got to be bound to [tbl_purchase_order].[vendorID]. To the table, where the selected value is the foreign key.
It's got to be the same as you already did with the address_typeID.
The selected value of the vendor combobox got to be bound to [tbl_purchase_order].[vendorID]. To the table, where the selected value is the foreign key. (#VMai)
In my opinion, open the Query Builder of Form (as picture below), then add column [tbl_purchase_order].[vendorID]
/
Cause I don't have enought reputation for write comment, so I write down here.
Hope it help ! ^^
I was hoping someone out there may have experienced this before.
I have a database that (as far as I'm aware) is in perfect working order. I have no problems with it whatsoever. I'm trying to add a column to some of the tables but when I save the changes I get the following message
This error message is then stuck in a loop and the only thing I can do is kill the SQL Management Studio process.
The database exists, the table exists, I can run any query I want against it, I just can't make any changes to it.
The steps I'm taking are:
Right click table
Select "design"
Right click "add new column" in designer
Fill in the details as normal
Click Save
Anyone know how I can resolve this?
Thanks.
It's telling you that you haven't specified the name of the table. The name of the table should be between the two single quotes.
Without knowing how you're doing this it's hard to tell more, but the first two possibilities off the top of my head are:
If you're looping through tables in code to do something, you may be hitting a record with no table name.
If it's pure SQL, perhaps an error in your syntax
EDIT: Please read my answer below first, before you decide to read and try to understand the text below. You may not find it's worth it when you see what was going on ;)
I have a weird problem: SQL Server 2008 R2 keeps complaining about an invalid column that is indeed not there anymore, but I'm not using it either!
I can't update any rows in that table anymore from within my own application, where no reference to the column can be found, because I always get this error now.
I then wanted to update straight in SSMS as a test, but when I edit the rows there, I still get this error.
What happened before: I made a column called CertcUL varchar(1), and that worked. After a while it appeared I needed it to be a varchar(30), so I edited the table design and turned it into a varchar(30).
From that moment I saw that I could only update this column when I stored 1 character. When I tried to store more, I got an error warning me about string or binary truncation. So somehow, the previous varchar(1) info was still present in the DB.
When I renamed that column to CertcUL2 or Cert_cUL, the same things kept happening! So changing the column name does not change the underlying cause. Also when just trying to add some characters straight in SSMS.
When I deleted the column, and added a new one with varchar(30) straight away, and called 'test', the same problem remained! This column still only allows me to store one character! The column was the one but last column. Making it the last column does not help either. Only when creating an new column while keeping the other column, I can have columns that behave properly.
So somehow, SQL Server saves some meta data about a column, even when it has been deleted. And does not look at the name, but rather at the order in which the columns are created.
Does anyone have an idea how this can happen, and how I can fix this besides (probably) dropping and recreating the whole table?
Thanks!
Oh my God I feel so stupid...it's a trigger that still contains this column. I just noticed it because when trying to update with an update statement. Only this way I got a proper error message, so I now know what's going on. So stupid that I didn't check the triggers! Sorry about that!
More info: I had an update trigger on this table A, that copies all current values to a history table B that contains the same columns. So I did change the length of the column CertcUL in table A, but forgot about table B. So it was very confusing to see the old column name popping up every time, and see it complianing about string truncation while my column in table A seemed just fine.
Sorry again :)