"In 200.000 years on Earth, humanity has upset the balance of the planet, estabilished by nearly four billion years of evolution. The price to pay is high, but it's too late to be a pessimist: humanity has barely ten years to reverse the trend, become aware of the full extent of its spoliation of the Earth's riches and change its patterns of consumption.
information_schema in MySQL 5.x gives you the opportunity to dig into the database metadata. Unfortunately it's slow like hell. I've attempted to write a query that returns all foreign keys that have no index defined on their columns. It seems that information_schema needs a lot more tuning, because my query results in the following error message:#126 - Incorrect key file for table '/mnt/mysql-tmp/#sql_969_2.MYI'; try to repair itLAST_UPD date column that contains the date of last modification for a given record. Using this you can easily write a procedure to look for tables/records that have changed since a specific date (or in the last "n" minutes). Thus you can find out for every operation available in Siebel Tools the tables it involves. Eg. you can edit the web layout of an applet, save the changes and then query the list of tables that contain records updated in the last 1-2 minutes to see where are the layout settings stored. You can apply the same method for any operations via the user interface (like adding/modifying a new contact, an employee, etc.).
notify-osd package was installed indeed (so far so good), but the old notification-daemon was still left behind and apparently if both are installed, notification-daemon is picked by Ubuntu to be used. Uninstalling the latter left only notify-osd which resulted in the appearance of the new notification bubbles. Now that I know we can choose which one to use, I'll leave it up to the users (my colleagues) to decide. If you happen to know how to set/change the order of preference in case both daemons are installed, please share your knowledge in a comment.@Table parameter and the rowid of the record in the @Rowid parameter) by going through all the foreign keys that are pointing to the specified table and executing a query to get the count of referring records. Since this is a Transact SQL code snippet, it suggests you're running Siebel CRM on a Microsoft SQL Server (which is not the typical case ... but occurs anyway as it did with one of the clients of my company). 
Recent comments
1 day 11 hours ago
1 week 11 hours ago
1 week 4 days ago
1 week 4 days ago
2 weeks 1 day ago
2 weeks 2 days ago
2 weeks 2 days ago
2 weeks 2 days ago
2 weeks 3 days ago
2 weeks 6 days ago