|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius | Page:   1 2 3   |
|
|||||||||||||||
| Problem to localize DB - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator 
|
Hi Andrew, I implemented row id localization for SQL Server. The new feature is in 1.5.12 that will come out early next week. Thank you for your patience. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator
|
Hi Andrew, 1.5.12 is read to be downloaded http://www.sisulizer.com/downloads.shtml Best regards, Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
André Bitzer Member
|
Hi Jaakko, Thanks for the new release. Unfortunately, I could not find a way to specify the ID-Field and when I try to scan the database for changes I get this "Field '' not found"-ERROR. Any suggestions...? Best regards, Andrew
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator
|
Hi, Can you send me the SQL statement of your table(s) support (at) sisulizer.fi Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator
|
Thank you for the files. The reason was that the primary key in your table was uniqueidentifier. This is GUID. Current SL can handle only table having integer primary key. I will fix this in the next build. Jaakko Last edited on Tue Jun 19th, 2007 02:22 am by Jaakko.Salmenius ____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
André Bitzer Member
|
Hi Jaakko, Thank you. I'm looking forward to hearing from you. Best regards, Andrew
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator
|
Hi Andrew, I got this working now. The fix will be in the next build that comes tomorrow or Friday. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
André Bitzer Member
|
Hi Jaakko, First of all, Thanks for the new release. After all, I could test it and I'm happy with the new Tab (Properties - Items) since we have quite a few tables. Unfortunately, I still have problems. Please have a look at the screenshot. I'm missing my primary key for the table(s) and when I scan for changes Sisulizer responses with "Field not found". What am I doing wrong? Best regards, Andrew Attachment: MissingPrimaryKey.JPG (Downloaded 28 times)
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator
|
Right click fddfmdOid and choose Id field. This should work. I will make this automatic in 1.5.14 Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
André Bitzer Member
|
Hi Actually, fddfmdOid is not my primary key. This would be fddOid! fddfmdOid is the foreign key, I've metioned in one of my previous posts. Best, Andrew
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator
|
I noticed one bug. If you open existing slp and choose Properties from tree, SL does not remember you field setting when you use SQL Server. This is because SQL Server requires login (Access and other local do not). I will fix this in the next build (1.5.15) that will come next week. I can not fix this to today build but I implemented a new feature if you select a item that used to be an Id field to Language field, SL will automatically select the next possible and available field to Id field. Oh boy. This row id database localization method is pretty complex but not problem. I get it working smoothly. It just needs a bit more testing. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator
|
André Bitzer wrote: Actually, fddfmdOid is not my primary key. Yes. I know that. You don't have to select primary key. There can be only on primary key in the table and it is automatically used. This field having foreight key is called the Id field. In you case there are tro possible Id fields: 1) fddfmdOid (this is the one) 2) fddculOid (this is supposed to be the language field) However SL can not see that. By default is select the first possible field to be an ID file. In your case it is fddculOid. Thsi is why you have to set the fddculOid to be a Language field and set the fddfmdOid be to Id field. See the screen shot. Attachment: untitled.PNG (Downloaded 26 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
André Bitzer Member
|
Hi again, That's it. Looks much better!  The naming was a little bit missing leading. I assumed that I have to specifiy the primary key to be the "ID Field". But once more Sisulizer is smarter than expected and so far it works. I will test and give you a more detailed response as soon as possible. Great work. Best regards, Andrew
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator
|
I implemented auto login to SQL Server. Now the Database properties dialog keeps the existing settings. The new feature is in the next build (1.5.14) Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
André Bitzer Member
|
Hi Jaakko, I've had the time to test the new release and it looks fine for all the "normal" cases. Thanks! But in certain circumstances there is a row missing in the Insert-Statement (Seen in SQL Server Profiler). (Could not reproduce this, sorry. I'll keep an eye on it) And there exists a special case, that has to be handled in a different way. Sometimes we have two columns in a table which have to be localized independent. Lets call them "Description" and "Name". When I set both of this columns as a localizable fields in Sisulizer, I can't "Build" the Project anymore. The SQL Server Profiler shows me that Sisulizer handle the two fields independently and therefor sends two Insert Statements with just one of the columns set and since we have a "not null" constraint set, the statement fails. Even if not, what would be the expected result? In my opinion this could be handled in the GUI or the underlying Code: 1. GUI If more than one column in the same table are selected as localizable fields, Sisulizer shows them in one row and update them like that. (Maybe the simpler solution for you) 2. Code The GUI still separats the two columns but the Code merges the two "virtual" tables. (Important: Same "ID-Field"-Value and "Culture Field"-Value are the merging condition) What do you think? Thank you and have a nice day (even though this post won't help too much, sorry) Best regards, Andrew
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator
|
Hi Andrew, You are right. SL used separate insert statements. It was an accident, it was supposed to be single statement. I fixed this in 1.5.14. The old code worked just fine when I tested Access, Interbase, MySQL and SQL Server Express. I guess you use a full version of SQL Server that is stricker. Thank you for your report. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
André Bitzer Member
|
Hi Jaakko, Yes, I do. I've just striked an other idee to handle the "ID-Field". You could have this more general if one could choose for each field, which is not the culture-field, localizable or the primary key, what the default value should be. - For the "ID-Field" one would choose, "same as original" (default selection) - For a not localized "char"-field, a value from a textbox (this is optional, since this could be done easily by a SQL statement, select 'defaultvalue') - Or a value from a SQL-Statement Best regards. Andrew
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
André Bitzer Member
|
Hi Jaakko, I've just came across an other problem. If I have a table with two localized fields, one of them "looses" its empty rows when I build the project. After a new scan they appear again. Best regards. Andrew Last edited on Mon Jul 2nd, 2007 04:13 pm by André Bitzer |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
André Bitzer Member
|
Hi Jaakko, On the settings tab for a database source, one can specify the behaviour for the case of a not complete row. Unfortunately, I have to specify this for different tables differently. Maybe, this could be done an the properties tab for a table. What do you think? Best regards. Andrew
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator
|
Hi Andrew, What do you mean by empty row? On the settings tab for a database source, one can specify the behaviour for the case of a not complete row. Unfortunately, I have to specify this for different tables differently. Maybe, this could be done an the properties tab for a table. What do you think? Yes. I will implement this. I leave the settings in the source but you can override this table by table. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 10:21 am | Page: 1 2 3 |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Problem to localize DB | |
Sisulizer software localization tool - Three simple steps to localize
