Search Results

Search found 49789 results on 1992 pages for 'mysql insert id'.

Page 6/1992 | < Previous Page | 2 3 4 5 6 7 8 9 10 11 12 13  | Next Page >

• SQL Server giving a weird conversion error

  - by codingguy3000

  Hello Everyone I'm stuck and any help you can give me is greatly appreciated. create table stackoverflow_rules(myguid uniqueidentifier primary key, myvarchar50 varchar(50)) insert into stackoverflow_rules(myguid, myvarchar50) values('27C4CF31-2C4C-4C78-BBDC-2D0FDAA891CF','9985276') insert into stackoverflow_rules(myguid, myvarchar50) values('6F865BBD-1D79-4931-BCFE-71AD7A14B145','9985275') insert into stackoverflow_rules(myguid, myvarchar50) values('C91124D9-CE83-44C6-A979-427858BBCDCE','9985274') insert into stackoverflow_rules(myguid, myvarchar50) values('18D89F3C-D15D-4A27-9695-CE4417A9D752','9985273') insert into stackoverflow_rules(myguid, myvarchar50) values('40C9A127-D50D-440C-A6BF-A3C292B56121','9985272') insert into stackoverflow_rules(myguid, myvarchar50) values('3191CE74-6443-4DF0-ABFB-4083150E27A7','9985271') insert into stackoverflow_rules(myguid, myvarchar50) values('489606B3-8EE8-4308-BD3B-660FEC999B84','9985270') insert into stackoverflow_rules(myguid, myvarchar50) values('7FB986D6-7ACF-4453-B124-E688514D3A84','9985269') insert into stackoverflow_rules(myguid, myvarchar50) values('2E1662CB-FBC2-418A-9FFD-453895EE6FA4','9985268') insert into stackoverflow_rules(myguid, myvarchar50) values('6180E683-AA19-4B5D-9AA1-370B9AA8C156','9985267') insert into stackoverflow_rules(myguid, myvarchar50) values('39BDD429-4C49-4351-951F-016B89E700D0','9985267') insert into stackoverflow_rules(myguid, myvarchar50) values('9A09CF26-B168-48D2-9178-EBBD6C0BA5F4','9985267') insert into stackoverflow_rules(myguid, myvarchar50) values('56BA06A7-71F6-4AC2-817A-69A3E800BE54','9985266') insert into stackoverflow_rules(myguid, myvarchar50) values('35D8C2FE-4793-40BC-AECA-10AA722866AE','9985265') insert into stackoverflow_rules(myguid, myvarchar50) values('84162588-D2A2-4B67-869D-2D7A0CB3ABEC','9985264') insert into stackoverflow_rules(myguid, myvarchar50) values('05A8BE08-B0CF-4ADC-A901-2DB6B70713DA','9985263') insert into stackoverflow_rules(myguid, myvarchar50) values('11E1B3F5-5EC0-43BF-B868-B30BCC5F97B3','9985262') insert into stackoverflow_rules(myguid, myvarchar50) values('D48875E9-4A2B-4A5E-8C3A-6788ADD2E44E','9985261') insert into stackoverflow_rules(myguid, myvarchar50) values('5C29D799-5F86-4B5D-8B31-1AFB9E289417','9985260') insert into stackoverflow_rules(myguid, myvarchar50) values('3FAF4D60-F06A-4754-A26F-61DE6A121E9E','9985259') insert into stackoverflow_rules(myguid, myvarchar50) values('4F001BF6-BF60-4F40-AAE1-32CD707E87F8','9985258') insert into stackoverflow_rules(myguid, myvarchar50) values('56A91F39-F9D2-438C-A424-F26ED799F723','9985258') insert into stackoverflow_rules(myguid, myvarchar50) values('F55F72CA-0C2B-4DE7-B725-C9521CD57B23','9985257') insert into stackoverflow_rules(myguid, myvarchar50) values('364808A7-46E6-4639-A14D-6A350A56D2A0','9985256') insert into stackoverflow_rules(myguid, myvarchar50) values('68FA5B18-BBE3-4F1F-A9DE-D46853AD5D4A','9985255') insert into stackoverflow_rules(myguid, myvarchar50) values('B0118D37-807A-4D29-9B56-790F3D810C64','9985254') insert into stackoverflow_rules(myguid, myvarchar50) values('E998F33E-F05A-4C49-8CC2-B90BCFA9AE0E','9985253') insert into stackoverflow_rules(myguid, myvarchar50) values('A0531477-335C-4A7D-A1E7-1DAD54ECB7AD','9985252') insert into stackoverflow_rules(myguid, myvarchar50) values('96540D09-BA49-413B-9FD6-228DF524BE1A','9985251') insert into stackoverflow_rules(myguid, myvarchar50) values('23CD3C18-DAE2-463B-B27C-977488DF9C5F','9985251') insert into stackoverflow_rules(myguid, myvarchar50) values('8BF4AE7D-0AF0-47F9-9388-A2D4CA4C3160','9985250') insert into stackoverflow_rules(myguid, myvarchar50) values('E1892F4D-471C-4A49-8D68-F9F1E6E9C275','9985249') insert into stackoverflow_rules(myguid, myvarchar50) values('641A62CC-1DEE-4DFD-BC9A-DD47D7C45B18','9985248') insert into stackoverflow_rules(myguid, myvarchar50) values('3AF2F7CA-489D-4A79-A6F5-DB5578F381D0','9985247') insert into stackoverflow_rules(myguid, myvarchar50) values('939B3773-BE13-483C-A27F-5594A23AB6F2','9985247') insert into stackoverflow_rules(myguid, myvarchar50) values('81A5FD90-1E2D-4DB5-A10F-5624A576D566','9985247') insert into stackoverflow_rules(myguid, myvarchar50) values('E87109DD-7283-4B60-AB7F-F9A3DD384E52','9985247') insert into stackoverflow_rules(myguid, myvarchar50) values('689A789F-0FFC-45AE-87DF-66C5130338E2','9985246') insert into stackoverflow_rules(myguid, myvarchar50) values('4A9D3A2D-940B-4D45-8234-A1C98FF8A2FB','9985246') insert into stackoverflow_rules(myguid, myvarchar50) values('75073565-E623-40FC-AEF3-81620F2514A8','9985245') insert into stackoverflow_rules(myguid, myvarchar50) values('DB583FF8-1635-47C1-8241-D37C015C7642','9985244') insert into stackoverflow_rules(myguid, myvarchar50) values('39EA148B-55D1-4878-925A-39FA8592F451','9985243') insert into stackoverflow_rules(myguid, myvarchar50) values('BF1CE2D7-ABD3-460B-A7DC-BD0E2B2A5388','9985242') insert into stackoverflow_rules(myguid, myvarchar50) values('B6431717-26F0-436E-9DCC-C0C5240AC329','9985242') insert into stackoverflow_rules(myguid, myvarchar50) values('4F22E672-6F3D-454C-ABA7-D9B84D12DDE0','9985241') insert into stackoverflow_rules(myguid, myvarchar50) values('0436E893-DC43-4FF7-8BDC-BD0BF9E9A55D','9985240') insert into stackoverflow_rules(myguid, myvarchar50) values('60B2FE73-3575-4047-B324-63620FEACD6B','9985239') insert into stackoverflow_rules(myguid, myvarchar50) values('2041E1E5-F60F-4494-A000-F349F49662EC','9985238') insert into stackoverflow_rules(myguid, myvarchar50) values('B89636C8-4648-4058-8DC6-95DCE468CA63','9985237') insert into stackoverflow_rules(myguid, myvarchar50) values('4EC1B486-1E9C-4B41-94C1-5B24471BAD3D','9985236') insert into stackoverflow_rules(myguid, myvarchar50) values('4C86120E-1A27-4F59-948B-F11D8ACD498E','9985234') insert into stackoverflow_rules(myguid, myvarchar50) values('E8A1EA7A-5337-4769-9D23-25F7BFB589AF','9985217') insert into stackoverflow_rules(myguid, myvarchar50) values('6E7982F0-5899-4214-A05A-262E05A540CB','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('C55B838F-FD63-40E9-97AF-25E02A37ABB7','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('95296596-ED86-4A88-8C46-27CF79D4AFB9','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('149BC6CC-857C-4CD7-B374-29EE6382CFCF','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('5D3E88FC-1DB5-4BAF-A16B-29F2A2C7D997','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('1FDB6AD4-3860-411E-A247-22B9D00C9053','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('83BD156B-C5ED-460E-95F0-21E8B4254BF8','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('2FD09C37-E224-414D-8C41-220B6528EB9C','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('A46D0B0D-70E2-4AEF-BF30-2244FFA8EF9E','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('824B7F04-51B4-48F6-920A-1FDE8571E32F','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('79DD6034-A9DC-4AC1-9CD3-338F0521AC99','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('BFD35E07-C5DE-4C8B-ADC4-36069655F450','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('D655AD53-8107-481B-A1C9-340A7B31EFB6','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('7E6FF0E9-E1F4-4522-AB91-1A64C2AC0E3A','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('3A977BFE-17F6-46FA-8568-1A8ED2F48483','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('D95A941D-DEB3-46B5-8B2B-1AC9741824ED','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('55528060-12AE-4C2E-A4A1-11E40881DEAE','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('E99B4179-DE6E-4FCB-B7B9-165C05A94424','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('20D2D92B-E45A-4883-A114-109C41E2F278','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('7161CC4A-0B3E-4B97-A973-0C5A7F26CC0D','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('5E267539-8412-4423-A82C-0C74C995D561','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('AE173244-38CD-4B8D-A1CB-0DC112AC6F54','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('3ED8BF74-D0D1-4D11-92B3-008F11E34308','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('6F77EAF9-0520-495A-ADB5-027F611E418D','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('34DAFFBC-0733-4EC0-8607-0287DA5929D6','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('5266FB2F-2829-4C60-91E7-00D9A0832B8E','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('A1EC9933-92F0-4805-93C2-071F503BE816','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('EC19E064-940A-4EEA-9A12-07D2A0680C03','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('7CA5F400-0E57-4A86-B4E1-094720E98B56','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('3A7F95B9-79B6-4323-B390-5B30AE23F66C','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('CCA677CB-8889-40E6-8FDC-54C33DCBAD93','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('345FACAF-90B2-4B2D-B6CF-577F242F28C9','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('20531AFD-21EB-4B75-B50C-5FEABDAE29DB','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('A8FF5B5F-7976-43FE-B013-67CEE5F07710','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('AEF6E39A-6CC2-48E8-9999-65D7CD103A45','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('8AB565EE-4A53-40B9-9D95-66034FD72B6D','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('B0DAC1F6-B7E0-476F-8543-6282203A72C7','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('DACE56ED-5964-44FD-9E35-68E3B409B2D7','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('C64F5A8A-1930-4824-9F0E-68EF848F2F86','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('38817195-BDB0-44AC-988D-690BE9E50FD0','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('BF4202D8-A23A-48DB-8799-694578EED45A','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('D26A3E39-EEA2-4928-82F9-676B3F901021','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('0D3F16C2-237A-4461-9851-6B0555EDADCE','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('F8CCEE52-A31D-4B6D-9F9F-6D53BE7EB919','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('BCE3146A-AACE-4CF5-ADF1-3D5E57827D96','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('5D6E4347-ABC8-4892-89EC-3FE666A8523B','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('8BD465A9-DC91-4960-BCC7-42EAEE51024A','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('54FCE80F-F551-4548-BCE2-4499AB66D93F','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('843C8651-A95D-458F-A6E7-488F5978FB56','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('4BE7BC8D-BC97-4F8F-85BB-48CC970B9465','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('6C611A14-11CC-454D-A9C8-48CF0B2776A9','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('50819781-F028-4976-A406-45D88804C566','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('1EE5DBE0-0EA3-4F9B-8C78-469D00888892','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('33B87A5D-CB69-4BD2-BEC8-4D90D6A21232','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('C31D7CD1-E9BA-4B03-BB11-4DE7022A45AD','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('2E1FC057-4C57-4C27-86E4-4EC887B77ABE','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('7811CF7B-2935-47A6-92CB-520C4E0AEC4A','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('2DAB5B2D-3D94-4F47-B7F5-536FAF08BCC6','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('2F405742-CF20-4995-84D3-976B108DBB99','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('2852C9C8-325D-4C82-837E-9D6E751B794F','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('40E87A07-DA9B-4277-90BB-8FA994470CB1','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('732DF392-C8D6-4EEF-B046-8FC6C0DB4DEC','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('AA55681E-FE4A-46E9-8809-928941C165AD','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('C146FDD8-EF42-48B4-A357-90CEE93FE902','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('A0FEAAAD-8B44-4797-BD1F-A34AC872EC39','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('A45F22EE-8740-4A3B-ABB5-A8F7EE32B107','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('1A073622-C5D6-41B0-BCC2-8220ED1978BA','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('C7CFCCDC-5ADF-4BCF-BBE4-7E6D611B96CC','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('A618A9A7-5DAC-4658-9B6F-7FC091C49122','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('0F698448-929F-4E3B-A6B1-810BF66DC9AD','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('2FD04ED9-AC24-4E80-8902-7AF2351DAB7B','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('2DA5D721-DFDD-4E96-9A5C-7DF7B0FA9ABB','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('76816CF3-FB2E-440D-91E7-7FF179CE2702','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('228A8BC4-D136-4FDA-B006-84FD69D583A0','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('838DCC6F-0C37-4144-9461-892F1DE2A0D4','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('E65DF83F-FDA5-4883-9E29-8CAB66297328','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('621547A3-613E-4CB7-9537-8D1FF987ADC7','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('2ABB681F-5258-4DF3-A0B8-89962ADDBCB8','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('F54E5C88-17FA-407C-B457-8B69077748E9','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('63D66460-3834-4873-9BD4-74148EC300F4','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('14A19194-457F-40D3-B08E-715EF830FD75','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('75CF2565-D36A-46F6-935E-BFD82144B8A2','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('EDA93745-2009-41F6-B01F-C3F9930C0F67','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('20CFC7EE-7188-49F0-BDEB-C0CAF3610F2C','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('ED6EDD00-2151-4CA7-9F22-BF6DE74B0622','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('EC8DAC77-E516-4B8E-9FB8-C5A4C963563A','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('C6FDECC9-24BE-4AA0-B33C-C9195DC630B0','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('BD9890BA-8F8A-4596-B0F0-BA2F3467E5B4','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('2F496F30-1E08-4174-ABE4-BBE3977268EF','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('2CD7D3D2-77D4-43DE-A44F-B248AAF8891F','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('FFC7E6E7-00E9-41E8-BD11-B0EFD4BA3971','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('B8348F9C-D57F-4561-9981-B14DAEE7257B','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('2CAE1761-8DB0-4D18-8FF6-AD79D44EF699','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('9A241CB7-1FAE-4767-8E13-AF3A66123DC0','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('B836DB33-FB5A-4FF7-A293-D7A29488A6F6','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('23207756-F6E1-406C-AEAC-DFC1710E3E41','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('64ED1587-8791-414F-B2EA-E265584BECE9','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('07442948-0FE7-4EDD-8779-E4808B20852C','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('ACAE3351-3EDF-43E3-8021-E4CBAF20BA55','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('1E96680B-1E92-40F2-AAAE-E4D524206982','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('57A0F1D0-8029-4110-9C2A-D3A2F13E6776','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('D0A76745-1930-4755-90EA-D3CA0240BA6D','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('5379B540-4DCC-4A71-BE19-D1DA4B808A4D','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('B41B60EB-5C83-4CA6-8768-D2226A164FB6','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('31CA2727-7227-4377-B127-D261AA0CD304','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('BD7102BB-FA67-4A33-82C4-D3616ED7CB3F','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('7090FCA6-144A-430B-A609-CDDFB39C4D25','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('382BE0D2-A92A-4D73-B2CE-D640A2BBA523','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('1A4011C0-40C8-4ABD-8ACF-D6D3A220B940','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('53A62E1F-5926-4DEA-A7FB-C99B14A2120D','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('24C84EE0-70DF-4602-B133-F1CB765F2B29','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('B40C80C7-26C0-43F9-9B8A-F2C46A6FD79F','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('8F9FE478-6961-4042-A62D-F464F21BFC46','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('6E9B27D8-C963-4413-ABB5-F31F307F2AE1','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('1CCAB652-042A-4C6F-B89B-ECBFFCA468C6','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('FDA7C815-F4ED-4E6D-AE95-ED18005651EB','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('6D48A842-B5F9-45AA-BC3C-EF74C911E2FC','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('571A48F3-10E2-419C-8E72-EB4B833FA2A2','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('27C54188-4CD7-447D-9C47-E7C7F4A87A47','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('0F8E94BC-1612-4086-A6C1-E883C83758E4','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('24315A1A-CFD9-4984-AF64-F9A79E960D45','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('38602998-8149-4B6A-91EA-F9D4B93810A6','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('1FDB6A11-E422-4EA1-B4AC-FDD1197BB7F3','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('FDDCB1EA-37C9-4833-BDD8-FEFDEEF0A749','9980234') insert into stackoverflow_rules(myguid, myvarchar50) values('5241815C-CE10-4C08-BE01-CB2D1012CCF0','9980066') insert into stackoverflow_rules(myguid, myvarchar50) values('D0E5E79E-4502-42F8-B8C6-EDE3D20526B4','9970234') insert into stackoverflow_rules(myguid, myvarchar50) values('B173FC5D-BAB3-4942-A904-D9D3BA66A1ED','9960234') insert into stackoverflow_rules(myguid, myvarchar50) values('D5C2A2D9-2BA6-4059-896C-B464C8C8CB5F','9960234') insert into stackoverflow_rules(myguid, myvarchar50) values('32B865C7-1D67-457A-9550-DFDBCBFB12C6','9951166') insert into stackoverflow_rules(myguid, myvarchar50) values('82F0A99B-0C88-44EB-BE50-265C6C4C1B86','9400000') insert into stackoverflow_rules(myguid, myvarchar50) values('BDE9DC0D-B9A7-4AC9-83D5-8F9ED5F25FDA','9299199') insert into stackoverflow_rules(myguid, myvarchar50) values('2FE2415A-9D51-4AD4-9679-74BDA93DC6A6','9299166') insert into stackoverflow_rules(myguid, myvarchar50) values('4BC3D4FF-5FBB-484E-8BC6-CFE90706E3D2','9299111') insert into stackoverflow_rules(myguid, myvarchar50) values('0FC22F14-A499-4C8C-9E6B-0CF613ACF505','9281266') insert into stackoverflow_rules(myguid, myvarchar50) values('AC6B2795-A9A0-40DF-9BAF-04D4A74F4B9B','9281166') insert into stackoverflow_rules(myguid, myvarchar50) values('DAA73B60-65B9-46B2-B1AC-76A74B621700','9281166') insert into stackoverflow_rules(myguid, myvarchar50) values('D419DCBB-A76E-47DF-A59D-803AFAB770C5','9281166') insert into stackoverflow_rules(myguid, myvarchar50) values('405847E0-4764-4409-81E8-8ECCCAAE94BB','9280666') insert into stackoverflow_rules(myguid, myvarchar50) values('76D59559-F986-45EF-9F74-7870D97A377D','9280666') insert into stackoverflow_rules(myguid, myvarchar50) values('3F6F78A9-7930-4F76-839F-77304396CBC3','9280666') insert into stackoverflow_rules(myguid, myvarchar50) values('2C1A62F2-B783-432B-B83A-6BD8B29EE2DE','9280666') insert into stackoverflow_rules(myguid, myvarchar50) values('D371D319-6E88-4286-A46E-6C1905ADD6AC','9280666') insert into stackoverflow_rules(myguid, myvarchar50) values('10C42C2E-DC1A-43C4-959C-98D3A798D631','9280666') insert into stackoverflow_rules(myguid, myvarchar50) values('215F0003-188D-45C9-85BE-9B3811760CCB','9280666') insert into stackoverflow_rules(myguid, myvarchar50) values('4DD2BA43-BA1C-44BE-8C10-996454D63205','9280666') insert into stackoverflow_rules(myguid, myvarchar50) values('26D863E7-6F96-42BC-A2BA-99B30D94F6D9','9280666') insert into stackoverflow_rules(myguid, myvarchar50) values('625A2793-A60F-4FE7-9BD4-A953877B258D','9280666') insert into stackoverflow_rules(myguid, myvarchar50) values('5B5A2538-74E0-4A6F-9929-AA29BA3BDCCE','9280666') insert into stackoverflow_rules(myguid, myvarchar50) values('B8597353-0254-42AB-BAF7-AA4DAF195CC8','9280666') insert into stackoverflow_rules(myguid, myvarchar50) values('22F392BC-B42C-434F-9E32-AB8DFFC6EA76','9280666') insert into stackoverflow_rules(myguid, myvarchar50) values('E703EEE4-82B1-43C0-914F-ABCF3EF53E91','9280666') insert into stackoverflow_rules(myguid, myvarchar50) values('09BD6548-7395-4450-A7CA-D0AB0631F222','9280666') insert into stackoverflow_rules(myguid, myvarchar50) values('71D737EB-59CA-4685-827D-E17A0B4FA44D','9280666') insert into stackoverflow_rules(myguid, myvarchar50) values('F09ACB1E-64B0-4F29-86BF-E323C5347883','9280666') insert into stackoverflow_rules(myguid, myvarchar50) values('8A39E85B-8E49-44C1-8B4A-B9D79CC3F97F','9280666') insert into stackoverflow_rules(myguid, myvarchar50) values('E3BE436C-0BEC-45CE-9680-AFCE70D59B84','9280666') insert into stackoverflow_rules(myguid, myvarchar50) values('915D4F2A-8430-479F-84ED-064A3D6889DA','9280666') insert into stackoverflow_rules(myguid, myvarchar50) values('FF6DEFF5-072D-4E14-A6C2-0EF4862CCF28','9280666') insert into stackoverflow_rules(myguid, myvarchar50) values('2E7944D1-5A85-4D85-9660-138F30BED95C','9280666') insert into stackoverflow_rules(myguid, myvarchar50) values('E449E8A8-1CE4-49DE-898F-1C357777B674','9280666') insert into stackoverflow_rules(myguid, myvarchar50) values('65E89A21-5908-4913-840A-28E625F4C003','9280666') insert into stackoverflow_rules(myguid, myvarchar50) values('E23175FD-B60E-4FD4-A99A-2DB232BCB6B1','9280666') insert into stackoverflow_rules(myguid, myvarchar50) values('A521CC05-21C1-4759-AA00-384014F9C4CB','9280666') insert into stackoverflow_rules(myguid, myvarchar50) values('218CE896-8D3F-447B-A504-33428F797CE2','9280666') insert into stackoverflow_rules(myguid, myvarchar50) values('D4A3A407-20BF-481D-95DE-2C2BED13FD60','9280666') insert into stackoverflow_rules(myguid, myvarchar50) values('B5FCEB1B-3F0D-4DFE-B47D-4D44E88879A1','9280666') insert into stackoverflow_rules(myguid, myvarchar50) values('519BB489-1606-4A64-BA49-456DE79FC471','9280666') insert into stackoverflow_rules(myguid, myvarchar50) values('837D5167-CE68-4840-9592-432D371EE3AF','9280666') insert into stackoverflow_rules(myguid, myvarchar50) values('F140182F-844E-4CA7-BAA1-6A96FA726A93','9280666') insert into stackoverflow_rules(myguid, myvarchar50) values('8FB3AE45-3BFF-4DBF-ABAE-61A97EE73F36','9280666') insert into stackoverflow_rules(myguid, myvarchar50) values('33D59F0B-DAD6-4608-BF70-F2C49805FF54','9280666') insert into stackoverflow_rules(myguid, myvarchar50) values('5BFB5CEC-1322-49B0-A626-EC94092998A3','9280666') insert into stackoverflow_rules(myguid, myvarchar50) values('8AB2E1F8-A4F6-48AC-B789-FB1F46A89617','9280666') insert into stackoverflow_rules(myguid, myvarchar50) values('CD559FD0-552F-4F54-A638-F86878413D7B','9280666') insert into stackoverflow_rules(myguid, myvarchar50) values('D23AC171-E7E8-4310-B3B5-1253CCA33E5C','9251166') insert into stackoverflow_rules(myguid, myvarchar50) values('0E777743-0C70-4D76-9293-076F9DBC02EB','9251166') insert into stackoverflow_rules(myguid, myvarchar50) values('B0CDE199-9BDF-4CDD-8E32-1384CB8512B4','9200166') insert into stackoverflow_rules(myguid, myvarchar50) values('1F48F171-5179-4EC9-9554-2DA6EF60B9E8','9002266') insert into stackoverflow_rules(myguid, myvarchar50) values('A9168993-F6AF-4F81-A166-441411E72691','9001166') insert into stackoverflow_rules(myguid, myvarchar50) values('25FB4906-2AC8-4A29-B077-C4BC681D3227','9000001') insert into stackoverflow_rules(myguid, myvarchar50) values('02E14983-49E2-4867-B0C2-0BCF9BC3BAB6','8860235') insert into stackoverflow_rules(myguid, myvarchar50) values('53F915DE-1A8A-4A75-A661-0CAB56F39B11','8860234') insert into stackoverflow_rules(myguid, myvarchar50) values('834F1EB8-AEA0-435F-81AF-0C212BD54A17','8860234') insert into stackoverflow_rules(myguid, myvarchar50) values('797AFF3A-8CB0-4AE8-8430-0ED04A72394B','8860234') insert into stackoverflow_rules(myguid, myvarchar50) values('56B83693-3F46-4D8F-93A8-098517C96E94','8860234') insert into stackoverflow_rules(myguid, myvarchar50) values('1559018C-71F3-45FC-9642-09DFCC06EA78','8860234') insert into stackoverflow_rules(myguid, myvarchar50) values('04A86146-97FC-46C4-B1FE-07E916509908','8860234') insert into stackoverflow_rules(myguid, myvarchar50) values('1A3367B3-CB36-40CA-8D7D-02206840089A','8860234') insert into stackoverflow_rules(myguid, myvarchar50) values('33626BD1-AED2-4AEF-9289-199F641FDFE0','8860234') insert into stackoverflow_rules(myguid, myvarchar50) values('8468E795-71A8-4417-8179-1778FD7E915E','8860234') insert into stackoverflow_rules(myguid, myvarchar50) values('9EE6FF40-AAFB-46A8-8655-186515189AB8','8860234') insert into stackoverflow_rules(myguid, myvarchar50) values('D314A6A4-BBB5-4499-9EF4-1B37EA9131B6','8860234') insert into stackoverflow_rules(myguid, myvarchar50) values('788898AF-48E6-4DA0-BDBB-12871FE81D35','8860234') insert into stackoverflow_rules(myguid, myvarchar50) values('34D55FA5-FF82-49B5-A4EF-144999BB1B4F','8860234') insert into stackoverflow_rules(myguid, myvarchar50) values('C8FF93B1-EB7C-4711-85BA-14C78B7A27C1','8860234') insert into stackoverflow_rules(myguid, myvarchar50) values('54199346-624C-4B1E-8293-14EE9C6EF23B','8860234') insert into stackoverflow_rules(myguid, myvarchar50) values('5105C133-9120-4075-9EB6-151569E0719D','8860234') insert into stackoverflow_rules(myguid, myvarchar50) values('D03366DB-BC4A-44CC-ABC8-151F627E2A95','8860234') insert into stackoverflow_rules(myguid, myvarchar50) values('40EF76A3-2250-4840-90C1-1577AE855EEE','8860234') insert into stackoverflow_rules(myguid, myvarchar50) values('8E229744-7528-4727-880A-168331E72ED0','8860234') insert into stackoverflow_rules(myguid, myvarchar50) values('10F66C0C-C97B-4A8B-9FAC-160F3AA09A62','8860234') insert into stackoverflow_rules(myguid, myvarchar50) values('8173CB1C-A65D-4B89-9BD3-2DC4BA2F4C72','8860234') insert into stackoverflow_rules(myguid, myvarchar50) values('1CEAE246-6323-402D-95DB-2AC25DF1FD83','8860234') insert into stackoverflow_rules(myguid, myvarchar50) values('BB859D4A-3B1C-40FC-8C74-2BD44902894C','8860234') insert into stackoverflow_rules(myguid, myvarchar50) values('A31C45AF-D149-4789-A22D-2FB3E6A17627','8860234') insert into stackoverflow_rules(myguid, myvarchar50) values('52F98EEC-D3AC-429C-948F-306FA865EDE7','8860234') insert into stackoverflow_rules(myguid, myvarchar50) values('06E84032-C102-49F4-B544-3169FC1C62F4','8860234') insert into stackoverflo

  Read the article

• Guide to MySQL & NoSQL, Webinar Q&A

  - by Mat Keep

  0 0 1 959 5469 Homework 45 12 6416 14.0 Normal 0 false false false EN-US JA X-NONE /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin:0cm; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:Cambria; mso-ascii-font-family:Cambria; mso-ascii-theme-font:minor-latin; mso-hansi-font-family:Cambria; mso-hansi-theme-font:minor-latin; mso-ansi-language:EN-US;} Yesterday we ran a webinar discussing the demands of next generation web services and how blending the best of relational and NoSQL technologies enables developers and architects to deliver the agility, performance and availability needed to be successful. Attendees posted a number of great questions to the MySQL developers, serving to provide additional insights into areas like auto-sharding and cross-shard JOINs, replication, performance, client libraries, etc. So I thought it would be useful to post those below, for the benefit of those unable to attend the webinar. Before getting to the Q&A, there are a couple of other resources that maybe useful to those looking at NoSQL capabilities within MySQL: - On-Demand webinar (coming soon!) - Slides used during the webinar - Guide to MySQL and NoSQL whitepaper  - MySQL Cluster demo, including NoSQL interfaces, auto-sharing, high availability, etc.  So here is the Q&A from the event  Q. Where does MySQL Cluster fit in to the CAP theorem? A. MySQL Cluster is flexible. A single Cluster will prefer consistency over availability in the presence of network partitions. A pair of Clusters can be configured to prefer availability over consistency. A full explanation can be found on the MySQL Cluster & CAP Theorem blog post.  Q. Can you configure the number of replicas? (the slide used a replication factor of 1) Yes. A cluster is configured by an .ini file. The option NoOfReplicas sets the number of originals and replicas: 1 = no data redundancy, 2 = one copy etc. Usually there's no benefit in setting it >2. Q. Interestingly most (if not all) of the NoSQL databases recommend having 3 copies of data (the replication factor).    Yes, with configurable quorum based Reads and writes. MySQL Cluster does not need a quorum of replicas online to provide service. Systems that require a quorum need > 2 replicas to be able to tolerate a single failure. Additionally, many NoSQL systems take liberal inspiration from the original GFS paper which described a 3 replica configuration. MySQL Cluster avoids the need for a quorum by using a lightweight arbitrator. You can configure more than 2 replicas, but this is a tradeoff between incrementally improved availability, and linearly increased cost. Q. Can you have cross node group JOINS? Wouldn't that run into the risk of flooding the network? MySQL Cluster 7.2 supports cross nodegroup joins. A full cross-join can require a large amount of data transfer, which may bottleneck on network bandwidth. However, for more selective joins, typically seen with OLTP and light analytic applications, cross node-group joins give a great performance boost and network bandwidth saving over having the MySQL Server perform the join. Q. Are the details of the benchmark available anywhere? According to my calculations it results in approx. 350k ops/sec per processor which is the largest number I've seen lately The details are linked from Mikael Ronstrom's blog The benchmark uses a benchmarking tool we call flexAsynch which runs parallel asynchronous transactions. It involved 100 byte reads, of 25 columns each. Regarding the per-processor ops/s, MySQL Cluster is particularly efficient in terms of throughput/node. It uses lock-free minimal copy message passing internally, and maximizes ID cache reuse. Note also that these are in-memory tables, there is no need to read anything from disk. Q. Is access control (like table) planned to be supported for NoSQL access mode? Currently we have not seen much need for full SQL-like access control (which has always been overkill for web apps and telco apps). So we have no plans, though especially with memcached it is certainly possible to turn-on connection-level access control. But specifically table level controls are not planned. Q. How is the performance of memcached APi with MySQL against memcached+MySQL or any other Object Cache like Ecache with MySQL DB? With the memcache API we generally see a memcached response in less than 1 ms. and a small cluster with one memcached server can handle tens of thousands of operations per second. Q. Can .NET can access MemcachedAPI? Yes, just use a .Net memcache client such as the enyim or BeIT memcache libraries. Q. Is the row level locking applicable when you update a column through memcached API? An update that comes through memcached uses a row lock and then releases it immediately. Memcached operations like "INCREMENT" are actually pushed down to the data nodes. In most cases the locks are not even held long enough for a network round trip. Q. Has anyone published an example using something like PHP? I am assuming that you just use the PHP memcached extension to hook into the memcached API. Is that correct? Not that I'm aware of but absolutely you can use it with php or any of the other drivers Q. For beginner we need more examples. Take a look here for a fully worked example Q. Can I access MySQL using Cobol (Open Cobol) or C and if so where can I find the coding libraries etc? A. There is a cobol implementation that works well with MySQL, but I do not think it is Open Cobol. Also there is a MySQL C client library that is a standard part of every mysql distribution Q. Is there a place to go to find help when testing and/implementing the NoSQL access? If using Cluster then you can use the cluster@lists.mysql.com alias or post on the MySQL Cluster forum Q. Are there any white papers on this?  Yes - there is more detail in the MySQL Guide to NoSQL whitepaper If you have further questions, please don’t hesitate to use the comments below!

  Read the article

• Importing data from text file to specific columns using BULK INSERT

  - by Dinesh Asanka

  Bulk insert is much faster than using other techniques such as  SSIS. However, when you are using bulk insert you can’t insert to specific columns. If, for example, there are five columns in a table you should have five values for each record in the text file you are importing from. This is an issue when you are expecting default values to be inserted into tables. Let us say you have table as below: In this table, you are expecting ID, Status and CreatedDate to be updated automatically, so your text file may only have   FirstName  LastName  values as below: Dinesh,Asanka Saman,Liyanage Ruwan,Silva Susantha,Bathige Jude,Peires Sanjeewa,Jayawickrama If you use bulk insert to this table like follows, You will be returned an error: Bulk load data conversion error (type mismatch or invalid character for the specified codepage) for row 1, column 1 (ID). To avoid this you will need to create a view with the columns you are expecting to fill and use bulk insert against it. If you check the table now, you will see table with values in the text file and the default values.

  Read the article

• Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)

  - by Bakhtiyor

  I have mailserver configure using dovecot+postfix+mysql and it was runnig fine in the server(Ubuntu Server). But during last week it stopped working correctly. It doesn't send email. When I try to telnet localhost smtp I'm connecting successfully but when I do mail from:<[email protected]> and hit Enter it hangs on, nothing happen. Having reviewed /var/log/mail.log file I've found out that probably(99%) the problem is on postfix when it is trying to connect to MySQL server. If you see the log file given below you can see that it says Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2). Nov 14 21:54:36 ns1 dovecot: dovecot: Killed with signal 15 (by pid=7731 uid=0 code=kill) Nov 14 21:54:36 ns1 dovecot: Dovecot v1.2.9 starting up (core dumps disabled) Nov 14 21:54:36 ns1 dovecot: auth-worker(default): mysql: Connected to localhost (mailserver) Nov 14 21:54:44 ns1 postfix/postfix-script[7753]: refreshing the Postfix mail system Nov 14 21:54:44 ns1 postfix/master[1670]: reload -- version 2.7.0, configuration /etc/postfix Nov 14 21:54:52 ns1 postfix/trivial-rewrite[7759]: warning: connect to mysql server localhost: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) Nov 14 21:54:52 ns1 postfix/trivial-rewrite[7759]: fatal: mysql:/etc/postfix/mysql-virtual-alias-maps.cf(0,lock|fold_fix): table lookup problem Nov 14 21:54:53 ns1 postfix/master[1670]: warning: process /usr/lib/postfix/trivial-rewrite pid 7759 exit status 1 Nov 14 21:54:53 ns1 postfix/cleanup[7397]: warning: problem talking to service rewrite: Connection reset by peer Nov 14 21:54:53 ns1 postfix/master[1670]: warning: /usr/lib/postfix/trivial-rewrite: bad command startup -- throttling Nov 14 21:54:53 ns1 postfix/smtpd[7071]: warning: problem talking to service rewrite: Success I tried netstat -ln | grep mysql and it returns unix 2 [ ACC ] STREAM LISTENING 5817 /var/run/mysqld/mysqld.sock. The content of /etc/postfix/mysql-virtual-alias-maps.cf file is here: user = stevejobs password = apple hosts = localhost dbname = mailserver query = SELECT destination FROM virtual_aliases WHERE source='%s' Here I tried to change hosts = 127.0.0.1 but it says warning: connect to mysql server 127.0.0.1: Can't connect to MySQL server on '127.0.0.1' (110) So, I am lost and don't know where else to change in order to solve the problem. Any help would be appreciated highly. Thank you.

  Read the article

• dependency problems at installation from mysql-server-5.5

  - by Furtano

  qcons@014-QCONS:/var/lib$ sudo apt-get install -f mysql-server Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut Statusinformationen werden eingelesen... Fertig mysql-server ist schon die neueste Version. 0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert. 2 nicht vollständig installiert oder entfernt. Nach dieser Operation werden 0 B Plattenplatz zusätzlich benutzt. Möchten Sie fortfahren [J/n]? j mysql-server-5.5 (5.5.28-0ubuntu0.12.04.2) wird eingerichtet ... 121112 11:16:52 [Note] Plugin 'FEDERATED' is disabled. 121112 11:16:52 InnoDB: The InnoDB memory heap is disabled 121112 11:16:52 InnoDB: Mutexes and rw_locks use GCC atomic builtins 121112 11:16:52 InnoDB: Compressed tables use zlib 1.2.3.4 121112 11:16:52 InnoDB: Initializing buffer pool, size = 128.0M 121112 11:16:52 InnoDB: Completed initialization of buffer pool 121112 11:16:52 InnoDB: highest supported file format is Barracuda. 121112 11:16:53 InnoDB: Waiting for the background threads to start 121112 11:16:54 InnoDB: 1.1.8 started; log sequence number 1595675 121112 11:16:54 InnoDB: Starting shutdown... 121112 11:16:54 InnoDB: Shutdown completed; log sequence number 1595675 start: Job failed to start invoke-rc.d: initscript mysql, action "start" failed. dpkg: Fehler beim Bearbeiten von mysql-server-5.5 (--configure): Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück dpkg: Abhängigkeitsprobleme verhindern Konfiguration von mysql-server: mysql-server hängt ab von mysql-server-5.5; aber: Paket mysql-server-5.5 ist noch nicht konfiguriert. dpkg: Fehler beim Bearbeiten von mysql-server (--configure): Abhängigkeitsprobleme - verbleibt unkonfiguriert Es wurde kein Apport-Bericht verfasst, da die Fehlermeldung darauf hindeutet, dass dies lediglich ein Folgefehler eines vorherigen Problems ist. Fehler traten auf beim Bearbeiten von: mysql-server-5.5 mysql-server E: Sub-process /usr/bin/dpkg returned an error code (1)

  Read the article

• Thank You MySQL Community! MySQL 5.6.9 Release Candidate Available Now!

  - by Rob Young

  The MySQL Community continues its good work in testing and refining MySQL 5.6, and as such the next iteration of the 5.6 Release Candidate is now available for download.  You can get MySQL 5.6.9 here (look under the "Development Releases" tab).  This version is the result of feedback we have gotten since MySQL 5.6.7 was announced at MySQL Connect in late September. As iron sharpens iron, Community feedback sharpens the quality and performance of MySQL so please download 5.6.9 and let us know how we can improve it as we move toward the production-ready product release in early 2013. MySQL 5.6 is designed to meet the agility demands of the next generation of web apps and services and includes across the board improvements to the Optimizer, InnoDB performance/scale and online DDL operations, self-healing Replication, Performance Schema Instrumentation, Security and developer enabling NoSQL functionality.  You can learn all the details and follow MySQL Engineering blogs on all of the key features in this MySQL DevZone article. On a related note, plan to join this week's live webinars to learn more about MySQL 5.6 Self-Healing Replication Clusters and Building the Next Generation of Web, Cloud, SaaS, Embedded Application and Services with MySQL 5.6.  Hurry!  Seating is limited!  As always, thanks for your continued support of MySQL!

  Read the article

• Installing Mysql Ruby gem on 64-bit CentOS

  - by Jacek

  Hi, I have a problem installing mysql ruby gem on 64bit CentOS machine. [jacekb@vitaidealn ~]$ uname -a Linux vitaidealn.local 2.6.18-92.el5 #1 SMP Tue Jun 10 18:51:06 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux Mysql and mysql-devel packages are installed. Mysql_config provides following paths: Usage: /usr/lib64/mysql/mysql_config [OPTIONS] Options: --cflags [-I/usr/include/mysql -g -pipe -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -fno-strict-aliasing -fwrapv] --include [-I/usr/include/mysql] --libs [-L/usr/lib64/mysql -lmysqlclient -lz -lcrypt -lnsl -lm -L/usr/lib64 -lssl -lcrypto] --libs_r [-L/usr/lib64/mysql -lmysqlclient_r -lz -lpthread -lcrypt -lnsl -lm -lpthread -L/usr/lib64 -lssl -lcrypto] --socket [/var/lib/mysql/mysql.sock] --port [3306] --version [5.0.45] --libmysqld-libs [-L/usr/lib64/mysql -lmysqld -lz -lpthread -lcrypt -lnsl -lm -lpthread -lrt -L/usr/lib64 -lssl -lcrypto] Trying to install: [jacekb@vitaidealn ~]$ gem install mysql -- --with-mysql-include=/usr/include/mysql --with-mysql-libs=/usr/lib64/mysql ... ERROR: Error installing mysql: ERROR: Failed to build gem native extension. /usr/bin/ruby extconf.rb --with-mysql-include=/usr/include/mysql --with-mysql-libs=/usr/lib64/mysql checking for mysql_query() in -lmysqlclient... no checking for main() in -lm... no checking for mysql_query() in -lmysqlclient... no checking for main() in -lz... no checking for mysql_query() in -lmysqlclient... no checking for main() in -lsocket... no checking for mysql_query() in -lmysqlclient... no checking for main() in -lnsl... no checking for mysql_query() in -lmysqlclient... no *** extconf.rb failed *** Could not create Makefile due to some reason, probably lack of necessary libraries and/or headers. Check the mkmf.log file for more details. You may need configuration options. I would appreciate any help. Thanks for reading :).

  Read the article

• MySQL permission errors

  - by dotancohen

  It seems that on a Ubuntu 14.04 machine the user mysql cannot access anything. It is not writing logs nor reading files. Witness: - bruno():mysql$ cat /etc/passwd | grep mysql mysql:x:116:127:MySQL Server,,,:/nonexistent:/bin/false - bruno():mysql$ sudo mysql_install_db Installing MySQL system tables... 140818 18:16:50 [ERROR] Can't read from messagefile '/usr/share/mysql/english/errmsg.sys' 140818 18:16:50 [ERROR] Aborting 140818 18:16:50 [Note] Installation of system tables failed! Examine the logs in /var/lib/mysql for more information. ...boilerplate trimmed... - bruno():mysql$ ls -la /usr/share/mysql/english/errmsg.sys -rw-r--r-- 1 root root 59535 Jul 29 13:40 /usr/share/mysql/english/errmsg.sys - bruno():mysql$ wc -l /usr/share/mysql/english/errmsg.sys 16 /usr/share/mysql/english/errmsg.sys Here we have seen that mysql cannot read /usr/share/mysql/english/errmsg.sys even though the permissions are open to read it, and in fact the regular login user can read the file (with wc). Additionally, MySQL is not writing any logs: - bruno():mysql$ ls -la /var/log/mysql total 8 drwxr-s--- 2 mysql adm 4096 Aug 18 16:10 . drwxrwxr-x 18 root syslog 4096 Aug 18 16:10 .. What might cause this user to not be able to access anything? What can I do about it?

  Read the article

• Interview with Lenz Grimmer about MySQL Connect

  - by Keith Larson

  Keith Larson: Thank you for allowing me to do this interview with you.  I have been talking with a few different Oracle ACEs   about the MySQL Connect Conference. I figured the MySQL community might be missing you as well. You have been very busy with Oracle Linux but I know you still have an eye on the MySQL Community. How have things been?Lenz Grimmer: Thanks for including me in this series of interviews, I feel honored! I've read the other interviews, and really liked them. I still try to follow what's going on over in the MySQL community and it's good to see that many of the familiar faces are still around. Over the course of the 9 years that I was involved with MySQL, many colleagues and contacts turned into good friends and we still maintain close relationships.It's been almost 1.5 years ago that I moved into my new role here in the Linux team at Oracle, and I really enjoy working on a Linux distribution again (I worked for SUSE before I joined MySQL AB in 2002). I'm still learning a lot - Linux in the data center has greatly evolved in so many ways and there are a lot of new and exciting technologies to explore. Keith Larson: What were your thoughts when you heard that Oracle was going to deliver the MySQL Connect conference to the MySQL Community?Lenz Grimmer: I think it's testament to the fact that Oracle deeply cares about MySQL, despite what many skeptics may say. What started as "MySQL Sunday" two years ago has now evolved into a full-blown sub-conference, with 80 sessions at one of the largest corporate IT events in the world. I find this quite telling, not many products at Oracle enjoy this level of exposure! So it certainly makes me feel proud to see how far MySQL has come. Keith Larson: Have you had a chance to look over the sessions? What are your thoughts on them?Lenz Grimmer: I did indeed look at the final schedule.The content committee did a great job with selecting these sessions. I'm glad to see that the content selection was influenced by involving well-known and respected members of the MySQL community. The sessions cover a broad range of topics and technologies, both covering established topics as well as recent developments. Keith Larson: When you get a chance, what sessions do you plan on attending?Lenz Grimmer: I will actually be manning the Oracle booth in the exhibition area on one of these days, so I'm not sure if I'll have a lot of time attending sessions. But if I do, I'd love to see the keynotes and catch some of the sessions that talk about recent developments and new features in MySQL, High Availability and Clustering . Quite a lot has happened and it's hard to keep up with this constant flow of new MySQL releases.In particular, the following sessions caught my attention: MySQL Connect Keynote: The State of the Dolphin Evaluating MySQL High-Availability Alternatives CERN’s MySQL “as a Service” Deployment with Oracle VM: Empowering Users MySQL 5.6 Replication: Taking Scalability and High Availability to the Next Level What’s New in MySQL Server 5.6? MySQL Security: Past and Present MySQL at Twitter: Development and Deployment MySQL Community BOF MySQL Connect Keynote: MySQL Perspectives Keith Larson: So I will ask you just like I have asked the others I have interviewed, any tips that you would give to people for handling the long hours at conferences?Lenz Grimmer: Wear comfortable shoes and make sure to drink a lot! Also prepare a plan of the sessions you would like to attend beforehand and familiarize yourself with the venue, so you can get to the next talk in time without scrambling to find the location. The good thing about piggybacking on such a large conference like Oracle OpenWorld is that you benefit from the whole infrastructure. For example, there is a nice schedule builder that helps you to keep track of your sessions of interest. Other than that, bring enough business cards and talk to people, build up your network among your peers and other MySQL professionals! Keith Larson: What features of the MySQL 5.6 release do you look forward to the most ?Lenz Grimmer: There has been solid progress in so many areas like the InnoDB Storage Engine, the Optimizer, Replication or Performance Schema, it's hard for me to really highlight anything in particular. All in all, MySQL 5.6 sounds like a very promising release. I'm confident it will follow the tradition that Oracle already established with MySQL 5.5, which received a lot of praise even from very critical members of the MySQL community. If I had to name a single feature, I'm particularly and personally happy that the precise GIS functions have finally made it into a GA release - that was long overdue. Keith Larson:  In your opinion what is the best reason for someone to attend this event?Lenz Grimmer: This conference is an excellent opportunity to get in touch with the key people in the MySQL community and ecosystem and to get facts and information from the domain experts and developers that work on MySQL. The broad range of topics should attract people from a variety of roles and relations to MySQL, beginning with Developers and DBAs, to CIOs considering MySQL as a viable solution for their requirements. Keith Larson: You will be attending MySQL Connect and have some Oracle Linux Demos, do you see a growing demand for MySQL on Oracle Linux ?Lenz Grimmer: Yes! Oracle Linux is our recommended Linux distribution and we have a good relationship to the MySQL engineering group. They use Oracle Linux as a base Linux platform for development and QA, so we make sure that MySQL and Oracle Linux are well tested together. Setting up a MySQL server on Oracle Linux can be done very quickly, and many customers recognize the benefits of using them both in combination.Because Oracle Linux is available for free (including free bug fixes and errata), it's an ideal choice for running MySQL in your data center. You can run the same Linux distribution on both your development/staging systems as well as on the production machines, you decide which of these should be covered by a support subscription and at which level of support. This gives you flexibility and provides some really attractive cost-saving opportunities. Keith Larson: Since I am a Linux user and fan, what is on the horizon for  Oracle Linux?Lenz Grimmer: We're working hard on broadening the ecosystem around Oracle Linux, building up partnerships with ISVs and IHVs to certify Oracle Linux as a fully supported platform for their products. We also continue to collaborate closely with the Linux kernel community on various projects, to make sure that Linux scales and performs well on large systems and meets the demands of today's data centers. These improvements and enhancements will then rolled into the Unbreakable Enterprise Kernel, which is the key ingredient that sets Oracle Linux apart from other distributions. We also have a number of ongoing projects which are making good progress, and I'm sure you'll hear more about this at the upcoming OpenWorld conference :) Keith Larson: What is something that more people should be aware of when it comes to Oracle Linux and MySQL ?Lenz Grimmer: Many people assume that Oracle Linux is just tuned for Oracle products, such as the Oracle Database or our Engineered Systems. While it's of course true that we do a lot of testing and optimization for these workloads, Oracle Linux is and will remain a general-purpose Linux distribution that is a very good foundation for setting up a LAMP-Stack, for example. We also provide MySQL RPM packages for Oracle Linux, so you can easily stay up to date if you need something newer than what's included in the stock distribution.One more thing that is really unique to Oracle Linux is Ksplice, which allows you to apply security patches to the running Linux kernel, without having to reboot. This ensures that your MySQL database server keeps up and running and is not affected by any downtime. Keith Larson: What else would you like to add ?Lenz Grimmer: Thanks again for getting in touch with me, I appreciated the opportunity. I'm looking forward to MySQL Connect and Oracle OpenWorld and to meet you and many other people from the MySQL community that I haven't seen for quite some time! Keith Larson:  Thank you Lenz!

  Read the article

• MySQL Connector/Net 6.5.5 Maintenance Release has been released

  - by fernando

  MySQL Connector/Net 6.5.5, a new maintenance release of our 6.5 series, has been released.  This release is GA quality and is appropriate for use in production environments.  Please note that 6.6 is our latest driver series and is the recommended product for development. It is now available in source and binary form from http://dev.mysql.com/downloads/connector/net/#downloads and mirror sites (note that not all mirror sites may be up to date at this point-if you can't find this version on some mirror, please try again later or choose another download site.) The 6.5.5 version of MySQL Connector/Net brings the following fixes: - Fix for ArgumentNull exception when using Take().Count() in a LINQ to Entities query (bug MySql #64749, Oracle bug #13913047). - Fix for type varchar changed to bit when saving in Table Designer (Oracle bug #13916560). - Fix for error when trying to change the name of an Index on the Indexes/Keys editor; along with this fix now users can change the Index type of a new Index which could not be done   in previous versions, and when changing the Index name the change is reflected on the list view at the left side of the Index/Keys editor (Oracle bug #13613801). - Fix for stored procedure call using only its name with EF code first (MySql bug #64999, Oracle bug #14008699). - Fix for List.Contains generates a bunch of ORs instead of more efficient IN clause in   LINQ to Entities (Oracle bug #14016344, MySql bug #64934). - Fix for performance issue in generated EF query: .NET StartsWith/Contains/EndsWith produces MySql's locate instead of Like (MySql bug #64935, Oracle bug #14009363). - Fix for script generated for code first contains wrong alter table and wrong declaration for byte[] (MySql bug #64216, Oracle bug #13900091). - Fix and code contribution for bug Timed out sessions are removed without notification which allow to enable the Expired CallBack when Session Provider times out any session (bug MySql #62266 Oracle bug # 13354935) - Fix for Exception thrown when using cascade delete in an EDM Model-First in Entity Framework (Oracle bug #14008752, MySql bug #64779). - Fix for Session locking issue with MySqlSessionStateStore (MySql bug #63997, Oracble bug #13733054). - Fixed deleting a user profile using Profile provider (MySQL bug #64470, Oracle bug #13790123) - Fix for bug Cannot Create an Entity with a Key of Type String (MySQL bug #65289, Oracle bug #14540202). This fix checks if the type has a FixedLength facet set in order to create a char otherwise should create varchar, mediumtext or longtext types when using a String CLR type in Code First or Model First also tested in Database First. Unit tests added for Code First and ProviderManifest. - Fix for bug "CacheServerProperties can cause 'Packet too large' error". The issue was due to a missing reading of Max_allowed_packet server property when CacheServerProperties is in true, since the value was read only in the first connection but the following pooled connections had a wrong value causing a Packet too large error. Including also a unit test for this scenario. All unit test passed. MySQL Bug #66578 Orabug #14593547. - Fix for handling unnamed parameter in MySQLCommand. This fix allows the mysqlcommand to handle parameters without requiring naming (e.g. INSERT INTO Test (id,name) VALUES (?, ?) ) (MySQL Bug #66060, Oracle bug #14499549). - Fixed inheritance on Entity Framework Code First scenarios. Discriminator column is created using its correct type as varchar(128) (MySql bug #63920 and Oracle bug #13582335). - Fixed "Trying to customize column precision in Code First does not work" (MySql bug #65001, Oracle bug #14469048). - Fixed bug ASP.NET Membership database fails on MySql database UTF32 (MySQL bug #65144, Oracle bug #14495292). - Fix for MySqlCommand.LastInsertedId holding only 32 bit values (MySql bug #65452, Oracle bug #14171960) by changing   several internal declaration of lastinsertid from int to long. - Fixed "Decimal type should have digits at right of decimal point", now default is 2, but user's changes in   EDM designer are recognized (MySql bug #65127, Oracle bug #14474342). - Fix for NullReferenceException when saving an uninitialized row in Entity Framework (MySql bug #66066, Oracle bug #14479715). - Fix for error when calling RoleProvider.RemoveUserFromRole(): causes an exception due to a wrong table being used (MySql bug #65805, Oracle bug #14405338). - Fix for "Memory Leak on MySql.Data.MySqlClient.MySqlCommand", too many MemoryStream's instances created (MySql bug #65696, Oracle bug #14468204). - Added ANTLR attribution notice (Oracle bug #14379162). - Fixed Entity Framework + mysql connector/net in partial trust throws exceptions (MySql bug #65036, Oracle bug #14668820). - Added support in Parser for Datetime and Time types with precision when using Server 5.6 (No bug Number). - Small improvement on MySqlPoolManager CleanIdleConnections for better mysqlpoolmanager idlecleanuptimer at startup (MySql bug #66472 and Oracle bug #14652624). - Fix for bug TIMESTAMP values are mistakenly represented as DateTime with Kind = Local (Mysql bug #66964, Oracle bug #14740705). - Fix for bug Keyword not supported. Parameter name: AttachDbFilename (Mysql bug #66880, Oracle bug #14733472). - Added support to MySql script file to retrieve data when using "SHOW" statements. - Fix for Package Load Failure in Visual Studio 2005 (MySql bug #63073, Oracle bug #13491674). - Fix for bug "Unable to connect using IPv6 connections" (MySQL bug #67253, Oracle bug #14835718). - Added auto-generated values for Guid identity columns (MySql bug #67450, Oracle bug #15834176). - Fix for method FirstOrDefault not supported in some LINQ to Entities queries (MySql bug #67377, Oracle bug #15856964). The release is available to download at http://dev.mysql.com/downloads/connector/net/6.5.html Documentation ------------------------------------- You can view current Connector/Net documentation at http://dev.mysql.com/doc/refman/5.5/en/connector-net.html You can find our team blog at http://blogs.oracle.com/MySQLOnWindows. You can also post questions on our forums at http://forums.mysql.com/. Enjoy and thanks for the support! 

  Read the article

• MySQL Connect 9 Days Away – Optimizer Sessions

  - by Bertrand Matthelié

  72 1024x768 Normal 0 false false false EN-US X-NONE X-NONE /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin:0cm; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:"Times New Roman"; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} Following my previous blog post focusing on InnoDB talks at MySQL Connect, let us review today the sessions focusing on the MySQL Optimizer: Saturday, 11.30 am, Room Golden Gate 6: MySQL Optimizer Overview—Olav Sanstå, Oracle The goal of MySQL optimizer is to take a SQL query as input and produce an optimal execution plan for the query. This session presents an overview of the main phases of the MySQL optimizer and the primary optimizations done to the query. These optimizations are based on a combination of logical transformations and cost-based decisions. Examples of optimization strategies the presentation covers are the main query transformations, the join optimizer, the data access selection strategies, and the range optimizer. For the cost-based optimizations, an overview of the cost model and the data used for doing the cost estimations is included. Saturday, 1.00 pm, Room Golden Gate 6: Overview of New Optimizer Features in MySQL 5.6—Manyi Lu, Oracle Many optimizer features have been added into MySQL 5.6. This session provides an introduction to these great features. Multirange read, index condition pushdown, and batched key access will yield huge performance improvements on large data volumes. Structured explain, explain for update/delete/insert, and optimizer tracing will help users analyze and speed up queries. And last but not least, the session covers subquery optimizations in Release 5.6. Saturday, 7.00 pm, Room Golden Gate 4: BoF: Query Optimizations: What Is New and What Is Coming? This BoF presents common techniques for query optimization, covers what is new in MySQL 5.6, and provides a discussion forum in which attendees can tell the MySQL optimizer team which optimizations they would like to see in the future. Sunday, 1.15 pm, Room Golden Gate 8: Query Performance Comparison of MySQL 5.5 and MySQL 5.6—Øystein Grøvlen, Oracle MySQL Release 5.6 contains several improvements in the query optimizer that create improved performance for complex queries. This presentation looks at how MySQL 5.6 improves the performance of many of the queries in the DBT-3 benchmark. Based on the observed improvements, the presentation discusses what makes the specific queries perform better in Release 5.6. It describes the relevant new optimization techniques and gives examples of the types of queries that will benefit from these techniques. Sunday, 4.15 pm, Room Golden Gate 4: Powerful EXPLAIN in MySQL 5.6—Evgeny Potemkin, Oracle The EXPLAIN command of MySQL has long been a very useful tool for understanding how MySQL will execute a query. Release 5.6 of the MySQL database offers several new additions that give more-detailed information about the query plan and make it easier to understand at the same time. This presentation gives an overview of new EXPLAIN features: structured EXPLAIN in JSON format, EXPLAIN for INSERT/UPDATE/DELETE, and optimizer tracing. Examples in the session give insights into how you can take advantage of the new features. They show how these features supplement and relate to each other and to classical EXPLAIN and how and why the MySQL server chooses a particular query plan. You can check out the full program here as well as in the September edition of the MySQL newsletter. Not registered yet? You can still save US$ 300 over the on-site fee – Register Now!

  Read the article

• Refreshing imported MySQL data with MySQL for Excel

  - by Javier Rivera

  Welcome to another blog post from the MySQL for Excel Team. Today we're going to talk about a new feature included since MySQL for Excel 1.3.0, you can install the latest GA or maintenance version using the MySQL Installer or optionally you can download directly any GA or non-GA version from the MySQL Developer Zone.As some users suggested in our forums we should be maintaining the link between tables and Excel not only when editing data through the Edit MySQL Data option, but also when importing data via Import MySQL Data. Before 1.3.0 this process only provided you with an offline copy of the Table's data into Excel and you had no way to refresh that information from the DB later on. Now, with this new feature we'll show you how easy is to work with the latest available information at all times. This feature is transparent to you (it doesn't require additional steps to work as long as the users had the Create an Excel Table for the imported MySQL table data option enabled. To ensure you have this option checked, click over Advanced Options... after the Import Data dialog is displayed). The current blog post assumes you already know how to import data into excel, you could always take a look at our previous post How To - Guide to Importing Data from a MySQL Database to Excel using MySQL for Excel if you need further reference on that topic. After importing Data from a MySQL Table into Excel, you can refresh the data in 3 ways.1. Simply right click over the range of the imported data, to show the pop-up menu: Click over the Refresh button to obtain the latest copy of the data in the table. 2. Click the Refresh button on the Data ribbon: 3. Click the Refresh All button in the Data ribbon (beware this will refresh all Excel tables in the Workbook): Please take a note of a couple of details here, the first one is about the size of the table. If by the time you refresh the table new columns had been added to it, and you originally have imported all columns, the table will grow to the right. The same applies to rows, if the table has new rows and you did not limit the results , the table will grow to to the bottom of the sheet in Excel. The second detail you should take into account is this operation will overwrite any changes done to the cells after the table was originally imported or previously refreshed: Now with this new feature, imported data remains linked to the data source and is available to be updated at all times. It empowers the user to always be able to work with the latest version of the imported MySQL data. We hope you like this this new feature and give it a try! Remember that your feedback is very important for us, so drop us a message with your comments, suggestions for this or other features and follow us at our social media channels: MySQL on Windows (this) Blog: https://blogs.oracle.com/MySqlOnWindows/ MySQL for Excel forum: http://forums.mysql.com/list.php?172 Facebook: http://www.facebook.com/mysql YouTube channel: https://www.youtube.com/user/MySQLChannel Thanks!

  Read the article

• socket problem with MySQL

  - by Hristo

  This is a recent problem... MySQL was working and a couple of days ago I must have done something. I deleted MySQL and tried reinstalling using the .dmg file. The mysql.sock file never gets created and I get the following error messages: Hristo$ mysql Enter password: ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/mysql/mysql.sock' (2) I also tried stopping Apache and installing but Apache gave me an error... I don't know if this is good or bad: Hristo$ sudo apachectl stop launchctl: Error unloading: org.apache.httpd I tried the MacPorts installation as well but the socket file still didn't get created. I don't really know what to do and I don't want to reinstall Snow Leopard and start from scratch :/ I also tried installing the 32-bit version and same deal. No luck. Finally... I tried doing the source installation but when I get to the configuration step, I get the following error: -bash: ./configure: No such file or directory The file is "mysql-5.1.47-osx10.6-x86_64.tar.gz" so I think it is the proper file for source installation and yes I have a 64 bit system. I don't know what to do anymore. Any ideas? Thanks, Hristo

  Read the article

• Integer in MySQL Subqueries in store procedure

  - by confiq

  I made simple procedure just to demonstrate CREATE PROCEDURE `demo`(demo_int int) BEGIN DECLARE minid INT; SELECT min(id) FROM (SELECT id FROM events LIMIT demo_int,9999999999999999) as hoo INTO minid; END$$ The problem is with demo_int, if i change it to LIMIT 1,9999999999999999 it works but LIMIT demo_int,9999999999999999 Does not... It gives error You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'demo_int,9999999999999999) as hoo INTO minid; END' at line 4 (errno: 1064) Any clues?

  Read the article

• What's wrong with this MySQL Stored Function?

  - by Matt

  Having trouble getting this to apply in MySQL Workbench 5.2.15 DELIMITER // CREATE DEFINER=`potts`@`%` FUNCTION `potts`.`fn_create_category_test` (test_arg VARCHAR(50)) RETURNS int BEGIN DECLARE new_id int; SET new_id = 8; RETURN new_id; END// The actual function will have a lot more between BEGIN and END but as it stands, even this 3 liner won't work. Thanks!

  Read the article

• Integer in MySQL procedure, syntax error

  - by confiq

  I made simple procedure just to demonstrate CREATE PROCEDURE `demo`(demo_int int) BEGIN DECLARE minid INT; SELECT min(id) FROM (SELECT id FROM events LIMIT demo_int,9999999999999999) as hoo INTO minid; END$$ The problem is with demo_int, if i change it to LIMIT 1,9999999999999999 it works but LIMIT demo_int,9999999999999999 Does not... It gives error You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'demo_int,9999999999999999) as hoo INTO minid; END' at line 4 (errno: 1064) Any clues?

  Read the article

• insert ... select with divide operator in select errors?

  - by Mark

  Hi, the following query CREATE TABLE IF NOT EXISTS XY ( x INT NOT NULL , y FLOAT NULL , PRIMARY KEY(x) ) INSERT INTO XY (x,y) (select 1 as x ,(1/7) as y); errors with Error code 1064, SQL state 42000: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'INSERT INTO XY (x,y) (select 1 as x ,(1/7) as y)' at line 7 Line 1, column 1 any ideas?

  Read the article

• Verizon Wireless Supports its Mission-Critical Employee Portal with MySQL

  - by Bertrand Matthelié

  Normal 0 false false false EN-US X-NONE X-NONE /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin:0cm; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Cambria","serif"; mso-ascii-font-family:Cambria; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:"Times New Roman"; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Cambria; mso-hansi-theme-font:minor-latin;} Verizon Wireless, the #1 mobile carrier in the United States, operates the nation’s largest 3G and 4G LTE network, with the most subscribers (109 millions) and the highest revenue ($70.2 Billion in 2011). Verizon Wireless built the first wide-area wireless broadband network and delivered the first wireless consumer 3G multimedia service in the US, and offers global voice and data services in more than 200 destinations around the world. To support 4.2 million daily wireless transactions and 493,000 calls and emails transactions produced by 94.2 million retail customers, Verizon Wireless employs over 78,000 employees with area headquarters across the United States. The Business Challenge Seeing the stupendous rise in social media, video streaming, live broadcasting…etc which redefined the scope of technology, Verizon Wireless, as a technology savvy company, wanted to provide a platform to its employees where they could network socially, view and host microsites, stream live videos, blog and provide the latest news. The IT team at Verizon Wireless had abundant experience with various technology platforms to support the huge number of applications in the company. However, open-source products weren’t yet widely used in the organization and the team had the ambition to adopt such technologies and see if the architecture could meet Verizon Wireless’ rigid requirements. After evaluating a few solutions, the IT team decided to use the LAMP stack for Vzweb, its mission-critical, 24x7 employee portal, with Drupal as the front end and MySQL on Linux as the backend, and for a few other internal websites also on MySQL. The MySQL Solution Verizon Wireless started to support its employee portal, Vzweb, its online streaming website, Vztube, and internal wiki pages, Vzwiki, with MySQL 5.1 in 2010. Vzweb is the main internal communication channel for Verizon Wireless, while Vztube hosts important company-wide webcasts regularly for executive-level announcements, so both channels have to be live and accessible all the time for its 78,000 employees across the United States. However during the initial deployment of the MySQL based Intranet, the application experienced performance issues. High connection spikes occurred causing slow user response time, and the IT team applied workarounds to continue the service. A number of key performance indexes (KPI) for the infrastructure were identified and the operational framework redesigned to support a more robust website and conform to the 99.985% uptime SLA (Service-Level Agreement). The MySQL DBA team made a series of upgrades in MySQL: Step 1: Moved from MyISAM to InnoDB storage engine in 2010 Step 2: Upgraded to the latest MySQL 5.1.54 release in 2010 Step 3: Upgraded from MySQL 5.1 to the latest GA release MySQL 5.5 in 2011, and leveraging MySQL Thread Pool as part of MySQL Enterprise Edition to scale better After making those changes, the team saw a much better response time during high concurrency use cases, and achieved an amazing performance improvement of 1400%! In January 2011, Verizon CEO, Ivan Seidenberg, announced the iPhone launch during the opening keynote at Consumer Electronic Show (CES) in Las Vegas, and that presentation was streamed live to its 78,000 employees. The event was broadcasted flawlessly with MySQL as the database. Later in 2011, Hurricane Irene attacked the East Coast of United States and caused major life and financial damages. During the hurricane, the team directed more traffic to its west coast data center to avoid potential infrastructure damage in the East Coast. Such transition was executed smoothly and even though the geographical distance became longer for the East Coast users, there was no impact in the performance of Vzweb and Vztube, and the SLA goal was achieved. “MySQL is the key component of Verizon Wireless’ mission-critical employee portal application,” said Shivinder Singh, senior DBA at Verizon Wireless. “We achieved 1400% performance improvement by moving from the MyISAM storage engine to InnoDB, upgrading to the latest GA release MySQL 5.5, and using the MySQL Thread Pool to support high concurrent user connections. MySQL has become part of our IT infrastructure, on which potentially more future applications will be built.” To learn more about MySQL Enterprise Edition, Get our Product Guide.

  Read the article

• ???????HP??ID??????????30????

  - by Oracle Japan PR

  ?? ?????? ??????????HP????3??????????ID?????30??????????ID??????????30?????????ID?????????????????????????????????????????????ID?????????????????????????????????????????? ???????????????????

  Read the article

• Error 2013: Lost connection to MySQL server during query when executing CHECK TABLE FOR UPGRADE

  - by Dean Richardson

  I just upgraded Ubuntu from 11.10 to 12.04. My rails app now returns the (passenger) error "Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) (Mysql2::Error)". I get a similar error when I try to access mysql at the command line on my Ubuntu server using mysql -u root -p. I have mysql-server 5.5 installed. I've checked and mysql is not running. When I try to restart it, it fails. Here are some key lines from the tail of /var/log/syslog after an attempted restart: dean@dgwjasonfried:/etc/mysql$ tail -f /var/log/syslog Mar 7 08:55:27 dgwjasonfried /etc/mysql/debian-start[5107]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck Mar 7 08:55:27 dgwjasonfried /etc/mysql/debian-start[5107]: Running 'mysqlcheck' with connection arguments: '--port=3306' '--socket=/var/run/mysqld/mysqld.sock' '--host=localhost' '--socket=/var/run/mysqld/mysqld.sock' '--host=localhost' '--socket=/var/run/mysqld/mysqld.sock' Mar 7 08:55:27 dgwjasonfried /etc/mysql/debian-start[5107]: Running 'mysqlcheck' with connection arguments: '--port=3306' '--socket=/var/run/mysqld/mysqld.sock' '--host=localhost' '--socket=/var/run/mysqld/mysqld.sock' '--host=localhost' '--socket=/var/run/mysqld/mysqld.sock' Mar 7 08:55:27 dgwjasonfried /etc/mysql/debian-start[5107]: /usr/bin/mysqlcheck: Got error: 2013: Lost connection to MySQL server during query when executing 'CHECK TABLE ... FOR UPGRADE' Mar 7 08:55:27 dgwjasonfried /etc/mysql/debian-start[5107]: FATAL ERROR: Upgrade failed Mar 7 08:55:27 dgwjasonfried /etc/mysql/debian-start[5107]: molex_app_development.assets OK Mar 7 08:55:27 dgwjasonfried /etc/mysql/debian-start[5107]: molex_app_development.ecd_types OK Mar 7 08:55:27 dgwjasonfried /etc/mysql/debian-start[5124]: Checking for insecure root accounts. Mar 7 08:55:27 dgwjasonfried kernel: [ 7551.769657] init: mysql main process (5064) terminated with status 1 Mar 7 08:55:27 dgwjasonfried kernel: [ 7551.769697] init: mysql respawning too fast, stopped Here is most of /etc/mysql/my.cnf: Remember to edit /etc/mysql/debian.cnf when changing the socket location. [client] port = 3306 socket = /var/run/mysqld/mysqld.sock Here is entries for some specific programs The following values assume you have at least 32M ram This was formally known as [safe_mysqld]. Both versions are currently parsed. [mysqld_safe] socket = /var/run/mysqld/mysqld.sock nice = 0 [mysqld] Basic Settings user = mysql pid-file = /var/run/mysqld/mysqld.pid socket = /var/run/mysqld/mysqld.sock port = 3306 basedir = /usr datadir = /var/lib/mysql tmpdir = /tmp lc-messages-dir = /usr/share/mysql skip-external-locking Instead of skip-networking the default is now to listen only on localhost which is more compatible and is not less secure. bind-address = 127.0.0.1 And here are permissions for var/run/mysqld/mysqld.sock: srwxrwxrwx 1 mysql mysql 0 Mar 7 09:18 mysqld.sock I'd be grateful for any suggestions the community might have. I reviewed the related questions here and attempted some of the fixes offered but to no avail. Thanks! Dean Richardson Update: Thanks to quanta's suggestion, I looked at the /var/log/mysql/error.log file. I found error messages relating to pointers, fatal signals, and more stuff that I really couldn't make much sense of. I also found mysql man page references, however. One suggested that I try starting mysqld with the --innodb_force_recovery=# option, then attempt to dump (or drop) the offending/corrupted database or table. I worked through the escalating option levels one-by-one (innodb_force_recovery=1, innodb_force_recovery=2, etc.) This allowed me to successfully run mysql -u root -p from the command line and execute several commands. I was able to run queries on my production database, but any attempt to query, dump, or even drop my development database raised an error and led to me losing the connection to mysql. So I've made progress, but until I'm somehow able to drop or repair my development db I'm still unable to get my app to load. Any further advice or suggestions? Thanks! Dean Update: Right after running sudo mysqld --innodb_force_recover=1 from the command line, the error.log contains this: Right after retrying sudo mysqld --innodb_force_recover=1, The error.log file shows this: 130308 4:55:39 [Note] Plugin 'FEDERATED' is disabled. 130308 4:55:39 InnoDB: The InnoDB memory heap is disabled 130308 4:55:39 InnoDB: Mutexes and rw_locks use GCC atomic builtins 130308 4:55:39 InnoDB: Compressed tables use zlib 1.2.3.4 130308 4:55:39 InnoDB: Initializing buffer pool, size = 128.0M 130308 4:55:39 InnoDB: Completed initialization of buffer pool 130308 4:55:39 InnoDB: highest supported file format is Barracuda. InnoDB: The log sequence number in ibdata files does not match InnoDB: the log sequence number in the ib_logfiles! 130308 4:55:39 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... 130308 4:55:40 InnoDB: Waiting for the background threads to start 130308 4:55:41 InnoDB: 1.1.8 started; log sequence number 10259220 130308 4:55:41 InnoDB: !!! innodb_force_recovery is set to 1 !!! 130308 4:55:41 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306 130308 4:55:41 [Note] - '127.0.0.1' resolves to '127.0.0.1'; 130308 4:55:41 [Note] Server socket created on IP: '127.0.0.1'. 130308 4:55:41 [Note] Event Scheduler: Loaded 0 events 130308 4:55:41 [Note] mysqld: ready for connections. Version: '5.5.29-0ubuntu0.12.04.2' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu) Then after mysql -u root -p and mysql> drop database molex_app_development; ERROR 2013 (HY000): Lost connection to MySQL server during query mysql> the error.log contains: dean@dgwjasonfried:/var/log/mysql$ tail -f error.log /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f6a3ff9ecbd] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (7f6a1c004bd8): is an invalid pointer Connection ID (thread ID): 1 Status: NOT_KILLED The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 130308 4:55:39 [Note] Plugin 'FEDERATED' is disabled. 130308 4:55:39 InnoDB: The InnoDB memory heap is disabled 130308 4:55:39 InnoDB: Mutexes and rw_locks use GCC atomic builtins 130308 4:55:39 InnoDB: Compressed tables use zlib 1.2.3.4 130308 4:55:39 InnoDB: Initializing buffer pool, size = 128.0M 130308 4:55:39 InnoDB: Completed initialization of buffer pool 130308 4:55:39 InnoDB: highest supported file format is Barracuda. InnoDB: The log sequence number in ibdata files does not match InnoDB: the log sequence number in the ib_logfiles! 130308 4:55:39 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... 130308 4:55:40 InnoDB: Waiting for the background threads to start 130308 4:55:41 InnoDB: 1.1.8 started; log sequence number 10259220 130308 4:55:41 InnoDB: !!! innodb_force_recovery is set to 1 !!! 130308 4:55:41 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306 130308 4:55:41 [Note] - '127.0.0.1' resolves to '127.0.0.1'; 130308 4:55:41 [Note] Server socket created on IP: '127.0.0.1'. 130308 4:55:41 [Note] Event Scheduler: Loaded 0 events 130308 4:55:41 [Note] mysqld: ready for connections. Version: '5.5.29-0ubuntu0.12.04.2' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu) 130308 4:58:23 [ERROR] Incorrect definition of table mysql.proc: expected column 'comment' at position 15 to have type text, found type char(64). 130308 4:58:23 InnoDB: Assertion failure in thread 140168992810752 in file fsp0fsp.c line 3639 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 10:58:23 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=16777216 read_buffer_size=131072 max_used_connections=1 max_threads=151 thread_count=1 connection_count=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346681 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7f7ba4f6c2f0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 7f7ba3065e60 thread_stack 0x30000 mysqld(my_print_stacktrace+0x29)[0x7f7ba3609039] mysqld(handle_fatal_signal+0x483)[0x7f7ba34cf9c3] /lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x7f7ba2220cb0] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35)[0x7f7ba188c425] /lib/x86_64-linux-gnu/libc.so.6(abort+0x17b)[0x7f7ba188fb8b] mysqld(+0x65e0fc)[0x7f7ba37160fc] mysqld(+0x602be6)[0x7f7ba36babe6] mysqld(+0x635006)[0x7f7ba36ed006] mysqld(+0x5d7072)[0x7f7ba368f072] mysqld(+0x5d7b9c)[0x7f7ba368fb9c] mysqld(+0x6a3348)[0x7f7ba375b348] mysqld(+0x6a3887)[0x7f7ba375b887] mysqld(+0x5c6a86)[0x7f7ba367ea86] mysqld(+0x5ae3a7)[0x7f7ba36663a7] mysqld(_Z15ha_delete_tableP3THDP10handlertonPKcS4_S4_b+0x16d)[0x7f7ba34d3ffd] mysqld(_Z23mysql_rm_table_no_locksP3THDP10TABLE_LISTbbbb+0x568)[0x7f7ba3417f78] mysqld(_Z11mysql_rm_dbP3THDPcbb+0x8aa)[0x7f7ba339780a] mysqld(_Z21mysql_execute_commandP3THD+0x394c)[0x7f7ba33b886c] mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x10f)[0x7f7ba33bb28f] mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1380)[0x7f7ba33bc6e0] mysqld(_Z24do_handle_one_connectionP3THD+0x1bd)[0x7f7ba346119d] mysqld(handle_one_connection+0x50)[0x7f7ba3461200] /lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x7f7ba2218e9a] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f7ba1949cbd] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (7f7b7c004b60): is an invalid pointer Connection ID (thread ID): 1 Status: NOT_KILLED The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. --Dean

  Read the article

• Can't edit an account in MySQL Administrator on OS X

  - by Wavy Crab

  I'm running MySQL 5.5.20 on OS X 10.6.8. Using MySQL Administrator 1.2.12 (the latest) I am unable to edit any accounts. After successfully connecting to the database in MySQL Administrator, I go the Account tab, expand a user, and it just says "Loading...". It will stay on "Loading..." indefinitely. The symptoms are almost identical to user's experience and this MySQL bug from 2006, which has since been closed (fixed?). If I create a user and grant permissions to a schema, I get the error "Could not save changes to the use", which came up in 2005 as a bug (now closed). How do I edit MySQL accounts using MySQL Administrator?

  Read the article

• Upgrade MySQL on Plesk on Windows

  - by Cyril Gupta

  I just got a nasty surprise when I installed a website in Unicode Hindi (Indian language) on a server, all freshly entered unicode data is turning into question marks on the server. On my dev machine it works perfectly. I found that I have MySQL version 5.0.45 (installed in default by Plesk I guess). On my dev machine i have version 5.1.33. I believe the problem could be due to the version difference. The new version of MySQL apparently has better support for Unicode than the older one. I want to upgrade MySQL on my Windows Server machine with Plesk installed on it I am reluctant to just install the new version using the mysql installer because Plesk maintains some custom settings for mysql and I am afraid the new version could change those settings and break my db. Can anyone tell me do I have to do anything special to install MySQL on plesk on windows or can I just use the new version installer?

  Read the article

• mysql: job failded to start. mysqld.sock is missing

  - by Freefri

  How can I fix this and start mysql-server? After /etc/init.d/mysql start or service mysql start I get the message start: "Job failed to start" And after # mysqld I get this: mysqld 121123 11:33:33 [ERROR] Can't find messagefile '/usr/share/mysql/errmsg.sys' 121123 11:33:33 [Note] Plugin 'FEDERATED' is disabled. mysqld: Unknown error 1146 121123 11:33:33 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. 121123 11:33:33 InnoDB: The InnoDB memory heap is disabled 121123 11:33:33 InnoDB: Mutexes and rw_locks use GCC atomic builtins 121123 11:33:33 InnoDB: Compressed tables use zlib 1.2.3.4 121123 11:33:33 InnoDB: Initializing buffer pool, size = 128.0M 121123 11:33:33 InnoDB: Completed initialization of buffer pool 121123 11:33:33 InnoDB: highest supported file format is Barracuda. 121123 11:33:33 InnoDB: Waiting for the background threads to start 121123 11:33:34 InnoDB: 1.1.8 started; log sequence number 1595675 121123 11:33:34 [ERROR] Aborting 121123 11:33:34 InnoDB: Starting shutdown... 121123 11:33:35 InnoDB: Shutdown completed; log sequence number 1595675 121123 11:33:35 [Note] I try to do what mysql say me to do: mysql_upgrade Looking for 'mysql' as: mysql Looking for 'mysqlcheck' as: mysqlcheck Running 'mysqlcheck' with connection arguments: '--port=3306' '--socket=/var/run/mysqld/mysqld.sock' mysqlcheck: Got error: 2002: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) when trying to connect FATAL ERROR: Upgrade failed And yes, /var/run/mysql is empty: mysql_upgrade Looking for 'mysql' as: mysql Looking for 'mysqlcheck' as: mysqlcheck Running 'mysqlcheck' with connection arguments: '--port=3306' '--socket=/var/run/mysqld/mysqld.sock' mysqlcheck: Got error: 2002: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) when trying to connect FATAL ERROR: Upgrade failed And this is my file /etc/mysql/my.cnf # cat /etc/mysql/my.cnf |grep sock # Remember to edit /etc/mysql/debian.cnf when changing the socket location. socket = /var/run/mysqld/mysqld.sock socket = /var/run/mysqld/mysqld.sock socket = /var/run/mysqld/mysqld.sock Then I try to reinstall mysql from cero: apt-get purge mysql-client mysql-common mysql-server rm -R /var/lib/mysql rm -R /etc/mysql rm -R /var/run/mysqld userdel mysql apt-get install mysql-server mysql-client Then, after typing my root password for mysql I get this error: | Unable to set password for the MySQL "root" user ¦ ¦ ¦ ¦ An error occurred while setting the password for the MySQL administrative ¦ ¦ user. This may have happened because the account already has a password, or ¦ ¦ because of a communication problem with the MySQL server. ¦ ¦ ¦ ¦ You should check the account's password after the package installation. ¦ ¦ ¦ ¦ Please read the /usr/share/doc/mysql-server-5.5/README.Debian file for more ¦ ¦ information. And again I can't start mysql getting the same messages.

  Read the article

• App ID and Bundle Seed ID in multiple applications with ASPN, InApp Purchase, and other

  - by Benny7500

  I will create multiple sale versions of the same application with push notifications feature: CoolApp (full version) CoolApp Free (free, features limited version) CoolApp InApp (free version upgradable to full via InApp Purchase) While registering for App ID in Apple Program Portal is possible to create "Bundle seed ID": "The Bundle Seed ID portion of your App ID can be utilized to share keychain access between multiple applications you build with a single App ID" Is possible to create only one App ID, for example: "XDFGYE6TR4.com.company.coolapp" and use it for all three versions of CoolApp, with enabled push notifications and in app purchases?

  Read the article

• DELETING doubled users (MySQL)

  - by vizzdoom

  Hi I have two tables. There are users informations from two sites: p_users p_users2 There are 3726 users in first and 13717 in second. Some users in p_users2 are in p_users. I want merge this two tables to the one big table - but rows with same usernames can't be doubled. How can I do this? I tried something like this: DELETE FROM p_users2 WHERE user_id IN ( select p.user_id from p_users p join p_users2 p2 on p.username=p2.username ) After that I should receive a table with unique usernames, which I want to export and import to the first one. But when I execute my query I got error: SQL Error (1093): You can't specify target table 'p_users2' for update in FROM clause. (MYSQL)

  Read the article

< Previous Page | 2 3 4 5 6 7 8 9 10 11 12 13  | Next Page >