Datasets:

Cometyang

/

SQLData

like 1

--Updates triggerName field in the MOTECH_TASKS_TASKACTIVITY. SET SQL_SAFE_UPDATES = 0; UPDATE `MOTECH_TASKS_TASKACTIVITY` `dest`, (SELECT `trigger`.`id`, `trigger`.`displayName`, `task`.`id` AS 'taskId' FROM `MOTECH_TASKS_TASKTRIGGERINFORMATION` `trigger`, `MOTECH_TASKS_TASK` `task` WHERE ROW(`trigger`.`id` , `task`.`id`) IN (SELECT `trigger_id_OID`, `id` FROM `MOTECH_TASKS_TASK`)) `src` SET `dest`.`triggerName` = `src`.`displayName` WHERE `dest`.`task` = `src`.`taskId`; SET SQL_SAFE_UPDATES = 1;

<reponame>bishwajit06/bitm -- phpMyAdmin SQL Dump -- version 4.8.3 -- https://www.phpmyadmin.net/ -- -- Host: 127.0.0.1 -- Generation Time: Jul 07, 2020 at 06:58 PM -- Server version: 10.1.37-MariaDB -- PHP Version: 7.2.12 SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO"; SET AUTOCOMMIT = 0; START TRANSACTION; SET time_zone = "+00:00"; /*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */; /*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */; /*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */; /*!40101 SET NAMES utf8mb4 */; -- -- Database: `bitm` -- -- -------------------------------------------------------- -- -- Table structure for table `answers` -- CREATE TABLE `answers` ( `id` bigint(20) UNSIGNED NOT NULL, `question_id` int(10) UNSIGNED NOT NULL, `user_id` int(10) UNSIGNED NOT NULL DEFAULT '0', `body` text COLLATE utf8_unicode_ci NOT NULL, `votes_count` int(11) NOT NULL DEFAULT '0', `created_at` timestamp NULL DEFAULT NULL, `updated_at` timestamp NULL DEFAULT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Dumping data for table `answers` -- INSERT INTO `answers` (`id`, `question_id`, `user_id`, `body`, `votes_count`, `created_at`, `updated_at`) VALUES (1, 1, 5, 'Dicta voluptas cupiditate nam voluptatibus. Dolorem excepturi sit ea culpa nemo in. Aut eum cupiditate qui quis tempore quia.\n\nUt voluptas porro ea sit nihil magni. Nam pariatur cupiditate in incidunt. Beatae eos laboriosam eum in. Voluptate laborum magni libero nisi vel distinctio.\n\nQui quia ut aspernatur nisi facilis nemo. Minima qui ipsum sint quo non culpa voluptatem porro. Est facilis dolores velit non dignissimos.\n\nEt aperiam suscipit voluptas illo nesciunt qui. Perspiciatis officiis alias laboriosam perferendis quisquam nemo neque suscipit. Vitae assumenda qui corporis omnis corrupti mollitia. Reiciendis rem eius fugit autem eos consectetur rem. Fugit iste eaque magnam autem officiis.\n\nEveniet voluptatem aut ut voluptas qui ipsa voluptatem non. Numquam sit officia maiores omnis mollitia quod non quibusdam. Corporis alias tempore dignissimos et sint. Praesentium voluptatibus amet enim pariatur rerum eius quas.\n\nAlias non laudantium eos necessitatibus. Veniam odio qui sed tempore. Odit neque dolores eos dicta ab repellat. Blanditiis et occaecati possimus illo non eos.', 2, '2020-04-05 07:41:13', '2020-04-05 07:41:27'), (2, 1, 2, 'Doloremque sequi nulla aliquam repudiandae. Quaerat id ut molestiae optio alias eum distinctio. Inventore nihil aut vel ullam est suscipit.\n\nRerum voluptas optio quia molestias dolores eos. Odio cupiditate dolorum in molestias ut sunt eius. Non fuga quae beatae.\n\nVel delectus ut sapiente assumenda voluptatem inventore. Architecto sit minima modi. Neque ex ad veniam. Voluptate ut deleniti explicabo asperiores. Eius quis nisi recusandae repellendus enim.\n\nQui consequatur a aut repellendus beatae porro. Omnis reiciendis et ut id. Molestiae suscipit ratione non officia sint.\n\nConsequatur consequatur inventore omnis cupiditate neque. Id iure sed sint perspiciatis culpa at voluptas. Eum maxime aliquid nihil officia molestiae doloribus neque. Explicabo repellat fugiat temporibus. Atque deleniti blanditiis voluptas voluptas voluptates odio aut.\n\nOmnis modi consequatur voluptate ut neque et alias. Illo magni omnis sit libero. Quia iusto suscipit et dolor sequi harum laborum. Sequi sed veniam incidunt rerum.\n\nEa eveniet id quidem saepe quis dignissimos. Ullam ex fuga rerum exercitationem sunt reiciendis magnam aperiam. Mollitia excepturi iusto distinctio est.', 1, '2020-04-05 07:41:13', '2020-04-05 07:41:13'), (3, 1, 2, 'Nostrum nihil voluptatem rerum ea qui magni. Ipsam illo culpa inventore corrupti rerum at impedit dolor.\n\nOmnis labore qui quidem in doloremque ad. Sequi occaecati ipsam dolore in in nulla omnis. Incidunt sed ut et ut sit sint. Perspiciatis non nihil voluptates ut veniam voluptates mollitia. Praesentium rem ratione inventore accusantium dolores consequatur quam.\n\nQuos aut autem facere id unde tempore. Esse qui ipsum impedit omnis dolorum beatae alias. Iste cupiditate id laborum asperiores earum hic occaecati voluptas.\n\nProvident velit voluptatem sed deleniti vero debitis reiciendis sunt. Eum porro doloremque exercitationem officiis ut nemo error.\n\nQuas dolor vel nulla voluptatem sequi et optio. Error modi nesciunt molestiae placeat ut ab. Ipsa illo laboriosam dicta nihil ut. In quia tempora consequatur eos.', 2, '2020-04-05 07:41:14', '2020-04-05 07:41:27'), (4, 1, 5, 'Explicabo culpa omnis incidunt voluptas atque aut. Perferendis minima ullam rem ipsa. Hic corrupti vel adipisci sunt est saepe.\n\nEa et eligendi omnis molestiae pariatur nesciunt. Et et deserunt et assumenda. Autem ipsum molestiae non pariatur voluptas. Et est culpa sapiente unde omnis.\n\nDolor adipisci quas in ipsa. Iste est enim tempora et nam. Laboriosam voluptatum illo aut et.\n\nEaque sit hic id perferendis accusantium aut perferendis. Corrupti qui optio optio sit dignissimos quia. Excepturi beatae magni recusandae voluptas odit ut beatae. Quia quasi facilis tenetur laudantium.\n\nNihil rem laboriosam et totam aut dolore beatae. Accusamus qui rerum architecto voluptatibus deleniti ex. Omnis dolorum quisquam ab animi ipsa ut repellat.\n\nAut ad soluta amet qui ratione aspernatur voluptas. Iure ex voluptas provident est aliquam inventore numquam. Sint et qui hic enim suscipit ut inventore. Quam natus ex consequatur deserunt. Repellat et magni qui asperiores.', -1, '2020-04-05 07:41:14', '2020-04-05 07:41:27'), (5, 2, 4, 'Esse odit reiciendis eaque. Dolores enim quidem odit sequi tempore nobis ut necessitatibus. Et numquam doloribus commodi deserunt eius.\n\nCorrupti eum harum doloribus consequatur asperiores necessitatibus suscipit perspiciatis. Voluptas magni ab qui quia. Esse possimus aut quia ratione temporibus. Vel occaecati nulla dolore et eveniet corrupti sit.\n\nConsectetur aut vero ea architecto. Fugit assumenda enim minus blanditiis perspiciatis ab. Deleniti id impedit rem ex blanditiis.\n\nQuia placeat iusto est sapiente assumenda. Mollitia quisquam voluptatem quisquam doloremque. Explicabo commodi et iure aspernatur.\n\nCommodi qui nihil sunt ut suscipit facilis. Et ipsam dolorem autem eos sit odit modi modi.', 1, '2020-04-05 07:41:14', '2020-04-05 07:41:28'), (6, 2, 3, 'Modi et dolorum qui non. Delectus ut voluptates voluptatum voluptatem et modi. Qui fugit qui suscipit.\n\nSequi voluptatem facere omnis quod. Dolores aut voluptatem reprehenderit quae atque et consequuntur. Dignissimos quibusdam aspernatur autem nisi sapiente dolorem vel. Est totam nesciunt mollitia est.\n\nEst aut pariatur praesentium placeat tempore fugiat dolores. Et saepe praesentium asperiores voluptatibus hic fugit dolores. Sint veritatis consequatur quas dignissimos.\n\nReiciendis nemo commodi necessitatibus aliquam et ad maiores. Sint quisquam eos odit possimus in perspiciatis aut ipsam. Et officia architecto quis.\n\nConsequatur consequatur sint alias tempore commodi. Iure et repudiandae quisquam consequatur praesentium. Repellat perspiciatis vel non illo corporis. Enim omnis suscipit praesentium aut.', 0, '2020-04-05 07:41:14', '2020-04-05 07:41:28'), (7, 2, 1, 'Iste officiis necessitatibus qui qui sunt culpa culpa. Totam quo qui accusamus. Rem repellat voluptate deserunt maiores.\n\nExercitationem repellendus earum itaque sint tenetur quaerat id aliquam. Non vel molestiae ratione et. Voluptatem non repudiandae earum aut eaque quibusdam id iusto. In quisquam optio quod.\n\nVoluptatem repellendus molestiae ipsam assumenda. Alias odio culpa architecto commodi beatae et nostrum. Iure maxime aliquid id sequi. Neque eos hic consequatur nemo.\n\nPraesentium provident quo illum unde. Molestiae in praesentium cumque quo veritatis. Ducimus ut odit est culpa ipsum.', -1, '2020-04-05 07:41:14', '2020-04-05 07:41:28'), (8, 2, 5, 'Similique ut ea sequi aliquam. Necessitatibus dolorum omnis dolores nemo aperiam quidem. Dolores quo enim incidunt sequi temporibus qui qui.\n\nIn in tenetur distinctio quaerat. Quod sed numquam eveniet voluptatibus.\n\nExpedita saepe est sapiente omnis dolorem. Quia rerum qui assumenda sed quo in unde. Perferendis sed a alias unde voluptas voluptatibus. Repudiandae dolorem harum ut temporibus aliquam esse.\n\nUt architecto quis ut laboriosam sed dolorum aut. Quod molestiae velit quidem accusantium eos.', -1, '2020-04-05 07:41:14', '2020-04-05 07:41:28'), (9, 2, 4, 'In rerum earum vitae maxime et commodi provident. Dolorem vel tenetur rerum omnis ratione. Id eos consequuntur ea quia. Delectus hic quae omnis accusantium recusandae officiis.\n\nOmnis sunt tenetur illo veritatis quas. Quo ut aut maiores ea. Aut non et error reprehenderit delectus animi. Sit possimus excepturi fuga itaque possimus consectetur.\n\nEt nobis repellat officiis ut. Quas qui adipisci sit in autem. Repellat maxime exercitationem quia aspernatur quibusdam.', 1, '2020-04-05 07:41:14', '2020-04-05 07:41:29'), (10, 3, 5, 'Libero est debitis vel inventore porro quis. Veritatis rem aut harum deserunt. Fugit temporibus rem ut cum voluptas. Dolorem molestias omnis sed sit quo.\n\nAut porro voluptas vel nobis culpa illo soluta reprehenderit. Et qui voluptatibus sequi enim. Et velit porro eligendi nobis autem. Fugiat rerum sunt delectus consequatur sint laborum.\n\nVoluptatem et reprehenderit quia. Ut nesciunt autem asperiores dicta illum. Libero voluptates sunt eum officiis.\n\nQuam sunt porro qui et molestiae. Facilis eos repellat nobis labore. Quasi rerum quia ex.\n\nEt culpa qui et aut nesciunt rem laboriosam hic. Esse occaecati in est harum. Qui delectus enim sunt voluptatem praesentium dolorem quia. Sed maiores consectetur culpa aut sit natus. Ipsum molestiae delectus itaque fuga aut corporis consequatur.\n\nQuod veritatis aut dignissimos. Deserunt provident vel similique omnis consectetur necessitatibus. Nobis in perspiciatis qui tenetur quo sit dignissimos. Praesentium architecto qui perferendis porro. Id non iure consectetur nulla.\n\nEt nisi natus et labore totam. Nisi et est inventore cum velit nulla architecto exercitationem.', 1, '2020-04-05 07:41:14', '2020-04-05 07:41:29'), (11, 4, 4, 'Quod doloremque atque recusandae. Voluptatem veniam necessitatibus voluptatum numquam reiciendis vel et. Eos accusamus voluptas harum sit repellat.\n\nAsperiores et provident in. Excepturi nam et possimus impedit. Necessitatibus consectetur maiores velit eligendi quis repellendus. Ipsa voluptatum eum libero sapiente.\n\nVitae sit repudiandae explicabo ipsum. Ut qui odio porro repellat. Praesentium dolores quo corporis minima doloribus. Recusandae magni nobis impedit sit.', -1, '2020-04-05 07:41:14', '2020-04-05 07:41:29'), (12, 4, 4, 'Sint dolorem dicta consequatur est. Eos quisquam veniam id et asperiores. Cum repudiandae consequuntur magni et veniam.\n\nEt ducimus qui id ut qui assumenda perspiciatis. Id molestias tenetur error veniam deserunt. Necessitatibus fuga est quia earum sit deserunt.\n\nTempore quis ut laudantium consequatur inventore. Odio molestiae ipsum nihil omnis. Provident non facilis omnis dolorem quisquam.', 0, '2020-04-05 07:41:14', '2020-04-05 07:41:30'), (13, 5, 5, 'Debitis blanditiis dolorem ea doloremque. Rerum iusto rerum voluptatem eligendi tenetur. Sed facilis omnis veniam eum.\n\nPerspiciatis vel voluptas dolor voluptatibus illum. Ea est assumenda debitis qui quasi. Animi tempore dolores dolorem voluptatem maxime quia porro illo. Cumque ut aut unde rerum sit sapiente.\n\nSoluta incidunt fugiat quia similique. Nam nihil minima laudantium voluptatem asperiores natus. Quia saepe consequatur tenetur odio necessitatibus.\n\nNatus impedit eligendi placeat qui. Deserunt vitae placeat sed et et possimus repellendus. Tenetur iusto reprehenderit sed animi consequatur ipsa.\n\nRatione cumque pariatur eligendi porro libero. Magnam et atque illum est omnis. Suscipit mollitia placeat delectus cumque voluptatem. Ut quia maiores officia nihil sunt.\n\nQuos ipsa exercitationem soluta est qui nobis hic. Sunt voluptas dicta et. Quas sapiente itaque voluptatem ut modi eius non.\n\nRepudiandae magnam doloremque ex quas. Dolorem ut at sint qui dolorum velit. Corporis vero illo vitae. Vel similique et porro ipsam repellat eum.', -1, '2020-04-05 07:41:15', '2020-04-05 07:41:30'), (14, 6, 3, 'Hic enim recusandae voluptatum illum non laboriosam. Labore culpa rerum odit illum provident laudantium. Sed rerum facere voluptas ab sed sequi voluptatem. Magnam quam sit quam libero.\n\nLabore non et aut. Illo quibusdam ducimus et voluptates aut. Harum accusamus omnis id aut nulla. Doloremque enim incidunt quos tenetur.\n\nEnim et minus quia vel veritatis quia vero ipsum. Dignissimos delectus harum ipsum error et ut deserunt dolor. Vel corrupti nihil excepturi eum sequi. Et nam a qui aliquid consectetur aperiam omnis.\n\nProvident omnis iure ullam dignissimos id qui. Quae qui aliquid soluta aperiam omnis ut eaque. Consequatur iure rerum dolores quae et.\n\nEt ut ut vitae aut vel. Autem earum reprehenderit corrupti sed odio velit error. Totam sapiente molestiae expedita quia et eos.\n\nQuidem nam aut illum soluta ad illo et. Ut quasi iusto impedit quos.', -1, '2020-04-05 07:41:15', '2020-04-05 07:41:30'), (15, 6, 5, 'Ut molestiae et tempora. Maiores quo asperiores sequi animi et consequatur maxime. Dolores a et libero ducimus commodi temporibus numquam.\n\nEa minus est omnis quibusdam in eius ab omnis. Dicta omnis ipsum reiciendis et aut. Voluptatem esse quam laudantium nisi. Neque qui aperiam consequatur corrupti ducimus ducimus.\n\nQuo nostrum qui saepe ut blanditiis vitae. Aut libero laborum suscipit sunt quo asperiores. Qui optio iste sit in. Eius in reiciendis voluptas facilis quae perferendis.\n\nNatus alias ea placeat facilis nulla minima excepturi dolorum. Voluptatem omnis aut ut expedita facere. Et reiciendis autem laudantium accusantium omnis cupiditate ullam. Maiores nihil voluptatem perferendis qui qui.\n\nQuis aliquam est sint odit. Consequuntur quae velit porro nulla qui aut.', 0, '2020-04-05 07:41:15', '2020-04-05 07:41:30'), (16, 6, 5, 'Dignissimos repudiandae quo voluptatibus voluptatibus asperiores. Velit ad odit beatae. Quas provident consequuntur consequatur et sit blanditiis.\n\nMolestiae ad iste et enim doloribus sed. Excepturi et modi doloribus et qui accusantium. Et sit numquam veniam a possimus. Aspernatur error incidunt voluptas ipsum voluptate. Odit fugit labore et blanditiis.\n\nQui tempora est fugit ut voluptatem quia. Consequatur placeat quia impedit tempore commodi. Non ut est atque dolor consequatur occaecati. Est aspernatur veritatis autem quae. Ad ipsam natus atque aliquid.\n\nAssumenda voluptatem cumque porro quam molestiae consequatur. Ut tempora debitis eos sunt. Ut voluptatem saepe consequatur rerum excepturi aut. Incidunt exercitationem labore in rerum. Nihil rerum doloribus qui alias.', 1, '2020-04-05 07:41:15', '2020-04-05 07:41:30'), (17, 6, 4, 'Ipsum libero id saepe impedit fugit. Voluptas sit non vel iste consequatur blanditiis. Rerum quo quasi labore non voluptatem vel.\n\nExplicabo consequuntur temporibus dolores et. Reiciendis perspiciatis provident voluptatem ipsam est magnam. Sit aliquid nihil voluptatibus aliquam provident ea qui.\n\nRerum assumenda cupiditate maxime iure in est hic aspernatur. Molestiae quia sunt natus sed magnam. Aperiam voluptatem doloremque fuga autem qui mollitia. Alias eius aut eos neque.\n\nFuga numquam molestiae officiis expedita est. Voluptatem sint culpa sed iure est perspiciatis. Libero quos quasi fugit temporibus reprehenderit molestiae adipisci.', 2, '2020-04-05 07:41:15', '2020-04-05 07:41:31'), (18, 7, 3, 'Perferendis totam molestias ad temporibus voluptatem officia architecto. Quia dolores blanditiis aut animi sit. Incidunt sit esse dolorum iure quibusdam architecto.\n\nRecusandae est possimus quaerat voluptatem rem est odit cum. Autem id neque ab. Sequi dolorem recusandae accusamus est similique.\n\nNesciunt occaecati non in iste et. Nostrum quam optio quis qui sunt quod. Magnam facere consectetur expedita modi accusantium voluptatibus iure a.\n\nVoluptatum fuga sint cumque natus. Aut vitae nam nisi in dolorem. Similique tenetur repellat debitis laudantium. Est voluptatem nulla et consequatur quas.\n\nOccaecati qui quo sapiente et. Unde pariatur aut voluptatibus ad et sint. Voluptates aut dignissimos ipsum dignissimos officiis atque.\n\nVelit quo dolor est adipisci. Qui numquam omnis vitae nisi commodi. Nemo est consectetur est voluptatibus aut voluptas. Et dolores odio voluptas.\n\nOptio harum odit blanditiis. Voluptatem voluptate sit facere libero eligendi officiis. Accusamus hic sequi nesciunt corporis. Vel nemo distinctio quaerat voluptatem doloribus.', 3, '2020-04-05 07:41:15', '2020-04-05 07:41:31'), (19, 7, 4, 'Earum hic sit amet. Repudiandae molestias magni molestiae reprehenderit.\n\nVoluptatem consequuntur aliquam corporis quidem et magnam. Est voluptatem quod hic at ab expedita quam.\n\nIpsam nulla culpa qui fugit non laudantium. Nobis vel rerum expedita minima quia. Quibusdam dolorem quam illum error omnis et in. Qui sed repudiandae laborum sint aut.\n\nNumquam asperiores enim unde expedita cumque ducimus. Voluptatem expedita rerum nihil incidunt iusto aut. Rerum animi voluptas explicabo dolorum aliquid ea dolor.\n\nEt fugit est voluptatem officia consequatur. Magnam esse corporis non. Corporis consequatur animi beatae et iusto.\n\nDucimus molestias soluta earum iste. Culpa doloribus quis ut est ipsa. Ut molestiae omnis officiis dolor explicabo culpa nam.', 2, '2020-04-05 07:41:15', '2020-04-05 07:41:31'), (20, 7, 2, 'Et vitae et minus et. Et iusto nulla illo necessitatibus nihil ad. Iure eaque asperiores consectetur asperiores enim nostrum voluptas.\n\nNihil neque officia quia. Modi eius voluptatibus eos est necessitatibus beatae est perferendis. Sed delectus sapiente ut et nostrum aliquam alias. Nam voluptatem corrupti et occaecati.\n\nLaborum dolor et dolores perspiciatis eos. Libero tenetur assumenda molestiae corrupti delectus quae. Nemo sapiente quibusdam est est.\n\nSoluta quo mollitia sunt sit nesciunt ut. Eos cumque adipisci modi ut ex consequatur. Sit non aperiam minus doloribus accusamus quibusdam nulla.', -1, '2020-04-05 07:41:16', '2020-04-05 07:41:32'), (21, 7, 5, 'Molestias ad repellendus veniam quo. Atque molestias delectus esse at vitae nihil. Omnis earum eveniet qui cupiditate voluptas ut vel.\n\nEx quis sed ut officia ullam vel. Labore aut non sapiente cumque reprehenderit qui eos. Minima nemo aut laborum porro.\n\nUllam ipsum sit non praesentium. Sit debitis voluptatibus enim. Qui architecto deleniti est quia itaque culpa rerum officiis. Quasi quaerat id dolor placeat eos nesciunt et tenetur.\n\nQui fugiat ea illo aliquid. Quis omnis sed quaerat omnis. Expedita vero doloribus magnam laudantium nesciunt. Ullam aut consectetur non aspernatur beatae nisi.\n\nRem quis porro saepe. Nesciunt voluptatem corporis dolores qui doloribus ea totam vitae. Quia dolore totam voluptatum ut eos error. Soluta quia odit at magni quia similique aspernatur.\n\nItaque dolorem magni eaque neque enim. Reiciendis vel autem atque asperiores commodi sit consequatur. Placeat aut odio aut sit rerum nihil qui cupiditate. Sed dolor quo atque rerum quis aperiam cupiditate.\n\nEt dolor qui id iusto iure ipsum atque. Laudantium voluptatem aspernatur inventore. Voluptatum quia veritatis non ut accusantium doloremque recusandae.', 1, '2020-04-05 07:41:16', '2020-04-05 07:41:32'), (22, 8, 3, 'Eos ipsam sit at qui. Aut quia velit enim ratione est et. Voluptas soluta voluptatem debitis non.\n\nPerspiciatis reprehenderit ab facilis dolores. Assumenda in temporibus officiis rerum odit. Ut minus nam sequi ut pariatur quibusdam odio.\n\nDeleniti ut autem pariatur nesciunt quis. Velit ducimus iste dignissimos incidunt velit vero.', 0, '2020-04-05 07:41:16', '2020-04-05 07:41:32'), (23, 8, 4, 'Aliquam debitis et non qui pariatur impedit. Tenetur autem est quia eos sit et. Voluptatem velit nesciunt reiciendis veniam quod dignissimos. Et adipisci facere impedit et qui enim nam.\n\nQuisquam qui sit ipsam qui corporis. Quis repudiandae modi dolorem velit dicta omnis et modi. Sed voluptatibus ut mollitia est.\n\nEveniet autem omnis est in doloremque. Tenetur et quas sequi architecto et nesciunt rem.\n\nEt tempore ad in ut. Non incidunt mollitia eum voluptatem quos explicabo veritatis. Minima maiores beatae sunt sunt et. Quia harum ut enim voluptas. Beatae odio perspiciatis consequatur qui.\n\nEt recusandae recusandae possimus quia rerum. Eius quasi deserunt eius eligendi. Sint reprehenderit maiores quis consequatur harum reiciendis sint nobis. Incidunt sit eaque a voluptatem et dolorem.\n\nQuod voluptas at necessitatibus accusantium et est enim. Est nihil necessitatibus amet sint omnis quia nemo corrupti. Adipisci laborum ipsum molestias.', 0, '2020-04-05 07:41:16', '2020-04-05 07:41:33'), (24, 8, 3, 'Distinctio aspernatur quibusdam aut laudantium molestiae. Rerum cum ut illum. Hic qui a nisi natus assumenda sit unde. Quaerat voluptas nesciunt voluptatem iste.\n\nQuia quisquam praesentium natus vel explicabo laboriosam ut. Voluptas est non quasi odio commodi nihil quod aliquid.\n\nAccusantium eaque ut possimus delectus odio. Et est at voluptatem omnis accusantium consequuntur. Corrupti repudiandae velit iusto neque neque quia. Voluptas voluptatum dolor doloribus.\n\nNeque molestiae molestiae consequatur temporibus consequatur aperiam eius. Unde non nemo repudiandae modi. Distinctio beatae et exercitationem nostrum nam eaque.\n\nDeleniti voluptas voluptatem nesciunt nostrum ab provident. Omnis rerum voluptate molestiae ipsum. Neque veniam quis qui facilis. Nesciunt est repellat vero dicta.\n\nUt quis eaque eveniet sit. Eveniet quisquam voluptatem excepturi magnam. Et debitis aut dolore.\n\nPraesentium porro mollitia quia maxime. Nisi unde possimus consequuntur voluptate neque sit unde. Molestiae aut quibusdam sapiente consequatur sit nesciunt. Et dicta voluptatum rerum vitae pariatur rerum reiciendis. Incidunt cum quasi optio doloribus voluptatibus.', -1, '2020-04-05 07:41:16', '2020-04-05 07:41:33'), (25, 8, 5, 'Exercitationem consequuntur et a quia dolor. Autem mollitia quia delectus sint blanditiis.\n\nAb tempore doloribus natus sunt. Excepturi sit ut esse velit quis. Voluptatem iste non sed asperiores tempora at excepturi. Esse non facilis maxime voluptate impedit.\n\nOptio dolorum ab assumenda. Pariatur non error similique. Temporibus impedit ipsum fugiat harum assumenda est. Voluptas labore qui voluptas laboriosam.', -1, '2020-04-05 07:41:16', '2020-04-05 07:41:33'), (26, 8, 2, 'Deserunt ipsa dolores minima tenetur omnis. Ut nulla neque et iste labore magni veniam. Quia sit aliquam nostrum vero. Enim unde recusandae tempore consequuntur amet pariatur dolores.\n\nPorro accusantium ea quis quo. Qui eos non eaque ullam qui. Ipsa et accusantium quisquam magni fugit.\n\nAliquid autem qui qui aut. Perspiciatis maxime animi maxime. Vel vitae molestiae autem quidem eligendi cum. Consectetur non quod quas sapiente aliquid et.\n\nAnimi vitae saepe doloribus vel vero ad aut. Qui atque sint quo asperiores est neque sed. Molestiae error facere blanditiis odit autem.', 0, '2020-04-05 07:41:16', '2020-04-05 07:41:33'), (27, 9, 5, 'Provident expedita sit autem doloribus necessitatibus. Quasi omnis omnis ut ipsa adipisci est ut. Officiis quam omnis modi voluptate non.\n\nSint numquam et occaecati vitae doloremque commodi. Aut consequuntur adipisci ratione rerum. Rerum similique incidunt et porro voluptates.\n\nOptio voluptas cum est tempore. Dolorem rerum qui dolor.\n\nBeatae exercitationem iure quis officia qui pariatur explicabo et. Et sit qui consequuntur et quos. Rem esse autem totam corrupti accusantium. Non nisi neque quis ut.', 0, '2020-04-05 07:41:16', '2020-04-05 07:41:34'), (28, 10, 5, 'Cupiditate dolorem corporis totam dolor. Assumenda officia magni dolor quia ea cumque. Illo totam ratione et sit reiciendis sit repudiandae eaque.\n\nAliquid optio repellendus in nihil et veniam quod. Vitae adipisci voluptatem occaecati expedita similique est eos. Dolorum aut quo magnam recusandae assumenda nam est voluptatem. Facilis voluptate odit tempore occaecati.\n\nOdit unde pariatur qui expedita est veritatis. Velit a eius excepturi quis nulla. Ab ea sapiente eum omnis. Architecto dolorum et doloremque dolore natus ut quia.\n\nAmet reprehenderit vero aut est consequuntur. Quas ea dolore qui dolorum. Assumenda quas doloremque libero architecto.\n\nOfficia consequatur repellendus aperiam aliquam ut est illo distinctio. Quas numquam numquam quidem sit ex consequatur minima. Omnis alias quia sint ratione excepturi sed.\n\nAb nostrum eum quaerat impedit alias assumenda autem. Sed illum optio minima et odit expedita animi. Quia vel et aut possimus non. Quos sapiente saepe itaque nostrum dolores.\n\nPorro porro porro aut. Ut ipsa ut est aut porro in. Ut quidem ut et at. Mollitia molestias et laborum voluptas dolores quos.', 0, '2020-04-05 07:41:16', '2020-04-05 07:41:34'), (29, 10, 4, 'Optio est facere molestiae odit et et velit sint. Ut et tempora pariatur aut modi laborum id unde. Et voluptate animi sit ratione architecto qui.\n\nQuod rerum dignissimos consectetur eos quam omnis iusto. Ut aut dolor est est ratione in architecto nostrum. Nemo vel quo porro necessitatibus nemo. Expedita ad aut iusto eum consequuntur quibusdam laborum.\n\nId labore voluptas nam ea eveniet iusto sunt. Voluptate pariatur cum ducimus consectetur iste. Eligendi velit nemo omnis illum maxime adipisci. Dolorum quam consequatur et eum dignissimos non.\n\nAccusantium quis deserunt omnis suscipit natus. Non et deserunt repellat optio. Enim occaecati aut sint accusantium. Asperiores velit ut vitae sed molestias sed.', 1, '2020-04-05 07:41:16', '2020-04-05 07:41:34'), (30, 10, 1, 'Et tempore praesentium est ipsa. Consectetur eligendi asperiores eum amet quas omnis. Consequatur facere praesentium et quia quasi facere incidunt. Quo porro ea quis quo cumque.\n\nDelectus labore qui maiores est vitae sequi repellat placeat. Vitae alias sint ullam temporibus quaerat alias. Perspiciatis qui necessitatibus id ea sed cum.\n\nAt nulla cupiditate quibusdam odit neque praesentium quidem. Et voluptas quaerat voluptate ratione saepe. Facere voluptatum accusamus debitis ut quia nesciunt recusandae illo. Itaque ullam repudiandae non.\n\nAmet fuga excepturi aut ut non asperiores. Non doloribus nihil sunt dolores distinctio. Soluta eum et velit debitis quo.', 2, '2020-04-05 07:41:17', '2020-04-05 07:41:35'), (31, 10, 3, 'Sequi eos incidunt minima beatae porro. Tempore et provident nihil molestiae. Rerum et rem inventore ea pariatur. Velit fugiat voluptate at quisquam autem mollitia eos.\n\nConsectetur facilis quasi id enim tempora. Dolores nesciunt asperiores quo voluptas rem officia. Sit officia eum explicabo. Aperiam dignissimos a sunt aspernatur architecto. Et iste ut culpa.\n\nTotam optio ut voluptatem sed et. Rerum ex aspernatur voluptatem maiores nihil doloribus vel. Ipsum corporis qui ea eligendi in omnis.\n\nOfficia sint voluptatem voluptates quod nulla voluptas perferendis nesciunt. Eius qui et a distinctio adipisci. Consectetur modi error non illum tempore. Tempore inventore culpa fugiat ad porro suscipit.\n\nArchitecto eligendi sed sed quis aut. Voluptas modi autem animi sit quo. Beatae sunt tempore iusto facilis.\n\nQuam provident autem fugiat expedita unde exercitationem omnis. Repellendus ex et impedit. Rerum illum harum tempore. Aliquid et sit ullam numquam sed animi libero.\n\nEt optio quia id magni libero aut consectetur molestiae. Eius aut rerum ullam consequatur placeat vero. Atque autem quia qui sit et eos.', 0, '2020-04-05 07:41:17', '2020-04-05 07:41:35'), (32, 10, 5, 'Neque voluptatem sunt pariatur natus cum doloribus. Distinctio voluptatem perferendis et non. Quidem quasi architecto accusamus sunt eligendi. Tenetur ut qui ab laboriosam ut laudantium. Veniam sint sint dolor molestias qui doloribus.\n\nRerum hic assumenda sint eius quis eos. Modi vel doloremque eum numquam vel ab. Amet exercitationem perspiciatis ex ut error omnis omnis.\n\nNon aut ut in earum consequatur eum ut. Quam eum ut omnis debitis. Amet culpa necessitatibus eum.\n\nMolestias assumenda et debitis et quia hic animi. Sed omnis harum dolorum eum. Ab ratione et esse. Consequuntur sequi aut beatae et modi voluptas.\n\nEt qui et sint occaecati quisquam animi. Error reiciendis magnam suscipit voluptas quia temporibus voluptatem. Possimus nemo itaque nihil commodi provident et. Non et est incidunt fuga consequatur quaerat.', -1, '2020-04-05 07:41:17', '2020-04-05 07:41:35'), (33, 11, 1, 'Quia cum quisquam dolores ipsum nesciunt corrupti minima dicta. Sint et ea quasi culpa ex ab minima. Nam sunt hic nihil est.\n\nAmet nemo quos cumque odio. Odit rerum maxime dolore quis eligendi dicta. Autem iste vel ipsum vel sint non.\n\nAperiam eos voluptatibus illo architecto. Perspiciatis eaque dolor aut id iste expedita.\n\nAd nostrum illo est. Sit quia mollitia rem odit natus. Consectetur blanditiis enim aliquam voluptas id voluptatibus.\n\nMinus hic vitae animi. Molestiae dolores neque reprehenderit quidem.\n\nOfficiis voluptatem mollitia ea delectus qui illum. A ullam at soluta fuga aut quis qui. Repellendus et deserunt ea fugit cupiditate itaque.\n\nDolore modi est culpa fuga dolorem quam nulla. Vel velit minima eos dolorem eligendi quo. Magni voluptas officiis omnis labore neque ut. Exercitationem sapiente molestias dolore ab ipsa qui sit.', 0, '2020-04-05 07:41:17', '2020-04-05 07:41:35'), (34, 11, 3, 'Temporibus doloribus veniam nostrum id. Nemo nam ipsum deserunt adipisci. Velit aliquid aliquam accusantium fugit ipsum temporibus ea. Voluptas maxime voluptates esse nesciunt.\n\nEnim ut ipsum voluptatem repudiandae. Qui nihil iste molestiae vero minima perspiciatis doloremque perferendis. Id consequuntur molestiae minima distinctio id maxime.\n\nVoluptates quidem corporis aut deserunt. Et non iste voluptatem pariatur cupiditate natus. Pariatur consequatur repellendus est illo. Magnam quos laborum commodi non laudantium.\n\nDolores atque voluptatem quae velit non ratione amet. Totam debitis quibusdam rerum odio aut. Qui sed quod maxime culpa reiciendis debitis.\n\nIste voluptatem sequi adipisci ut voluptatibus laudantium delectus. Error officiis quae ut ullam. Quisquam animi labore quam est expedita natus consequuntur. Modi qui non id iusto qui sint.', 1, '2020-04-05 07:41:17', '2020-04-05 07:41:35'), (35, 11, 2, 'Ea explicabo natus quisquam. Soluta ex et mollitia sint officia fugit. Id aut consectetur sint porro. Libero quasi et enim.\n\nDolorem eum quis illo. Voluptas et tempora voluptatum eveniet. Commodi illum nihil quos dolores qui eum nam quisquam.\n\nPossimus et voluptas cumque repellat consequuntur. Incidunt harum quos autem dolores et. Quisquam veniam placeat iure qui ex ipsa. Sunt dolores esse rem.\n\nOfficiis quia minus quis nihil voluptatum sit quae labore. Aperiam labore harum illo consectetur.', 1, '2020-04-05 07:41:17', '2020-04-05 07:41:35'), (36, 11, 3, 'Non impedit nemo voluptatem quod consequatur. Mollitia beatae voluptas et est ad. Repellat amet velit dignissimos a vel optio provident.\n\nDignissimos ad laboriosam aliquam fugit. Quas est et eligendi sint sunt culpa autem iusto. Repellendus qui sed atque aut totam quam eum. Voluptatem sapiente aut voluptatum.\n\nConsectetur deserunt repellendus iste. Minima eaque doloremque voluptatem qui.', -3, '2020-04-05 07:41:17', '2020-04-05 07:41:36'), (37, 12, 4, 'Aut voluptas quia maxime qui. Sequi et qui quia minima consequatur repudiandae. Corrupti perferendis a autem provident velit.\n\nLaudantium nihil ut minus maxime illum. Blanditiis perspiciatis aliquid reiciendis minima id qui. Quibusdam quam vero enim accusantium aliquam sequi omnis. Minus labore laborum voluptas possimus sint praesentium ducimus.\n\nSunt voluptas saepe quis enim voluptas animi. Omnis explicabo maxime officiis autem. Sint vitae eum cupiditate dolorum. Ut minus et soluta quidem illum adipisci velit.\n\nPorro doloremque est ea eum aut commodi. Qui vitae cum molestias nostrum. Unde commodi labore dolore maxime harum quod.', 1, '2020-04-05 07:41:18', '2020-04-05 07:41:36'), (38, 13, 1, 'Reprehenderit eius rerum animi sit incidunt quod distinctio. Nobis qui veniam illo molestias in recusandae optio animi. Qui consequatur optio id voluptas.\n\nAccusantium doloremque in officia ut. Voluptatem et corporis commodi quae odit ratione iste. Temporibus unde ipsum nulla possimus fugiat.\n\nDicta neque corrupti et sit. Ea praesentium inventore et incidunt qui.\n\nDolorem omnis quis culpa nisi. Cum est sed esse rerum eum laboriosam.\n\nAsperiores praesentium ea est quae. Enim delectus sit tempore ipsa. Eius architecto sed ea neque quia vitae. Sapiente quam non commodi doloribus asperiores fugit consequatur.\n\nOmnis nisi voluptates ipsam quia deserunt qui. Qui aliquid qui omnis perspiciatis repellendus sed. Magnam accusamus molestiae accusantium reiciendis ab eaque.\n\nQui eius voluptates sint accusantium. Qui quo placeat ducimus neque quae et. Et nesciunt ullam est blanditiis adipisci eveniet. Velit nihil eos sit temporibus quod nemo. Sequi quibusdam iste facere aspernatur.', 1, '2020-04-05 07:41:18', '2020-04-05 07:41:36'), (39, 13, 3, 'Quae doloremque modi voluptatem ab corrupti alias architecto laboriosam. Sit qui voluptas rerum accusamus iure. Neque pariatur et ea omnis.\n\nUnde aspernatur et maiores ut et totam exercitationem. Maiores exercitationem sed est consequatur corporis aut. Quia voluptatem excepturi necessitatibus debitis.\n\nProvident molestiae qui repellat fugit est quia in. Cupiditate dolorem sit adipisci iure. Voluptatibus autem officia ad incidunt beatae similique quod. Exercitationem suscipit necessitatibus molestiae quaerat.\n\nRecusandae fuga sequi qui minima. Qui neque aspernatur aut eum nobis. Nisi distinctio deserunt labore enim et tenetur.\n\nEst enim eligendi voluptatum rerum. Voluptatem ipsam aut nulla fugiat eum iste deleniti. Praesentium aut voluptatem consequuntur et. Enim sint voluptatibus voluptatem quis reprehenderit.\n\nVelit et suscipit voluptatum et ea odit. Necessitatibus eos eveniet repellat aut. Eveniet qui et aliquam repellat laboriosam temporibus. Esse quidem autem cum rerum perferendis qui.\n\nAut voluptatibus veniam et minima. Architecto optio recusandae maxime excepturi. Voluptas nisi amet distinctio occaecati deleniti ipsa quia voluptatem. Provident minus velit corporis omnis voluptas fuga sit soluta.', 0, '2020-04-05 07:41:18', '2020-04-05 07:41:37'), (40, 14, 5, 'Repellendus exercitationem beatae id necessitatibus voluptas rem. Sint id aut possimus. Illum dolorem aperiam cumque quod pariatur quas. Voluptas expedita quasi rem libero.\n\nIpsum hic consequuntur autem atque consequuntur quis. Ut et animi omnis enim molestias qui eius. Eligendi voluptas culpa corporis quia nam et sit.\n\nEligendi ea eveniet harum corrupti eum exercitationem ex. Occaecati natus unde voluptates. Ipsam sit perferendis eos quis labore hic.', 0, '2020-04-05 07:41:18', '2020-04-05 07:41:37'), (41, 14, 4, 'Fugit voluptatum rerum vitae ullam dolor dolorem sapiente. Dolorem ipsum nulla est temporibus nostrum. Laboriosam incidunt necessitatibus a officia. Cumque cumque quisquam et.\n\nCommodi ipsa magnam maiores cupiditate eligendi ea. Inventore sed molestias necessitatibus iusto voluptatibus consectetur iste. Incidunt quas culpa quis et dolor totam iure sint.\n\nPraesentium esse voluptates reiciendis aut sit illum quod unde. Voluptatem deserunt optio numquam consequuntur quasi odio aut. Animi eligendi laboriosam quia molestiae molestiae itaque magni velit.\n\nEst recusandae sit voluptatibus iusto. Velit asperiores cumque voluptatum. Quis maiores est voluptate sint sequi qui blanditiis.\n\nVoluptates assumenda et inventore repudiandae placeat. Incidunt aliquid eligendi occaecati error. Vel repellat dicta commodi vel quo veniam neque. Id et cum sapiente enim qui fugit sunt.', 0, '2020-04-05 07:41:18', '2020-04-05 07:41:37'), (42, 15, 1, 'Est et magnam minus quia et. Sunt vel maxime explicabo quia non natus a. Qui dolor quo praesentium sit error esse. Ea provident mollitia enim ut omnis fugit. Et rerum illum quos eligendi quod est ut.\n\nAtque minus omnis dolores laboriosam eaque sunt maiores totam. Quia doloremque sint impedit odit animi quis. Dignissimos fugit saepe officiis a sed. Laboriosam a modi dolores unde quam sit.\n\nVoluptatibus similique voluptatum voluptas blanditiis necessitatibus. Temporibus maxime repellat sit et. Ea iste consequatur asperiores facilis corporis. Iure corporis fugit excepturi exercitationem qui et.\n\nAt odit omnis sint aliquam dolorem accusamus dignissimos. Sit nemo autem delectus pariatur nam quasi. Optio non in deleniti molestiae corporis qui ratione.\n\nEsse iure laboriosam facere fugiat. Aliquid veritatis consectetur est quos provident necessitatibus. Velit voluptates et facilis alias esse saepe. Et quisquam ea quaerat praesentium. Nostrum dolores nihil fugit et vitae eveniet voluptas.', -2, '2020-04-05 07:41:18', '2020-04-05 07:41:37'), (43, 15, 2, 'Velit sapiente quo autem ut laborum eius vitae et. Aliquid rerum veritatis inventore est cupiditate ipsum. Nihil exercitationem beatae enim voluptatibus. Quia ut magnam in dolorum vero quisquam soluta.\n\nUllam debitis quia qui sunt pariatur labore velit laboriosam. Qui iste officiis a iste debitis ut excepturi. Libero similique et aut non dolorem soluta nihil. Asperiores ut perferendis corporis doloribus provident corrupti. Sunt et et quidem sed.\n\nMagni tenetur qui aperiam nisi velit. Commodi veniam deleniti magni necessitatibus sapiente. Fugit voluptas sunt debitis reprehenderit ducimus. Harum amet aut iure ad sit dolore autem totam.\n\nHic ex exercitationem cumque nulla. Voluptatem ullam totam animi libero quia fuga ex. Facilis enim est eum quisquam consectetur laborum quo. Quasi fugiat minima expedita sunt quas laboriosam sit. Veritatis quaerat corporis adipisci et qui.\n\nHic maiores laboriosam est. Nisi ea quo quod natus quia. Qui ut possimus est molestias pariatur impedit magni ea. Omnis adipisci enim repellat vero. Nihil ratione soluta dolorem eveniet id veritatis asperiores facere.\n\nIpsa et nihil quo sint distinctio sint. Harum nulla sit tenetur itaque quam a. Vel blanditiis harum sapiente dolor. Voluptatem qui tempora quaerat.\n\nLaborum nam voluptatibus et ut quidem in. Consequatur officiis consequatur quod non. Quia nobis praesentium odit debitis. Quia odit iusto enim sit repellendus error nemo.', 2, '2020-04-05 07:41:18', '2020-04-05 07:41:38'), (44, 15, 2, 'Aperiam eum est officiis aut. Ut est non perspiciatis soluta. Suscipit est odio iusto dolorem. Quidem vitae quibusdam et dolores.\n\nNeque velit vel pariatur odit consequatur consequatur earum. Numquam repellendus aut rerum quidem molestiae. Praesentium sit quis ullam a.\n\nEst facere cupiditate modi impedit veritatis sint. In accusantium eveniet sit accusantium. Et aut expedita animi. Corrupti illo doloribus odio in eos ut possimus.', -1, '2020-04-05 07:41:18', '2020-04-05 07:41:38'), (45, 15, 1, 'Necessitatibus sint labore inventore et sunt in ut. Cupiditate nemo quisquam et ullam dolores illo aliquam. Atque quo ut consequatur iusto. Ipsa sit voluptatem dolorem vitae animi tenetur.\n\nQui ad ducimus aliquid ea cum qui. Minus doloribus magnam fugit dolorum vero expedita maxime. Id dicta numquam placeat. Id id aut eos officia.\n\nNobis id cum corrupti et et sequi rerum qui. Delectus dolores quis porro voluptas ducimus quo. Deleniti necessitatibus officia recusandae est voluptates at quia.\n\nAccusamus repellendus excepturi reprehenderit laborum fugit molestias. Sint quis molestiae laboriosam incidunt nostrum. Voluptatem eum nisi non sequi corrupti sit. Itaque et rerum eum nesciunt.\n\nQuam odio nostrum nulla sunt eius sit numquam. Quod sit fugiat praesentium velit non consequatur.\n\nTemporibus distinctio nihil sunt natus enim suscipit porro. Ut enim expedita facere doloribus similique voluptas.\n\nEum laborum fugiat quia reiciendis sit enim. Voluptatem autem expedita asperiores.', 2, '2020-04-05 07:41:19', '2020-04-05 07:41:38'), (46, 15, 1, 'Et corporis voluptate non tempore suscipit recusandae. Doloribus nemo nemo vero eius magnam. Ut ducimus commodi animi corrupti possimus.\n\nNihil quis dicta repellat nostrum quo ducimus. Eaque deserunt sed assumenda nulla consequatur facilis. Autem voluptas praesentium rem neque excepturi qui. Dicta rerum et error pariatur nisi sint.\n\nMinus quis accusamus dolores ab. Aut culpa rem optio libero dignissimos. Magnam sed nemo qui exercitationem est amet esse dolor. Sed omnis maiores quis quia voluptatem ex sit. Veritatis nesciunt doloremque itaque sint.', 2, '2020-04-05 07:41:19', '2020-04-05 07:41:38'), (47, 16, 1, 'Eius natus harum fugit nihil. Et possimus ut maxime sit. Ipsam numquam quae aut ut. Error dolor ut dolorem nemo.\n\nDolor vero aut velit illo illum. Quasi molestiae illum at qui itaque. Ut ea impedit vitae error ut fugiat. Aut nemo vel reprehenderit dolores maxime modi.\n\nNihil eius et et molestiae excepturi alias atque. Quasi iusto vel aut autem atque. Est minus et velit delectus.\n\nOmnis ipsam doloribus sed sed blanditiis ullam nihil. Quae dolores explicabo eum nulla nemo. Eius suscipit et aperiam nemo id pariatur.\n\nFuga ratione et asperiores dolorem id. Voluptatem et nostrum placeat necessitatibus. Aperiam facere similique quia eligendi illum quidem quo. Blanditiis aut reprehenderit autem reprehenderit accusamus in.\n\nDelectus reiciendis dolores labore occaecati. Quia consequatur ullam et ut. Quia ut quo non non inventore officia ab.\n\nOdit ratione quam qui ut numquam animi nesciunt. Corporis impedit quis rerum consequatur. Omnis nihil non expedita dolorem consequatur pariatur saepe.', 2, '2020-04-05 07:41:19', '2020-04-05 07:41:39'), (48, 16, 4, 'Explicabo non natus iure ullam voluptatem. Iure quisquam occaecati blanditiis hic voluptate. Aut quia inventore sed eum. Velit iure aut assumenda possimus est autem id animi. Et voluptas molestias nulla repudiandae labore quo.\n\nUt perferendis quo harum culpa. Quasi est dolorem non explicabo autem voluptas ut voluptatem. Aut cupiditate possimus ut consectetur rerum nemo omnis.\n\nOmnis magnam magni fugiat sed ratione corporis blanditiis error. Similique quia repellendus non maxime. Quo totam asperiores ut dolore sed dolores. Et omnis similique eum et. Adipisci saepe eaque ut.\n\nQuis qui laboriosam voluptas ex debitis quo rerum. Et sequi rerum aliquam iste dolorem nemo. Vel et molestiae officiis et quae assumenda veniam at. Molestias perspiciatis eaque voluptas sed dolorem quibusdam.\n\nLibero quia ut quasi sapiente voluptatum earum. Sit et eius nihil dolor. Id consectetur et sunt magnam numquam. Itaque reiciendis fugit suscipit rerum aliquam deserunt iusto.\n\nNumquam consequatur cum minus sapiente. Possimus beatae mollitia eos in minus aliquid.', -1, '2020-04-05 07:41:19', '2020-04-05 07:41:39'), (49, 17, 1, 'Molestias unde non rem voluptate et soluta. Iure occaecati eum nostrum qui.\n\nQuis est quia nobis dolorem culpa. Illo vero quaerat et velit. Voluptatem culpa ex adipisci repudiandae sed. Omnis iste possimus sunt.\n\nMolestiae neque voluptas voluptas quo. Voluptatem corrupti voluptate facere adipisci nihil. Rerum nam voluptatum minima illum veniam eius. Nobis qui mollitia et qui animi aut ipsa.\n\nSimilique aut recusandae ut laborum beatae. Ad autem ea et nostrum. Corporis eius et repudiandae illum corporis veritatis. Nesciunt facere alias est earum temporibus voluptatem est.\n\nNumquam sint quasi consequatur maxime. Eos accusamus cum maxime nihil provident. Exercitationem sit dolorem dolorem maiores autem nostrum tenetur. Aut dolor velit non est sit eius.', 3, '2020-04-05 07:41:19', '2020-04-05 07:41:39'), (50, 17, 4, 'Esse impedit fuga laboriosam rerum consequatur. Asperiores dolore aliquam neque quasi sunt. Impedit expedita molestias quisquam. Ut ab consequatur et quia id.\n\nQui aut rerum ipsum dignissimos eum ex. Id odio distinctio beatae id minima animi et. Quis facere reprehenderit ratione non.\n\nTempora molestias dolorem adipisci mollitia. Aspernatur magnam nisi deleniti sit rem. Voluptates nulla autem quo culpa. At quisquam reiciendis reprehenderit vel. Molestias vitae inventore impedit assumenda nesciunt.', 1, '2020-04-05 07:41:19', '2020-04-05 07:41:40'), (51, 17, 4, 'Libero facilis non qui in. Laudantium sapiente deleniti reiciendis velit. Et autem ratione numquam provident excepturi ut. Sunt est cum libero repellendus sed.\n\nAperiam quia fugiat aut eveniet vero. Aut et expedita et sed natus. In vitae quaerat explicabo soluta rerum ex et.\n\nLaboriosam modi et qui cumque dolor distinctio ipsa. Animi autem asperiores non explicabo aliquid. Repellendus eum autem omnis ut aut nobis. Inventore alias et ratione nemo dolorem sunt.', 1, '2020-04-05 07:41:19', '2020-04-05 07:41:40'), (52, 17, 1, 'Vitae cupiditate sit fugiat temporibus quidem. Quo sapiente repellat aliquam vel voluptatum officiis. Dolore voluptatem et deserunt dolor quae mollitia. Est suscipit tempora accusamus aut.\n\nDoloribus corrupti quasi quisquam nihil molestiae illo dolor. Doloremque culpa ipsam rerum ullam. Temporibus architecto facilis adipisci.\n\nQuis saepe sed nihil nam amet quidem. Reiciendis neque modi est suscipit eos. Provident qui nobis dolor facilis officiis voluptatem qui eveniet. Laborum et dolores aut quidem reprehenderit.', -1, '2020-04-05 07:41:19', '2020-04-05 07:41:40'), (53, 17, 2, 'Numquam architecto culpa magni fugiat. Aliquam ut repudiandae dolorem accusamus aliquam.\n\nCulpa repudiandae voluptates sit quibusdam facilis qui maiores. Optio in molestias eum dolor unde ut. Aut ipsam vel fugit amet vel ea explicabo culpa. Tempore maxime tempora blanditiis dolorum eligendi ipsum dolor ducimus.\n\nFuga consequatur atque culpa cum. Magnam ipsum ipsum dolorem sunt doloremque. Sit magnam eaque eum in illum natus.\n\nIn fugit deleniti porro qui velit et. Iste et rerum quibusdam numquam quia vel velit voluptates.\n\nIusto sit cumque corrupti nihil enim corrupti. Quis vero pariatur ut numquam. Ipsam voluptatem vel quo architecto. Vitae aut vel quae numquam.\n\nVoluptatem rerum quo voluptas dolor sunt veritatis. Commodi delectus eum ullam assumenda et. Qui non nostrum voluptates illo temporibus eum voluptatum.\n\nSit quae voluptatem assumenda consequatur qui voluptas dolores. Delectus rerum aut quos eos. Assumenda cupiditate ut nemo eos. Sapiente ipsam et autem numquam repellendus.', -3, '2020-04-05 07:41:19', '2020-04-05 07:41:41'), (54, 18, 2, 'Est id qui unde velit. Sunt et iusto nobis consequatur ipsam veritatis quas quibusdam. Aut et et aspernatur eos cum ducimus omnis. Tempore eos asperiores fuga quod.\n\nSit earum et assumenda illo sit. Laboriosam quae minima in itaque praesentium in quis. Ut fugit aut est et fugit aut quaerat vel. Qui quidem maiores voluptate et. Praesentium qui omnis culpa eum repellat velit.\n\nAdipisci voluptas ea sunt esse quis molestiae modi. Illum unde itaque quod neque. Sint consectetur quas sit corporis.\n\nEveniet consectetur voluptates explicabo ducimus aut omnis nihil. Adipisci perspiciatis qui ea in. Quasi corporis minima officiis doloribus et. Eligendi sit et adipisci eius consequatur sed. Ut veritatis libero neque delectus rerum tempora blanditiis.\n\nEst consequatur facere ea voluptatem doloribus autem voluptate. Ipsam culpa ipsam expedita distinctio eveniet beatae.', 4, '2020-04-05 07:41:19', '2020-04-05 07:41:41'), (55, 18, 5, 'Nemo nihil enim delectus et. Dolor dolor cupiditate voluptas eos voluptas quos. Quo incidunt unde numquam necessitatibus at id optio saepe.\n\nVel voluptatum praesentium ea quia sed. Ipsa minus eligendi est quia deleniti.\n\nAmet quis id at quis. Dolorem id nihil esse dolor. Voluptate ullam necessitatibus sed sed. Dolorem et necessitatibus perspiciatis aut sit ut cum tenetur.\n\nExplicabo est voluptas quo accusamus. Omnis quia aut ipsam dolor. Aspernatur aut quam maiores qui consequatur. Qui nihil illo cupiditate ea eum omnis.', -1, '2020-04-05 07:41:19', '2020-04-05 07:41:41'), (56, 18, 3, 'Dolores soluta fuga non temporibus qui. Molestias nam nam consequatur deserunt itaque aut magni.\n\nVel expedita veniam eum doloremque sint. Libero qui cupiditate corrupti aut est aut. Ut eum omnis saepe eligendi fugiat natus incidunt. Omnis illum accusamus et. Odio consequatur earum aut sapiente.\n\nDolorem id aperiam explicabo rerum occaecati corporis eaque. Ipsa quo velit cupiditate sed consequatur eum a. In repudiandae eos cumque dolore. Omnis ut eum ut nulla.\n\nEos vel ut qui minima vitae. Omnis autem facilis doloremque aut provident quod.', 2, '2020-04-05 07:41:19', '2020-04-05 07:41:41'), (57, 18, 2, 'Et mollitia ut et et explicabo. Mollitia dolorem reiciendis aut repellat odit nihil provident. Ab dignissimos numquam et recusandae similique.\n\nTotam adipisci nobis et porro. Officia facere quibusdam corporis sapiente provident laborum. Libero itaque provident nostrum aut. Dolores officia dolorum qui consectetur fugiat accusamus fuga error. Et voluptate et maxime voluptas nobis deleniti.\n\nNulla ab eos et aut similique. Quis et vel inventore voluptatem. Corrupti tempore harum repudiandae minus a ex.\n\nEt repellat inventore quibusdam et. Beatae fugit beatae mollitia autem et veritatis.', 0, '2020-04-05 07:41:20', '2020-04-05 07:41:41'), (58, 18, 5, 'Ducimus laboriosam iure ea. Et velit amet enim eius sit quae et. Rerum aspernatur non laborum natus est maxime laudantium. Expedita doloribus alias quos aliquid at dolorem ut sunt.\n\nQuae rerum asperiores commodi aperiam. Perspiciatis illo et vitae voluptate doloribus cum. Facilis cumque inventore amet atque. Est voluptate error nulla vitae aut.\n\nFacere non molestias ut repudiandae. Ab quod sit omnis temporibus unde. Aut et ipsa voluptatem quisquam. Molestiae facilis est voluptas ea aut est voluptas. Ab adipisci qui minima aut officia laboriosam.\n\nArchitecto est et delectus. Non minus aspernatur facere. Perspiciatis eos iure et voluptatibus. Dignissimos id aut explicabo magni eveniet.\n\nSuscipit soluta suscipit ut iste eveniet. Sit natus aut eos cumque. Eligendi dolor sit sunt reiciendis. Voluptatem enim quis a vel molestias itaque. Commodi dolor dolor est tempora.', -3, '2020-04-05 07:41:20', '2020-04-05 07:41:42'), (59, 19, 1, 'Et sunt laboriosam nihil ut est et error dolorem. Est dolor voluptatem officia ratione rerum. Voluptatem quam adipisci quidem dolorum cupiditate amet iste. Mollitia labore est et autem velit dignissimos quos. Molestias ab quaerat quibusdam quidem dolores suscipit.\n\nConsequatur totam repudiandae perspiciatis deleniti est. Vero porro quia nam qui maxime nihil ut iusto. Magni voluptate beatae animi animi vel. Et alias laboriosam voluptas.\n\nNihil esse neque porro qui sit. Et quasi eius doloremque asperiores sit. Ducimus voluptatibus id tempora pariatur et dicta sapiente.', -2, '2020-04-05 07:41:20', '2020-04-05 07:41:42'); INSERT INTO `answers` (`id`, `question_id`, `user_id`, `body`, `votes_count`, `created_at`, `updated_at`) VALUES (60, 19, 5, 'Magni animi libero similique excepturi velit magnam. Dolore nulla repellendus amet praesentium ducimus. Iusto dolorem perferendis repellat ea placeat deleniti ut. Dolorem sit officiis velit.\n\nDolorum inventore dolore minima fuga quo. Est velit nisi recusandae placeat ut deserunt. Quasi possimus voluptatem qui veniam doloribus enim. Qui aut consequatur ut excepturi.\n\nUnde eaque est velit. Nam atque accusamus non unde. Sed labore sequi omnis praesentium non voluptatibus voluptatum. Consequuntur architecto fugit laboriosam inventore.\n\nAd enim temporibus ad sunt quaerat. Et quia eos quo nesciunt dolores similique. Quibusdam blanditiis ipsa et culpa. Eaque non nemo id ipsa fuga magni sequi sit.\n\nSint quidem corporis voluptatem velit. Ipsum ut ut modi. Dolorem iure labore omnis rerum.\n\nOdit quos voluptatem nesciunt. Molestias accusantium molestiae eum neque rem est enim. Dolore et tempore ipsa voluptates repellendus nam sequi ut.', -3, '2020-04-05 07:41:20', '2020-04-05 07:41:43'), (61, 19, 3, 'Accusantium asperiores amet rerum quia quia aliquam. Est omnis non est omnis rerum. Nihil consequuntur vitae ut praesentium odio dignissimos inventore laudantium.\n\nUnde doloribus distinctio repellendus non sint ratione. Ab vero quis et cupiditate et. Adipisci iste non architecto fugit ut adipisci. Facere consectetur praesentium et necessitatibus.\n\nRepellendus rerum nesciunt accusantium quis vitae magni quis. Exercitationem commodi consequuntur nobis libero error est assumenda. Pariatur qui tenetur quod dolorum nobis provident reprehenderit ex.\n\nTempora omnis amet minima nemo minus quia quasi. Ab est nostrum aut odit. Ut rerum dignissimos fugit ullam amet voluptatum veniam. Possimus debitis ullam aliquam qui odio consequatur.', 1, '2020-04-05 07:41:20', '2020-04-05 07:41:43'), (62, 19, 3, 'Reprehenderit quidem voluptas qui nesciunt qui saepe. Voluptates ut modi voluptatem non dolor pariatur. Eaque nulla debitis illum.\n\nPraesentium odio nihil sequi saepe aut et nisi. Aliquid aut dolor aut eos est voluptatem voluptatem. Aliquam quia voluptatem eius facilis. Ea totam doloribus voluptas qui. Eaque id eligendi rerum aut ut.\n\nUt eos dolor expedita iste. Deleniti iure aperiam et enim officia sit enim quia. Omnis libero quas repellendus ipsum sequi. Sunt occaecati illum sunt repellat ut.\n\nIllum cupiditate exercitationem molestiae qui placeat quia nostrum. Minima facilis recusandae dolores voluptate. Explicabo optio corrupti quibusdam iste. Nesciunt libero odio nam sequi. Nemo nobis et nihil ea voluptate nisi.', -1, '2020-04-05 07:41:20', '2020-04-05 07:41:43'), (63, 19, 2, 'Accusantium aliquid dicta voluptatem consequatur corporis facere culpa. Maxime porro pariatur saepe modi dicta. In et quod non assumenda beatae minima est.\n\nDolor amet quibusdam quaerat maiores. Ad qui et fugit atque delectus. Suscipit facere aliquam cum voluptates ratione qui. Minus nisi beatae molestiae in quia. Qui aut libero qui aperiam sapiente.\n\nNon neque expedita quod laboriosam fugiat laboriosam. Et minus et est error. Sunt quaerat vel doloribus facere. Est ut numquam similique est inventore.\n\nOdit quibusdam voluptas voluptatibus deserunt itaque debitis pariatur temporibus. Et consequuntur qui sint blanditiis. Enim aut et non aut autem alias officiis. Dolor perferendis et ex molestiae.\n\nLibero ipsam eos quam ducimus. Itaque ipsa aut quia id. Ea rerum earum animi laboriosam voluptas id. Sit explicabo consequatur tenetur voluptas aut dolore enim.', 1, '2020-04-05 07:41:20', '2020-04-05 07:55:23'), (64, 20, 6, 'Eaque rem doloribus et ut. Eius libero odio ut facilis rerum dolores.\r\n\r\nIncidunt aliquam consectetur dolorem est. Sit ex beatae placeat sit possimus suscipit enim. Voluptatibus repudiandae voluptatem praesentium qui.\r\n\r\nMaiores libero aut sunt aut rem voluptates voluptas aut. Laboriosam rerum itaque vel quasi tenetur. Qui officiis optio ea ut. Officiis magnam veniam quisquam ex neque.', 1, '2020-04-05 07:51:56', '2020-04-05 07:53:25'), (65, 17, 6, 'Eaque rem doloribus et ut. Eius libero odio ut facilis rerum dolores.\r\n\r\nIncidunt aliquam consectetur dolorem est. Sit ex beatae placeat sit possimus suscipit enim. Voluptatibus repudiandae voluptatem praesentium qui.\r\n\r\nMaiores libero aut sunt aut rem voluptates voluptas aut. Laboriosam rerum itaque vel quasi tenetur. Qui officiis optio ea ut. Officiis magnam veniam quisquam ex neque.Eaque rem doloribus et ut. Eius libero odio ut facilis rerum dolores.\r\n\r\nIncidunt aliquam consectetur dolorem est. Sit ex beatae placeat sit possimus suscipit enim. Voluptatibus repudiandae voluptatem praesentium qui.\r\n\r\nMaiores libero aut sunt aut rem voluptates voluptas aut. Laboriosam rerum itaque vel quasi tenetur. Qui officiis optio ea ut. Officiis magnam veniam quisquam ex neque.', 0, '2020-04-05 07:52:16', '2020-04-05 07:52:16'), (66, 20, 7, 'Voluptate eum occaecati aut et magni repudiandae tenetur iure. Velit corrupti aliquid cupiditate provident velit fugit. Ipsum excepturi perspiciatis vel repellendus.\r\n\r\nEaque rem doloribus et ut. Eius libero odio ut facilis rerum dolores.\r\n\r\nIncidunt aliquam consectetur dolorem est. Sit ex beatae placeat sit possimus suscipit enim. Voluptatibus repudiandae voluptatem praesentium qui.\r\n\r\nMaiores libero aut sunt aut rem voluptates voluptas aut. Laboriosam rerum itaque vel quasi tenetur. Qui officiis optio ea ut. Officiis magnam veniam quisquam ex neque.', 1, '2020-04-05 07:53:12', '2020-04-05 07:54:52'), (67, 21, 7, 'Aut sit quia nihil distinctio. Minus ex amet commodi dolores. Voluptatum autem ea quae quidem. Sint autem est eligendi et.\r\n\r\nVoluptate eum occaecati aut et magni repudiandae tenetur iure. Velit corrupti aliquid cupiditate provident velit fugit. Ipsum excepturi perspiciatis vel repellendus.\r\n\r\nEaque rem doloribus et ut. Eius libero odio ut facilis rerum dolores.\r\n\r\nIncidunt aliquam consectetur dolorem est. Sit ex beatae placeat sit possimus suscipit enim. Voluptatibus repudiandae voluptatem praesentium qui', 0, '2020-04-05 07:53:55', '2020-04-05 07:53:55'), (68, 21, 6, 'Tempora rerum voluptatem adipisci sit optio dignissimos id. Nesciunt autem error sunt. In qui perferendis dolorem asperiores qui dolor quia. Laborum voluptatem eum ut dignissimos quia dolorem ea.\r\n\r\nEt rem et odit laborum vel iure. Recusandae ratione molestias corporis odit temporibus qui ipsa. Ad aperiam in non et omnis expedita cum. Magni natus expedita voluptas dolorem officiis.\r\n\r\nAut sit quia nihil distinctio. Minus ex amet commodi dolores. Voluptatum autem ea quae quidem. Sint autem est eligendi et.', 0, '2020-04-05 07:54:36', '2020-04-05 07:54:36'), (69, 22, 6, '<h1 style=\"font-size:100px;\">Aut sit quia nihil distinctio. Minus ex amet commodi dolores. Voluptatum autem ea quae quidem. Sint autem est eligendi et.</h1>', 0, '2020-04-05 08:16:46', '2020-04-05 08:16:46'); -- -------------------------------------------------------- -- -- Table structure for table `failed_jobs` -- CREATE TABLE `failed_jobs` ( `id` bigint(20) UNSIGNED NOT NULL, `connection` text COLLATE utf8_unicode_ci NOT NULL, `queue` text COLLATE utf8_unicode_ci NOT NULL, `payload` longtext COLLATE utf8_unicode_ci NOT NULL, `exception` longtext COLLATE utf8_unicode_ci NOT NULL, `failed_at` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -------------------------------------------------------- -- -- Table structure for table `favorites` -- CREATE TABLE `favorites` ( `user_id` int(10) UNSIGNED NOT NULL, `question_id` int(10) UNSIGNED NOT NULL, `created_at` timestamp NULL DEFAULT NULL, `updated_at` timestamp NULL DEFAULT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Dumping data for table `favorites` -- INSERT INTO `favorites` (`user_id`, `question_id`, `created_at`, `updated_at`) VALUES (2, 6, '2020-04-05 07:41:21', '2020-04-05 07:41:21'), (2, 9, '2020-04-05 07:41:21', '2020-04-05 07:41:21'), (2, 12, '2020-04-05 07:41:21', '2020-04-05 07:41:21'), (2, 13, '2020-04-05 07:41:22', '2020-04-05 07:41:22'), (3, 1, '2020-04-05 07:41:20', '2020-04-05 07:41:20'), (3, 2, '2020-04-05 07:41:20', '2020-04-05 07:41:20'), (3, 3, '2020-04-05 07:41:20', '2020-04-05 07:41:20'), (3, 6, '2020-04-05 07:41:21', '2020-04-05 07:41:21'), (3, 7, '2020-04-05 07:41:21', '2020-04-05 07:41:21'), (3, 8, '2020-04-05 07:41:21', '2020-04-05 07:41:21'), (3, 9, '2020-04-05 07:41:21', '2020-04-05 07:41:21'), (3, 10, '2020-04-05 07:41:21', '2020-04-05 07:41:21'), (3, 11, '2020-04-05 07:41:21', '2020-04-05 07:41:21'), (3, 12, '2020-04-05 07:41:21', '2020-04-05 07:41:21'), (3, 13, '2020-04-05 07:41:21', '2020-04-05 07:41:21'), (3, 14, '2020-04-05 07:41:22', '2020-04-05 07:41:22'), (3, 17, '2020-04-05 07:41:22', '2020-04-05 07:41:22'), (3, 18, '2020-04-05 07:41:22', '2020-04-05 07:41:22'), (3, 19, '2020-04-05 07:41:22', '2020-04-05 07:41:22'), (4, 1, '2020-04-05 07:41:20', '2020-04-05 07:41:20'), (4, 2, '2020-04-05 07:41:20', '2020-04-05 07:41:20'), (4, 6, '2020-04-05 07:41:21', '2020-04-05 07:41:21'), (4, 9, '2020-04-05 07:41:21', '2020-04-05 07:41:21'), (4, 11, '2020-04-05 07:41:21', '2020-04-05 07:41:21'), (4, 12, '2020-04-05 07:41:21', '2020-04-05 07:41:21'), (4, 13, '2020-04-05 07:41:21', '2020-04-05 07:41:21'), (4, 14, '2020-04-05 07:41:22', '2020-04-05 07:41:22'), (4, 17, '2020-04-05 07:41:22', '2020-04-05 07:41:22'), (4, 18, '2020-04-05 07:41:22', '2020-04-05 07:41:22'), (4, 19, '2020-04-05 07:41:22', '2020-04-05 07:41:22'), (5, 6, '2020-04-05 07:41:21', '2020-04-05 07:41:21'), (5, 9, '2020-04-05 07:41:21', '2020-04-05 07:41:21'), (5, 12, '2020-04-05 07:41:21', '2020-04-05 07:41:21'), (5, 13, '2020-04-05 07:41:21', '2020-04-05 07:41:21'), (5, 14, '2020-04-05 07:41:22', '2020-04-05 07:41:22'), (6, 23, '2020-04-05 11:21:32', '2020-04-05 11:21:32'); -- -------------------------------------------------------- -- -- Table structure for table `migrations` -- CREATE TABLE `migrations` ( `id` int(10) UNSIGNED NOT NULL, `migration` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `batch` int(11) NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Dumping data for table `migrations` -- INSERT INTO `migrations` (`id`, `migration`, `batch`) VALUES (1, '2014_10_12_000000_create_users_table', 1), (2, '2014_10_12_100000_create_password_resets_table', 1), (3, '2019_08_19_000000_create_failed_jobs_table', 1), (4, '2020_03_19_145959_create_questions_table', 1), (5, '2020_03_22_084742_create_answers_table', 1), (6, '2020_03_22_092542_rename_questions_in_answers_table', 1), (7, '2020_03_30_093003_create_favorites_table', 1), (8, '2020_04_03_090229_create_votables_table', 1), (9, '2020_04_03_120054_rename_questions_on_votes_table', 1); -- -------------------------------------------------------- -- -- Table structure for table `password_resets` -- CREATE TABLE `password_resets` ( `email` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `token` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `created_at` timestamp NULL DEFAULT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -------------------------------------------------------- -- -- Table structure for table `questions` -- CREATE TABLE `questions` ( `id` bigint(20) UNSIGNED NOT NULL, `title` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `slug` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `body` text COLLATE utf8_unicode_ci NOT NULL, `views` int(10) UNSIGNED NOT NULL DEFAULT '0', `answers_count` int(10) UNSIGNED NOT NULL DEFAULT '0', `votes_count` int(11) NOT NULL DEFAULT '0', `best_answer_id` int(10) UNSIGNED DEFAULT NULL, `user_id` bigint(20) UNSIGNED NOT NULL, `created_at` timestamp NULL DEFAULT NULL, `updated_at` timestamp NULL DEFAULT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Dumping data for table `questions` -- INSERT INTO `questions` (`id`, `title`, `slug`, `body`, `views`, `answers_count`, `votes_count`, `best_answer_id`, `user_id`, `created_at`, `updated_at`) VALUES (1, 'Et quos accusamus harum neque culpa dolorem laborum', 'et-quos-accusamus-harum-neque-culpa-dolorem-laborum', 'Natus quos dolores est sed eaque autem. Sint dolor aut quo eum. Qui excepturi dolorum aliquid dolores ex sed natus. Necessitatibus ratione qui culpa non.\n\nProvident eos sed vel veniam velit modi. Sed voluptas cupiditate nostrum et aut dolorem.\n\nMolestiae omnis alias modi molestiae sed quis est. Nesciunt odio ex deserunt perferendis. Et sint rerum ut eaque nesciunt velit. Consequatur alias explicabo nihil.\n\nQuos quos et ipsam sint ut in aut. Aliquam sed voluptates maiores.\n\nUt error rerum odio quod. Distinctio laborum corrupti quasi saepe impedit distinctio voluptate.\n\nQuo quaerat dolor hic consectetur alias repellat nihil. Ut blanditiis qui incidunt. Autem vitae a possimus molestiae modi. Repellat et nesciunt porro reiciendis similique dolores odio.\n\nVero tenetur recusandae cupiditate debitis. Cupiditate repellendus saepe numquam nulla ut culpa enim.', 1, 4, 0, NULL, 1, '2020-04-05 07:41:13', '2020-04-05 07:41:22'), (2, 'Quia harum architecto dignissimos tempora enim', 'quia-harum-architecto-dignissimos-tempora-enim', 'Excepturi expedita qui numquam quam. Deleniti iusto aspernatur quas est sed. Nemo voluptas sed ea quia. Doloremque voluptatem voluptatem saepe autem voluptas nulla enim.\n\nSint velit veniam temporibus. Natus culpa accusantium qui voluptatum earum modi ex. Velit nam nisi quas occaecati. Ut ullam esse quo veniam rerum quisquam vitae vel.\n\nOmnis quia rerum sunt eaque. Et dolor nihil est quos. Optio in pariatur architecto sit.', 4, 5, 2, NULL, 1, '2020-04-05 07:41:13', '2020-04-05 07:41:22'), (3, 'Iste quibusdam perspiciatis dolorem ipsam laborum ea et', 'iste-quibusdam-perspiciatis-dolorem-ipsam-laborum-ea-et', 'In est ut eum consequuntur in nemo atque quaerat. Eos rerum est doloremque ex velit aut minima et. Commodi voluptas illum eius sequi.\n\nRem eligendi distinctio porro officia est in. Ut aut et numquam blanditiis quis natus. Sequi nihil incidunt aut ducimus ut.\n\nAdipisci quis magnam nobis tempora et. Facilis ab dolores quo minus vel. Id ut culpa consequatur. Molestias consequatur exercitationem molestiae corporis ipsa ea eveniet perspiciatis.\n\nAsperiores provident et iure beatae. Excepturi quibusdam facere libero est voluptatem quia corporis.\n\nAutem eos deserunt laudantium nobis cum et. Rem iure eos aut hic at modi. Rerum vel non in ut reiciendis. Consequatur quasi autem non nisi dicta.\n\nVoluptate est dolor voluptas. Ipsa mollitia sit quo provident qui quia.', 9, 1, 0, NULL, 2, '2020-04-05 07:41:14', '2020-04-05 07:41:23'), (4, 'Qui in fugiat hic et fugit suscipit', 'qui-in-fugiat-hic-et-fugit-suscipit', 'Maiores occaecati sunt aliquam ut ad. Quia sed sit sapiente placeat. Unde quia rerum aliquid asperiores. Earum est vero delectus deserunt assumenda dolorem alias consequatur.\n\nCommodi sit laudantium molestias qui consectetur eaque perferendis. Iusto ab et consequatur. Eaque dolorem et velit unde aut. Molestiae et reprehenderit aspernatur tempore libero sed. Aut cumque et atque molestias.\n\nVoluptas et suscipit aut eligendi omnis doloremque dolor consequatur. Eos similique aspernatur libero sint quia hic. Doloribus repellat necessitatibus reiciendis incidunt ut est. Perspiciatis dolor accusamus doloribus praesentium aspernatur quo quia amet.\n\nCupiditate quam in qui dolore voluptatem. Sunt culpa eligendi dolores vitae consequuntur commodi. Ipsum modi voluptas ea laudantium quia. Perferendis ut quo quia et dolorum. Voluptas nisi beatae placeat vitae.', 0, 2, 2, NULL, 2, '2020-04-05 07:41:14', '2020-04-05 07:41:23'), (5, 'Non voluptas rerum placeat optio', 'non-voluptas-rerum-placeat-optio', 'Est explicabo ut earum quia dolores. Perspiciatis ea reprehenderit voluptas similique placeat omnis autem. Et voluptatem commodi molestias praesentium et est sit.\n\nSaepe quisquam animi minus rerum quo. Nulla quia corporis eius saepe sequi et quaerat. Itaque aliquam quia ea odio quas dolorum. Debitis quas ut non rerum sunt officiis quas.\n\nId cumque nostrum harum quasi nam sint. Non pariatur dicta minus repellat. Qui et eum et similique voluptas optio occaecati. Eaque modi necessitatibus eligendi cum ut maiores.\n\nMaiores dolorem dolorum libero accusamus itaque. Est eum tempore dolorem ut omnis tempore libero ut. Quis sunt qui incidunt autem aperiam qui.\n\nInventore accusantium rerum sequi quidem numquam sint. Et impedit voluptas officia nesciunt dolorem. Et maiores quasi iusto odio error.', 8, 1, 2, NULL, 2, '2020-04-05 07:41:14', '2020-04-05 07:41:23'), (6, 'Vero eos animi omnis aut ipsum molestiae', 'vero-eos-animi-omnis-aut-ipsum-molestiae', 'Doloribus aliquam sunt iste quae sapiente autem molestiae. Dolorem et modi id possimus similique officiis. Labore rerum neque consequatur blanditiis.\n\nCumque omnis in et soluta et eveniet voluptatem minima. Et quia dolore corporis voluptates id cum et. Et voluptates mollitia itaque sint quibusdam ut qui.\n\nDolor sint autem ut est id omnis repellat. Molestiae est fugit doloremque id unde neque. Accusantium quis aspernatur amet sunt. Quasi nesciunt voluptas non vel magni accusantium veritatis sit.\n\nIllum repellendus occaecati cum sint. Velit nobis fuga illo sapiente amet numquam mollitia. Sed minus ullam eaque molestias aliquid.\n\nEst enim sed eos eum dolore. Quia sint ipsam quaerat necessitatibus repellendus dolor. Repellendus occaecati quidem animi natus.', 9, 4, -1, NULL, 2, '2020-04-05 07:41:14', '2020-04-05 07:41:23'), (7, 'Quidem nostrum qui voluptatem aut animi quo qui', 'quidem-nostrum-qui-voluptatem-aut-animi-quo-qui', 'Atque eaque repellendus eaque beatae doloremque autem totam. Dolorem facere nam totam est repellat. Maiores est officiis quo voluptas qui consectetur voluptas.\n\nRerum sed officia ut qui ipsam repudiandae rerum. Veritatis nulla aut dolorum et saepe. Quae voluptatem illum qui vitae qui ratione et. Est quia iure excepturi qui. Quam exercitationem sit id et sint ratione.\n\nDicta voluptas molestiae omnis pariatur ut itaque accusamus qui. Error rerum qui omnis enim quisquam quia. In ad quasi hic vel eos et.\n\nMinus magni itaque sit. Voluptatem totam quod laboriosam. Non error et optio voluptatem rerum labore.\n\nPraesentium excepturi itaque quod itaque sit quasi. Nemo et quia possimus molestias aut eius. Possimus quod porro quia voluptatem et sit et deleniti. Corporis reiciendis debitis qui adipisci.\n\nQuo laborum et nemo in. Quis ea odit ea qui tenetur. Qui aut qui qui assumenda ullam dolorum. Earum voluptas ut et odio odit aspernatur debitis maxime. Nihil eum ut laboriosam sit dolorem nam sed.\n\nReprehenderit minus pariatur maiores odit culpa fugiat. Et et ut neque optio qui. Temporibus culpa omnis molestias autem sint eligendi.', 1, 4, 2, NULL, 3, '2020-04-05 07:41:15', '2020-04-05 07:41:24'), (8, 'Perspiciatis illo at odio numquam a dolorum aspernatur nam ea quo', 'perspiciatis-illo-at-odio-numquam-a-dolorum-aspernatur-nam-ea-quo', 'Dignissimos inventore illum possimus. Aliquam delectus et est quam voluptatem quis veniam. Est sequi qui unde quis impedit sed vero.\n\nEsse odit quaerat sed rerum consequatur atque. Odio consequatur quaerat debitis est quas. Est consequuntur explicabo consectetur eius et.\n\nSed quas nam aut non vel dolorem. Aut a rerum vero. Sunt quia libero dolor sed deserunt officia.\n\nFacilis molestias non dolor sed molestiae cupiditate. A dolores corrupti quod voluptas maxime debitis. Est rerum quo in rem tempora omnis assumenda. Et distinctio at et quibusdam atque.\n\nDeserunt nulla vitae quae possimus eos ea velit. Est sed explicabo nihil et et aut.\n\nEt tenetur est maxime non aut accusamus non. Harum soluta a laudantium pariatur. Sint voluptatem unde exercitationem ut reiciendis aliquid.\n\nDolores provident quaerat eum sit porro aut. Tempora unde nesciunt dolore fugit eum tenetur eum. Omnis laboriosam vero officia est et. Minus omnis vitae possimus inventore libero.', 3, 5, 1, NULL, 3, '2020-04-05 07:41:15', '2020-04-05 07:41:24'), (9, 'Incidunt quidem voluptatum doloribus dolorem', 'incidunt-quidem-voluptatum-doloribus-dolorem', 'Qui et enim molestias. Cupiditate sit incidunt quaerat consequatur cumque dolor adipisci. In ipsa quasi excepturi aliquid eaque. Qui consequatur nostrum iure eius.\n\nVoluptas provident hic molestias adipisci eaque. Voluptas quidem deleniti quia a vel et in est. Voluptatem minus corrupti aut officiis velit. Accusamus qui quod molestiae eos aut.\n\nOmnis impedit quibusdam eius voluptas aut. Aut nihil cumque nemo rerum. Quia iusto veniam corrupti facere autem dicta dolor.\n\nRepellendus corporis aut dolorem perspiciatis blanditiis qui officia. Eaque placeat magni qui vel non nemo corrupti. Nisi rem labore omnis. Cum voluptas alias ad et deleniti quasi.\n\nQuo quia rem est tempora. Rerum doloremque est nemo velit beatae. Atque quod in officiis consequatur.\n\nNon minus sit similique commodi error qui quia. Aut repellendus quia explicabo ea sint ipsum. Repudiandae ipsum excepturi fugiat perspiciatis aliquid et est quam.\n\nRerum ea in vel sed ad qui. Consequatur ea voluptate repellat. Et rerum ex repudiandae est rem. Nisi necessitatibus unde repudiandae.', 5, 1, -1, NULL, 3, '2020-04-05 07:41:15', '2020-04-05 07:41:24'), (10, 'Accusamus ut non sunt reiciendis ad accusamus', 'accusamus-ut-non-sunt-reiciendis-ad-accusamus', 'Et provident cupiditate iure nostrum non distinctio. Cum modi quos et omnis quia qui ratione. Aut sit possimus quia magni natus.\n\nUllam similique voluptatum voluptatum facere voluptatum expedita. Est quia et eius voluptas in totam. Quos natus non neque enim est sed. Perspiciatis officiis ut laboriosam et dolores dolor aut. Dolores doloremque quos repellendus sequi.\n\nVoluptates est facere nemo illum id non magnam. Quia nisi corporis minima minus. Accusantium atque voluptas eos voluptates sit illo autem.\n\nPerferendis nam dolorum totam similique adipisci vero qui. Recusandae minus nemo necessitatibus non iusto odio doloribus. Et similique eum nesciunt nulla.', 7, 5, 0, NULL, 3, '2020-04-05 07:41:15', '2020-04-05 07:41:24'), (11, 'Explicabo harum est vel ipsa ipsam facilis et officia', 'explicabo-harum-est-vel-ipsa-ipsam-facilis-et-officia', 'Ut nihil tempore est ullam sint provident commodi et. Omnis et officiis eos corrupti. Quia perferendis dolor at dolores itaque assumenda quia. Rem officiis qui deleniti adipisci maiores. Fugit architecto odit eum cupiditate id et sit.\n\nLaudantium culpa illum et qui temporibus minima. Minima sed tenetur cumque natus incidunt. In iure omnis non. Voluptatibus explicabo vel incidunt ut nulla libero aut qui.\n\nEt rerum et omnis beatae nihil. Libero reiciendis ut voluptas. Et vitae quia dolor dolore sint aut. Accusamus rerum iure et nostrum quos est voluptatem.\n\nLaborum ratione optio facere voluptatum. Voluptatem sed atque aspernatur hic numquam doloremque excepturi. Nulla sint mollitia dolores sed explicabo.', 10, 4, 1, NULL, 3, '2020-04-05 07:41:15', '2020-04-05 07:41:25'), (12, 'Soluta expedita distinctio voluptatibus magnam ea', 'soluta-expedita-distinctio-voluptatibus-magnam-ea', 'Totam accusamus iste voluptatibus. Non et sunt corrupti velit ipsa porro ut. Beatae suscipit soluta excepturi eligendi dignissimos. Suscipit fugiat et laborum assumenda dolorum eos quod architecto.\n\nSint enim ut sapiente blanditiis eum dicta accusantium. Provident sit quia dolore. Repudiandae at ut error exercitationem iure.\n\nQuos alias eos eligendi iure quia porro. Eos reprehenderit et harum in dicta sed. Autem tempore velit mollitia perferendis laboriosam. Vero et et et labore dolorum impedit minima. Aspernatur reiciendis perferendis ipsum mollitia quas eius accusantium.', 8, 1, 2, NULL, 4, '2020-04-05 07:41:17', '2020-04-05 07:41:25'), (13, 'Rerum quod aliquid illo earum unde voluptatem facilis asperiores vel', 'rerum-quod-aliquid-illo-earum-unde-voluptatem-facilis-asperiores-vel', 'Vel sit ea et placeat. Sint tenetur eveniet aut corporis. Qui sint voluptatum nemo sapiente voluptas. Aut sit et non est aut modi officia.\n\nPossimus sit voluptas non suscipit velit inventore labore. Dicta illo voluptatem in qui. Sed qui quam quia repudiandae ipsum.\n\nVoluptatem sed ipsum et doloremque ea voluptatem architecto. Qui animi sed ipsam ipsum autem ea. Officia similique aut voluptatem laudantium illo suscipit aut.', 9, 2, -1, NULL, 4, '2020-04-05 07:41:17', '2020-04-05 07:41:25'), (14, 'Quasi est minima sint officiis dolore consequatur', 'quasi-est-minima-sint-officiis-dolore-consequatur', 'Aspernatur eius nihil et cum quia odit natus labore. Nostrum autem assumenda optio amet. Voluptatem illum dolor magnam et vero ratione. Rerum ut saepe veritatis rerum repellat ut voluptates.\n\nCorporis blanditiis nemo consequatur laboriosam et in. Adipisci illo velit doloribus ut.\n\nSed sequi et vel recusandae. Officia esse magnam blanditiis architecto. Architecto architecto eos cumque facilis impedit impedit.\n\nSoluta vero id et. Neque qui porro quibusdam accusamus quia expedita. Sed laudantium non quasi animi sunt ut fugit. Facilis dolores et fugit laboriosam eos culpa consequuntur.\n\nQuo dolores quaerat odio reiciendis. Maxime itaque minima enim perferendis et porro aut in. Voluptate reiciendis aliquid id ea qui eveniet voluptatem.', 9, 2, 0, NULL, 4, '2020-04-05 07:41:17', '2020-04-05 07:41:25'), (15, 'Distinctio enim omnis sed iusto et ad nulla quidem nam soluta sequi', 'distinctio-enim-omnis-sed-iusto-et-ad-nulla-quidem-nam-soluta-sequi', 'Libero suscipit officiis unde non et tempora laboriosam. Laborum eveniet consectetur exercitationem. Possimus vero dolore sit maxime itaque.\n\nEa sed maiores sunt eveniet qui deleniti quia excepturi. Beatae hic maxime soluta minima dolorem praesentium. Tempora occaecati non dolores dolores.\n\nSint autem voluptatem id accusamus odio architecto natus. Voluptas et ex ab et et amet veniam. Nobis magnam impedit rerum exercitationem. Cumque illo rem perspiciatis minus quia.\n\nPariatur quia sint assumenda quia. In itaque optio incidunt deleniti veniam omnis quidem. Eum et consequatur quibusdam enim.', 4, 5, -2, NULL, 4, '2020-04-05 07:41:17', '2020-04-05 07:41:26'), (16, 'Dolores neque distinctio placeat voluptatem', 'dolores-neque-distinctio-placeat-voluptatem', 'Eum ipsam perferendis voluptates. Laboriosam porro ullam aut cupiditate inventore quis quam. Iste deserunt doloribus reiciendis necessitatibus sed. Possimus in voluptatibus dolores consequatur ex velit laborum.\n\nEt quia sit eos nesciunt doloribus. Error hic laboriosam libero dolorem odio ipsa alias recusandae. Voluptas recusandae est vel aut quaerat dolorem voluptas minima. Neque sint enim eos facilis.\n\nRatione fugiat minus aut voluptas. At earum blanditiis eius repudiandae. Labore quam sequi praesentium qui.\n\nConsequatur voluptatem sed in quidem eum aliquid dicta ipsa. Libero nihil ea illo sint. Maxime praesentium quisquam dolor et. Voluptas nesciunt libero sed repellat quod suscipit.\n\nConsequatur labore voluptates ullam labore. Vel ea maiores non aliquid nobis qui totam. Harum sequi id deleniti perspiciatis id quis veritatis.\n\nAlias quod quod voluptate rerum facilis mollitia. Sed eius hic et modi molestias exercitationem molestias. Perspiciatis optio nostrum odit praesentium sed.\n\nQuia qui quam quia corrupti non est sed qui. Optio culpa labore ut omnis soluta. In exercitationem est facere.', 2, 2, 2, NULL, 4, '2020-04-05 07:41:18', '2020-04-05 07:43:50'), (17, 'Odio consequatur suscipit sint', 'odio-consequatur-suscipit-sint', 'Tempora rerum voluptatem adipisci sit optio dignissimos id. Nesciunt autem error sunt. In qui perferendis dolorem asperiores qui dolor quia. Laborum voluptatem eum ut dignissimos quia dolorem ea.\n\nEt rem et odit laborum vel iure. Recusandae ratione molestias corporis odit temporibus qui ipsa. Ad aperiam in non et omnis expedita cum. Magni natus expedita voluptas dolorem officiis.\n\nAut sit quia nihil distinctio. Minus ex amet commodi dolores. Voluptatum autem ea quae quidem. Sint autem est eligendi et.\n\nVoluptate eum occaecati aut et magni repudiandae tenetur iure. Velit corrupti aliquid cupiditate provident velit fugit. Ipsum excepturi perspiciatis vel repellendus.\n\nEaque rem doloribus et ut. Eius libero odio ut facilis rerum dolores.\n\nIncidunt aliquam consectetur dolorem est. Sit ex beatae placeat sit possimus suscipit enim. Voluptatibus repudiandae voluptatem praesentium qui.\n\nMaiores libero aut sunt aut rem voluptates voluptas aut. Laboriosam rerum itaque vel quasi tenetur. Qui officiis optio ea ut. Officiis magnam veniam quisquam ex neque.', 9, 6, 1, NULL, 5, '2020-04-05 07:41:19', '2020-04-05 07:52:17'), (18, 'Non facilis quibusdam vitae nisi nisi reprehenderit qui molestiae', 'non-facilis-quibusdam-vitae-nisi-nisi-reprehenderit-qui-molestiae', 'Odio facere qui eaque omnis. Et pariatur officia harum quod similique. Quibusdam quis rerum voluptatem autem quae delectus.\n\nEst expedita veritatis dolor blanditiis quidem repellendus aliquam eos. Quia mollitia enim culpa minima. Praesentium autem laudantium necessitatibus est non ut.\n\nArchitecto omnis velit et. Eligendi in consequatur hic sapiente maiores tempore voluptate. Mollitia sit est laudantium veniam est.\n\nDolores impedit tenetur voluptas accusamus. Similique id qui facere accusantium aliquid. Fugit omnis ratione consectetur mollitia ut.\n\nAmet doloribus omnis excepturi asperiores ad eum soluta. Quaerat vitae et numquam. Doloremque saepe dolor error ipsa corporis nisi sit.\n\nMolestiae ullam in soluta cupiditate deserunt. Nihil id sapiente veniam deleniti impedit rerum odit. Ut labore cum delectus.', 2, 5, 1, NULL, 5, '2020-04-05 07:41:19', '2020-04-05 07:41:26'), (19, 'Ut et rerum numquam temporibus deleniti impedit nulla unde ipsam voluptatibus', 'ut-et-rerum-numquam-temporibus-deleniti-impedit-nulla-unde-ipsam-voluptatibus', 'Illum numquam provident dolor non dolor et saepe. Animi molestiae voluptas cum qui. Pariatur molestiae aut error est impedit. Voluptatum sed ab autem qui autem.\n\nNihil eius eos maiores ipsa eaque. Voluptatem minima eos ut voluptas.\n\nUt eos inventore iste facilis enim et consequuntur aut. Aut officiis iure id. Aperiam non debitis minus numquam. Et quam in laboriosam.\n\nAdipisci vitae excepturi ipsam nihil voluptatem odit quaerat pariatur. Dicta aspernatur et provident ea rem assumenda. Esse dolorum quidem quidem. Quibusdam magni voluptatem eos necessitatibus tempore sint non expedita.\n\nEius cumque deserunt reprehenderit hic eius. Autem perferendis aliquam est voluptatum explicabo illum labore. Qui quod nulla nobis aut dolor voluptatibus quidem.\n\nDolores quo placeat qui perferendis qui ab. Repellat dolore et blanditiis dolores maxime sed labore. Et aspernatur enim commodi vel mollitia animi suscipit.', 7, 5, 4, NULL, 5, '2020-04-05 07:41:19', '2020-04-05 07:55:15'), (20, 'Tempora rerum voluptatem ad', 'tempora-rerum-voluptatem-ad', 'Tempora rerum voluptatem adipisci sit optio dignissimos id. Nesciunt autem error sunt. In qui perferendis dolorem asperiores qui dolor quia. Laborum voluptatem eum ut dignissimos quia dolorem ea.\r\n\r\nEt rem et odit laborum vel iure. Recusandae ratione molestias corporis odit temporibus qui ipsa. Ad aperiam in non et omnis expedita cum. Magni natus expedita voluptas dolorem officiis.\r\n\r\nAut sit quia nihil distinctio. Minus ex amet commodi dolores. Voluptatum autem ea quae quidem. Sint autem est eligendi et.\r\n\r\nVoluptate eum occaecati aut et magni repudiandae tenetur iure. Velit corrupti aliquid cupiditate provident velit fugit. Ipsum excepturi perspiciatis vel repellendus.\r\n\r\nEaque rem doloribus et ut. Eius libero odio ut facilis rerum dolores.\r\n\r\nIncidunt aliquam consectetur dolorem est. Sit ex beatae placeat sit possimus suscipit enim. Voluptatibus repudiandae voluptatem praesentium qui.\r\n\r\nMaiores libero aut sunt aut rem voluptates voluptas aut. Laboriosam rerum itaque vel quasi tenetur. Qui officiis optio ea ut. Officiis magnam veniam quisquam ex neque.', 0, 2, 1, 66, 6, '2020-04-05 07:51:46', '2020-04-05 07:55:01'), (21, 'Eius libero odio ut facilis rerum dolores.', 'eius-libero-odio-ut-facilis-rerum-dolores', 'Tempora rerum voluptatem adipisci sit optio dignissimos id. Nesciunt autem error sunt. In qui perferendis dolorem asperiores qui dolor quia. Laborum voluptatem eum ut dignissimos quia dolorem ea.\r\n\r\nEt rem et odit laborum vel iure. Recusandae ratione molestias corporis odit temporibus qui ipsa. Ad aperiam in non et omnis expedita cum. Magni natus expedita voluptas dolorem officiis.\r\n\r\nAut sit quia nihil distinctio. Minus ex amet commodi dolores. Voluptatum autem ea quae quidem. Sint autem est eligendi et.\r\n\r\nVoluptate eum occaecati aut et magni repudiandae tenetur iure. Velit corrupti aliquid cupiditate provident velit fugit. Ipsum excepturi perspiciatis vel repellendus.\r\n\r\nEaque rem doloribus et ut. Eius libero odio ut facilis rerum dolores.\r\n\r\nIncidunt aliquam consectetur dolorem est. Sit ex beatae placeat sit possimus suscipit enim. Voluptatibus repudiandae voluptatem praesentium qui.\r\n\r\nMaiores libero aut sunt aut rem voluptates voluptas aut. Laboriosam rerum itaque vel quasi tenetur. Qui officiis optio ea ut. Officiis magnam veniam quisquam ex neque.', 0, 2, 0, NULL, 7, '2020-04-05 07:53:47', '2020-04-05 07:54:36'), (22, 'Et rem et odit laborum vel iure. Recusan', 'et-rem-et-odit-laborum-vel-iure-recusan', '<!doctype html>\r\n<html lang=\"en\">\r\n <head>\r\n <!-- Required meta tags -->\r\n <meta charset=\"utf-8\">\r\n <meta name=\"viewport\" content=\"width=device-width, initial-scale=1, shrink-to-fit=no\">\r\n\r\n <!-- Bootstrap CSS -->\r\n <link rel=\"stylesheet\" href=\"https://stackpath.bootstrapcdn.com/bootstrap/4.4.1/css/bootstrap.min.css\" integrity=\"<KEY>\" crossorigin=\"anonymous\">\r\n\r\n <title>Hello, world!</title>\r\n </head>\r\n <body>\r\n <h1>Hello, world!</h1>\r\n\r\n <!-- Optional JavaScript -->\r\n <!-- jQuery first, then Popper.js, then Bootstrap JS -->\r\n <script src=\"https://code.jquery.com/jquery-3.4.1.slim.min.js\" integrity=\"<KEY>\" crossorigin=\"anonymous\"></script>\r\n <script src=\"https://cdn.jsdelivr.net/npm/[email protected]/dist/umd/popper.min.js\" integrity=\"sha384-Q6E9RHvbIyZFJoft+2mJbHaEWldlvI9IOYy5n3zV9zzTtmI3UksdQRVvoxMfooAo\" crossorigin=\"anonymous\"></script>\r\n <script src=\"https://stackpath.bootstrapcdn.com/bootstrap/4.4.1/js/bootstrap.min.js\" integrity=\"sha384-wfSDF2E50Y2D1uUdj0O3uMBJnjuUD4Ih7YwaYd1iqfktj0Uod8GCExl3Og8ifwB6\" crossorigin=\"anonymous\"></script>\r\n </body>\r\n</html>', 0, 1, 0, NULL, 6, '2020-04-05 08:11:48', '2020-04-05 08:16:46'), (23, 'ine\', \'Inline\', \'Common\'', 'ine-inline-common', 'return [\r\n \'encoding\' => \'UTF-8\',\r\n \'finalize\' => true,\r\n \'cachePath\' => storage_path(\'app/purifier\'),\r\n \'cacheFileMode\' => 0755,\r\n \'settings\' => [\r\n \'default\' => [\r\n \'HTML.Doctype\' => \'HTML 4.01 Transitional\',\r\n \'HTML.Allowed\' => \'div,b,strong,i,em,u,a[href|title],ul,ol,li,p[style],br,span[style],img[width|height|alt|src]\',\r\n \'CSS.AllowedProperties\' => \'font,font-size,font-weight,font-style,font-family,text-decoration,padding-left,color,background-color,text-align\',\r\n \'AutoFormat.AutoParagraph\' => true,\r\n \'AutoFormat.RemoveEmpty\' => true,\r\n ],\r\n \'test\' => [\r\n \'Attr.EnableID\' => \'true\',\r\n ],\r\n \"youtube\" => [\r\n \"HTML.SafeIframe\" => \'true\',\r\n \"URI.SafeIframeRegexp\" => \"%^(http://|https://|//)(www.youtube.com/embed/|player.vimeo.com/video/)%\",\r\n ],\r\n \'custom_definition\' => [\r\n \'id\' => \'html5-definitions\',\r\n \'rev\' => 1,\r\n \'debug\' => false,\r\n \'elements\' => [\r\n // http://developers.whatwg.org/sections.html\r\n [\'section\', \'Block\', \'Flow\', \'Common\'],\r\n [\'nav\', \'Block\', \'Flow\', \'Common\'],\r\n [\'article\', \'Block\', \'Flow\', \'Common\'],\r\n [\'aside\', \'Block\', \'Flow\', \'Common\'],\r\n [\'header\', \'Block\', \'Flow\', \'Common\'],\r\n [\'footer\', \'Block\', \'Flow\', \'Common\'],\r\n \r\n // Content model actually excludes several tags, not modelled here\r\n [\'address\', \'Block\', \'Flow\', \'Common\'],\r\n [\'hgroup\', \'Block\', \'Required: h1 | h2 | h3 | h4 | h5 | h6\', \'Common\'],\r\n \r\n // http://developers.whatwg.org/grouping-content.html\r\n [\'figure\', \'Block\', \'Optional: (figcaption, Flow) | (Flow, figcaption) | Flow\', \'Common\'],\r\n [\'figcaption\', \'Inline\', \'Flow\', \'Common\'],\r\n \r\n // http://developers.whatwg.org/the-video-element.html#the-video-element\r\n [\'video\', \'Block\', \'Optional: (source, Flow) | (Flow, source) | Flow\', \'Common\', [\r\n \'src\' => \'URI\',\r\n \'type\' => \'Text\',\r\n \'width\' => \'Length\',\r\n \'height\' => \'Length\',\r\n \'poster\' => \'URI\',\r\n \'preload\' => \'Enum#auto,metadata,none\',\r\n \'controls\' => \'Bool\',\r\n ]],\r\n [\'source\', \'Block\', \'Flow\', \'Common\', [\r\n \'src\' => \'URI\',\r\n \'type\' => \'Text\',\r\n ]],\r\n\r\n // http://developers.whatwg.org/text-level-semantics.html\r\n [\'s\', \'Inline\', \'Inline\', \'Common\'],\r\n [\'var\', \'Inline\', \'Inline\', \'Common\'],\r\n [\'sub\', \'Inline\', \'Inline\', \'Common\'],\r\n [\'sup\', \'Inline\', \'Inline\', \'Common\'],\r\n [\'mark\', \'Inline\', \'Inline\', \'Common\'],\r\n [\'wbr\', \'Inline\', \'Empty\', \'Core\'],\r\n \r\n // http://developers.whatwg.org/edits.html\r\n [\'ins\', \'Block\', \'Flow\', \'Common\', [\'cite\' => \'URI\', \'datetime\' => \'CDATA\']],\r\n [\'del\', \'Block\', \'Flow\', \'Common\', [\'cite\' => \'URI\', \'datetime\' => \'CDATA\']],\r\n ],\r\n \'attributes\' => [\r\n [\'iframe\', \'allowfullscreen\', \'Bool\'],\r\n [\'table\', \'height\', \'Text\'],\r\n [\'td\', \'border\', \'Text\'],\r\n [\'th\', \'border\', \'Text\'],\r\n [\'tr\', \'width\', \'Text\'],\r\n [\'tr\', \'height\', \'Text\'],\r\n [\'tr\', \'border\', \'Text\'],\r\n ],\r\n ],\r\n \'custom_attributes\' => [\r\n [\'a\', \'target\', \'Enum#_blank,_self,_target,_top\'],\r\n ],\r\n \'custom_elements\' => [\r\n [\'u\', \'Inline\', \'Inline\', \'Common\'],\r\n ],\r\n ],\r\n\r\n];', 0, 0, 1, NULL, 6, '2020-04-05 08:18:36', '2020-04-05 11:21:28'); -- -------------------------------------------------------- -- -- Table structure for table `users` -- CREATE TABLE `users` ( `id` bigint(20) UNSIGNED NOT NULL, `name` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `email` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `email_verified_at` timestamp NULL DEFAULT NULL, `password` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `remember_token` varchar(100) COLLATE utf8_unicode_ci DEFAULT NULL, `created_at` timestamp NULL DEFAULT NULL, `updated_at` timestamp NULL DEFAULT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Dumping data for table `users` -- INSERT INTO `users` (`id`, `name`, `email`, `email_verified_at`, `password`, `remember_token`, `created_at`, `updated_at`) VALUES (1, '<NAME>', '<EMAIL>', '2020-04-05 07:41:13', '$2y$10$92IXUNpkjO0rOQ5byMi.Ye4oKoEa3Ro9llC/.og/at2.uheWG/igi', 'fMg0PCT48A', '2020-04-05 07:41:13', '2020-04-05 07:41:13'), (2, '<NAME>', '<EMAIL>', '2020-04-05 07:41:13', '$2y$10$92IXUNpkjO0rOQ5byMi.Ye4oKoEa3Ro9llC/.og/at2.uheWG/igi', 'KjwYBrHFij', '2020-04-05 07:41:13', '2020-04-05 07:41:13'), (3, 'Ms. <NAME>', '<EMAIL>', '2020-04-05 07:41:13', '$2y$10$92IXUNpkjO0rOQ5byMi.Ye4oKoEa3Ro9llC/.og/at2.uheWG/igi', 'NA6BBwBXVl', '2020-04-05 07:41:13', '2020-04-05 07:41:13'), (4, '<NAME>', '<EMAIL>', '2020-04-05 07:41:13', '$2y$10$92IXUNpkjO0rOQ5byMi.Ye4oKoEa3Ro9llC/.og/at2.uheWG/igi', 'QQrbJUgx1L', '2020-04-05 07:41:13', '2020-04-05 07:41:13'), (5, '<NAME>', '<EMAIL>', '2020-04-05 07:41:13', '$2y$10$92IXUNpkjO0rOQ5byMi.Ye4oKoEa3Ro9llC/.og/at2.uheWG/igi', 'WDfGQGQ6hO', '2020-04-05 07:41:13', '2020-04-05 07:41:13'), (6, '<NAME>', '<EMAIL>', NULL, '$2y$10$1ZK9Ipidj4a7KYeJKXNT6On1.KSSdZN7So/S.LXkzdmS4mnrxHPqS', NULL, '2020-04-05 07:43:30', '2020-04-05 07:43:30'), (7, '<NAME>', '<EMAIL>', NULL, '$2y$10$OFDCNXw2rM8JcGf.FUF8MugA6g/VhHGNd3jvcusm5YSXX3mdRQPDm', NULL, '2020-04-05 07:52:57', '2020-04-05 07:52:57'); -- -------------------------------------------------------- -- -- Table structure for table `votables` -- CREATE TABLE `votables` ( `user_id` int(10) UNSIGNED NOT NULL, `votable_id` int(10) UNSIGNED NOT NULL, `votable_type` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `vote` tinyint(4) NOT NULL COMMENT '-1:down vote,1:up vote', `created_at` timestamp NULL DEFAULT NULL, `updated_at` timestamp NULL DEFAULT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Dumping data for table `votables` -- INSERT INTO `votables` (`user_id`, `votable_id`, `votable_type`, `vote`, `created_at`, `updated_at`) VALUES (1, 1, 'App\\Answer', 1, '2020-04-05 07:41:27', '2020-04-05 07:41:27'), (1, 1, 'App\\Question', 1, '2020-04-05 07:41:22', '2020-04-05 07:41:22'), (1, 2, 'App\\Answer', 1, '2020-04-05 07:41:27', '2020-04-05 07:41:27'), (1, 2, 'App\\Question', 1, '2020-04-05 07:41:22', '2020-04-05 07:41:22'), (1, 3, 'App\\Answer', 1, '2020-04-05 07:41:27', '2020-04-05 07:41:27'), (1, 3, 'App\\Question', 1, '2020-04-05 07:41:22', '2020-04-05 07:41:22'), (1, 4, 'App\\Answer', -1, '2020-04-05 07:41:27', '2020-04-05 07:41:27'), (1, 4, 'App\\Question', -1, '2020-04-05 07:41:23', '2020-04-05 07:41:23'), (1, 5, 'App\\Answer', -1, '2020-04-05 07:41:28', '2020-04-05 07:41:28'), (1, 5, 'App\\Question', 1, '2020-04-05 07:41:23', '2020-04-05 07:41:23'), (1, 6, 'App\\Answer', -1, '2020-04-05 07:41:28', '2020-04-05 07:41:28'), (1, 6, 'App\\Question', -1, '2020-04-05 07:41:23', '2020-04-05 07:41:23'), (1, 7, 'App\\Answer', -1, '2020-04-05 07:41:28', '2020-04-05 07:41:28'), (1, 7, 'App\\Question', 1, '2020-04-05 07:41:23', '2020-04-05 07:41:23'), (1, 8, 'App\\Answer', -1, '2020-04-05 07:41:28', '2020-04-05 07:41:28'), (1, 8, 'App\\Question', 1, '2020-04-05 07:41:24', '2020-04-05 07:41:24'), (1, 9, 'App\\Answer', -1, '2020-04-05 07:41:28', '2020-04-05 07:41:28'), (1, 9, 'App\\Question', 1, '2020-04-05 07:41:24', '2020-04-05 07:41:24'), (1, 10, 'App\\Answer', 1, '2020-04-05 07:41:29', '2020-04-05 07:41:29'), (1, 10, 'App\\Question', 1, '2020-04-05 07:41:24', '2020-04-05 07:41:24'), (1, 11, 'App\\Answer', -1, '2020-04-05 07:41:29', '2020-04-05 07:41:29'), (1, 11, 'App\\Question', 1, '2020-04-05 07:41:24', '2020-04-05 07:41:24'), (1, 12, 'App\\Answer', 1, '2020-04-05 07:41:29', '2020-04-05 07:41:29'), (1, 12, 'App\\Question', 1, '2020-04-05 07:41:25', '2020-04-05 07:41:25'), (1, 13, 'App\\Answer', -1, '2020-04-05 07:41:30', '2020-04-05 07:41:30'), (1, 13, 'App\\Question', -1, '2020-04-05 07:41:25', '2020-04-05 07:41:25'), (1, 14, 'App\\Answer', -1, '2020-04-05 07:41:30', '2020-04-05 07:41:30'), (1, 14, 'App\\Question', 1, '2020-04-05 07:41:25', '2020-04-05 07:41:25'), (1, 15, 'App\\Answer', 1, '2020-04-05 07:41:30', '2020-04-05 07:41:30'), (1, 15, 'App\\Question', -1, '2020-04-05 07:41:25', '2020-04-05 07:41:25'), (1, 16, 'App\\Answer', 1, '2020-04-05 07:41:30', '2020-04-05 07:41:30'), (1, 16, 'App\\Question', 1, '2020-04-05 07:41:26', '2020-04-05 07:41:26'), (1, 17, 'App\\Answer', 1, '2020-04-05 07:41:30', '2020-04-05 07:41:30'), (1, 17, 'App\\Question', 1, '2020-04-05 07:41:26', '2020-04-05 07:41:26'), (1, 18, 'App\\Answer', 1, '2020-04-05 07:41:31', '2020-04-05 07:41:31'), (1, 18, 'App\\Question', 1, '2020-04-05 07:41:26', '2020-04-05 07:41:26'), (1, 19, 'App\\Answer', 1, '2020-04-05 07:41:31', '2020-04-05 07:41:31'), (1, 19, 'App\\Question', -1, '2020-04-05 07:41:26', '2020-04-05 07:41:26'), (1, 20, 'App\\Answer', -1, '2020-04-05 07:41:31', '2020-04-05 07:41:31'), (1, 21, 'App\\Answer', 1, '2020-04-05 07:41:32', '2020-04-05 07:41:32'), (1, 22, 'App\\Answer', 1, '2020-04-05 07:41:32', '2020-04-05 07:41:32'), (1, 23, 'App\\Answer', 1, '2020-04-05 07:41:32', '2020-04-05 07:41:32'), (1, 24, 'App\\Answer', -1, '2020-04-05 07:41:33', '2020-04-05 07:41:33'), (1, 25, 'App\\Answer', -1, '2020-04-05 07:41:33', '2020-04-05 07:41:33'), (1, 26, 'App\\Answer', 1, '2020-04-05 07:41:33', '2020-04-05 07:41:33'), (1, 27, 'App\\Answer', -1, '2020-04-05 07:41:33', '2020-04-05 07:41:33'), (1, 28, 'App\\Answer', -1, '2020-04-05 07:41:34', '2020-04-05 07:41:34'), (1, 29, 'App\\Answer', -1, '2020-04-05 07:41:34', '2020-04-05 07:41:34'), (1, 30, 'App\\Answer', -1, '2020-04-05 07:41:34', '2020-04-05 07:41:34'), (1, 31, 'App\\Answer', 1, '2020-04-05 07:41:35', '2020-04-05 07:41:35'), (1, 32, 'App\\Answer', -1, '2020-04-05 07:41:35', '2020-04-05 07:41:35'), (1, 33, 'App\\Answer', -1, '2020-04-05 07:41:35', '2020-04-05 07:41:35'), (1, 34, 'App\\Answer', 1, '2020-04-05 07:41:35', '2020-04-05 07:41:35'), (1, 35, 'App\\Answer', 1, '2020-04-05 07:41:35', '2020-04-05 07:41:35'), (1, 36, 'App\\Answer', -1, '2020-04-05 07:41:35', '2020-04-05 07:41:35'), (1, 37, 'App\\Answer', 1, '2020-04-05 07:41:36', '2020-04-05 07:41:36'), (1, 38, 'App\\Answer', -1, '2020-04-05 07:41:36', '2020-04-05 07:41:36'), (1, 39, 'App\\Answer', -1, '2020-04-05 07:41:36', '2020-04-05 07:41:36'), (1, 40, 'App\\Answer', -1, '2020-04-05 07:41:37', '2020-04-05 07:41:37'), (1, 41, 'App\\Answer', 1, '2020-04-05 07:41:37', '2020-04-05 07:41:37'), (1, 42, 'App\\Answer', -1, '2020-04-05 07:41:37', '2020-04-05 07:41:37'), (1, 43, 'App\\Answer', 1, '2020-04-05 07:41:37', '2020-04-05 07:41:37'), (1, 44, 'App\\Answer', -1, '2020-04-05 07:41:38', '2020-04-05 07:41:38'), (1, 45, 'App\\Answer', 1, '2020-04-05 07:41:38', '2020-04-05 07:41:38'), (1, 46, 'App\\Answer', 1, '2020-04-05 07:41:38', '2020-04-05 07:41:38'), (1, 47, 'App\\Answer', -1, '2020-04-05 07:41:38', '2020-04-05 07:41:38'), (1, 48, 'App\\Answer', -1, '2020-04-05 07:41:39', '2020-04-05 07:41:39'), (1, 49, 'App\\Answer', 1, '2020-04-05 07:41:39', '2020-04-05 07:41:39'), (1, 50, 'App\\Answer', 1, '2020-04-05 07:41:39', '2020-04-05 07:41:39'), (1, 51, 'App\\Answer', 1, '2020-04-05 07:41:40', '2020-04-05 07:41:40'), (1, 52, 'App\\Answer', -1, '2020-04-05 07:41:40', '2020-04-05 07:41:40'), (1, 53, 'App\\Answer', -1, '2020-04-05 07:41:40', '2020-04-05 07:41:40'), (1, 54, 'App\\Answer', 1, '2020-04-05 07:41:41', '2020-04-05 07:41:41'), (1, 55, 'App\\Answer', -1, '2020-04-05 07:41:41', '2020-04-05 07:41:41'), (1, 56, 'App\\Answer', 1, '2020-04-05 07:41:41', '2020-04-05 07:41:41'), (1, 57, 'App\\Answer', 1, '2020-04-05 07:41:41', '2020-04-05 07:41:41'), (1, 58, 'App\\Answer', -1, '2020-04-05 07:41:42', '2020-04-05 07:41:42'), (1, 59, 'App\\Answer', -1, '2020-04-05 07:41:42', '2020-04-05 07:41:42'), (1, 60, 'App\\Answer', -1, '2020-04-05 07:41:42', '2020-04-05 07:41:42'), (1, 61, 'App\\Answer', 1, '2020-04-05 07:41:43', '2020-04-05 07:41:43'), (1, 62, 'App\\Answer', -1, '2020-04-05 07:41:43', '2020-04-05 07:41:43'), (1, 63, 'App\\Answer', 1, '2020-04-05 07:41:43', '2020-04-05 07:41:43'), (2, 1, 'App\\Answer', 1, '2020-04-05 07:41:27', '2020-04-05 07:41:27'), (2, 1, 'App\\Question', -1, '2020-04-05 07:41:22', '2020-04-05 07:41:22'), (2, 2, 'App\\Question', 1, '2020-04-05 07:41:22', '2020-04-05 07:41:22'), (2, 3, 'App\\Answer', 1, '2020-04-05 07:41:27', '2020-04-05 07:41:27'), (2, 3, 'App\\Question', -1, '2020-04-05 07:41:23', '2020-04-05 07:41:23'), (2, 4, 'App\\Answer', 1, '2020-04-05 07:41:27', '2020-04-05 07:41:27'), (2, 4, 'App\\Question', 1, '2020-04-05 07:41:23', '2020-04-05 07:41:23'), (2, 5, 'App\\Answer', 1, '2020-04-05 07:41:28', '2020-04-05 07:41:28'), (2, 5, 'App\\Question', 1, '2020-04-05 07:41:23', '2020-04-05 07:41:23'), (2, 6, 'App\\Answer', 1, '2020-04-05 07:41:28', '2020-04-05 07:41:28'), (2, 7, 'App\\Question', 1, '2020-04-05 07:41:24', '2020-04-05 07:41:24'), (2, 9, 'App\\Answer', 1, '2020-04-05 07:41:28', '2020-04-05 07:41:28'), (2, 9, 'App\\Question', -1, '2020-04-05 07:41:24', '2020-04-05 07:41:24'), (2, 10, 'App\\Question', -1, '2020-04-05 07:41:24', '2020-04-05 07:41:24'), (2, 11, 'App\\Answer', -1, '2020-04-05 07:41:29', '2020-04-05 07:41:29'), (2, 12, 'App\\Answer', -1, '2020-04-05 07:41:29', '2020-04-05 07:41:29'), (2, 12, 'App\\Question', 1, '2020-04-05 07:41:25', '2020-04-05 07:41:25'), (2, 13, 'App\\Answer', 1, '2020-04-05 07:41:30', '2020-04-05 07:41:30'), (2, 14, 'App\\Question', -1, '2020-04-05 07:41:25', '2020-04-05 07:41:25'), (2, 15, 'App\\Answer', -1, '2020-04-05 07:41:30', '2020-04-05 07:41:30'), (2, 15, 'App\\Question', 1, '2020-04-05 07:41:25', '2020-04-05 07:41:25'), (2, 17, 'App\\Answer', 1, '2020-04-05 07:41:31', '2020-04-05 07:41:31'), (2, 17, 'App\\Question', -1, '2020-04-05 07:41:26', '2020-04-05 07:41:26'), (2, 18, 'App\\Answer', 1, '2020-04-05 07:41:31', '2020-04-05 07:41:31'), (2, 19, 'App\\Answer', -1, '2020-04-05 07:41:31', '2020-04-05 07:41:31'), (2, 19, 'App\\Question', 1, '2020-04-05 07:41:26', '2020-04-05 07:41:26'), (2, 22, 'App\\Answer', -1, '2020-04-05 07:41:32', '2020-04-05 07:41:32'), (2, 23, 'App\\Answer', -1, '2020-04-05 07:41:32', '2020-04-05 07:41:32'), (2, 26, 'App\\Answer', -1, '2020-04-05 07:41:33', '2020-04-05 07:41:33'), (2, 27, 'App\\Answer', 1, '2020-04-05 07:41:33', '2020-04-05 07:41:33'), (2, 28, 'App\\Answer', 1, '2020-04-05 07:41:34', '2020-04-05 07:41:34'), (2, 29, 'App\\Answer', 1, '2020-04-05 07:41:34', '2020-04-05 07:41:34'), (2, 30, 'App\\Answer', 1, '2020-04-05 07:41:34', '2020-04-05 07:41:34'), (2, 31, 'App\\Answer', -1, '2020-04-05 07:41:35', '2020-04-05 07:41:35'), (2, 33, 'App\\Answer', 1, '2020-04-05 07:41:35', '2020-04-05 07:41:35'), (2, 36, 'App\\Answer', -1, '2020-04-05 07:41:35', '2020-04-05 07:41:35'), (2, 37, 'App\\Answer', 1, '2020-04-05 07:41:36', '2020-04-05 07:41:36'), (2, 38, 'App\\Answer', 1, '2020-04-05 07:41:36', '2020-04-05 07:41:36'), (2, 39, 'App\\Answer', 1, '2020-04-05 07:41:37', '2020-04-05 07:41:37'), (2, 40, 'App\\Answer', 1, '2020-04-05 07:41:37', '2020-04-05 07:41:37'), (2, 41, 'App\\Answer', -1, '2020-04-05 07:41:37', '2020-04-05 07:41:37'), (2, 42, 'App\\Answer', -1, '2020-04-05 07:41:37', '2020-04-05 07:41:37'), (2, 43, 'App\\Answer', -1, '2020-04-05 07:41:37', '2020-04-05 07:41:37'), (2, 44, 'App\\Answer', -1, '2020-04-05 07:41:38', '2020-04-05 07:41:38'), (2, 45, 'App\\Answer', 1, '2020-04-05 07:41:38', '2020-04-05 07:41:38'), (2, 46, 'App\\Answer', 1, '2020-04-05 07:41:38', '2020-04-05 07:41:38'), (2, 47, 'App\\Answer', 1, '2020-04-05 07:41:38', '2020-04-05 07:41:38'), (2, 48, 'App\\Answer', -1, '2020-04-05 07:41:39', '2020-04-05 07:41:39'), (2, 49, 'App\\Answer', 1, '2020-04-05 07:41:39', '2020-04-05 07:41:39'), (2, 50, 'App\\Answer', -1, '2020-04-05 07:41:40', '2020-04-05 07:41:40'), (2, 51, 'App\\Answer', -1, '2020-04-05 07:41:40', '2020-04-05 07:41:40'), (2, 52, 'App\\Answer', -1, '2020-04-05 07:41:40', '2020-04-05 07:41:40'), (2, 53, 'App\\Answer', -1, '2020-04-05 07:41:40', '2020-04-05 07:41:40'), (2, 54, 'App\\Answer', 1, '2020-04-05 07:41:41', '2020-04-05 07:41:41'), (2, 56, 'App\\Answer', 1, '2020-04-05 07:41:41', '2020-04-05 07:41:41'), (2, 57, 'App\\Answer', -1, '2020-04-05 07:41:41', '2020-04-05 07:41:41'), (2, 58, 'App\\Answer', -1, '2020-04-05 07:41:42', '2020-04-05 07:41:42'), (2, 59, 'App\\Answer', -1, '2020-04-05 07:41:42', '2020-04-05 07:41:42'), (2, 60, 'App\\Answer', -1, '2020-04-05 07:41:42', '2020-04-05 07:41:42'), (2, 61, 'App\\Answer', 1, '2020-04-05 07:41:43', '2020-04-05 07:41:43'), (2, 63, 'App\\Answer', 1, '2020-04-05 07:41:43', '2020-04-05 07:41:43'), (3, 4, 'App\\Answer', -1, '2020-04-05 07:41:27', '2020-04-05 07:41:27'), (3, 4, 'App\\Question', 1, '2020-04-05 07:41:23', '2020-04-05 07:41:23'), (3, 5, 'App\\Answer', 1, '2020-04-05 07:41:28', '2020-04-05 07:41:28'), (3, 9, 'App\\Answer', -1, '2020-04-05 07:41:28', '2020-04-05 07:41:28'), (3, 9, 'App\\Question', -1, '2020-04-05 07:41:24', '2020-04-05 07:41:24'), (3, 11, 'App\\Answer', 1, '2020-04-05 07:41:29', '2020-04-05 07:41:29'), (3, 13, 'App\\Answer', -1, '2020-04-05 07:41:30', '2020-04-05 07:41:30'), (3, 15, 'App\\Question', -1, '2020-04-05 07:41:25', '2020-04-05 07:41:25'), (3, 17, 'App\\Question', 1, '2020-04-05 07:41:26', '2020-04-05 07:41:26'), (3, 18, 'App\\Answer', 1, '2020-04-05 07:41:31', '2020-04-05 07:41:31'), (3, 19, 'App\\Answer', 1, '2020-04-05 07:41:31', '2020-04-05 07:41:31'), (3, 19, 'App\\Question', 1, '2020-04-05 07:41:26', '2020-04-05 07:41:26'), (3, 22, 'App\\Answer', -1, '2020-04-05 07:41:32', '2020-04-05 07:41:32'), (3, 27, 'App\\Answer', -1, '2020-04-05 07:41:33', '2020-04-05 07:41:33'), (3, 29, 'App\\Answer', 1, '2020-04-05 07:41:34', '2020-04-05 07:41:34'), (3, 30, 'App\\Answer', 1, '2020-04-05 07:41:34', '2020-04-05 07:41:34'), (3, 36, 'App\\Answer', -1, '2020-04-05 07:41:36', '2020-04-05 07:41:36'), (3, 37, 'App\\Answer', -1, '2020-04-05 07:41:36', '2020-04-05 07:41:36'), (3, 38, 'App\\Answer', 1, '2020-04-05 07:41:36', '2020-04-05 07:41:36'), (3, 43, 'App\\Answer', 1, '2020-04-05 07:41:37', '2020-04-05 07:41:37'), (3, 44, 'App\\Answer', 1, '2020-04-05 07:41:38', '2020-04-05 07:41:38'), (3, 47, 'App\\Answer', 1, '2020-04-05 07:41:39', '2020-04-05 07:41:39'), (3, 48, 'App\\Answer', 1, '2020-04-05 07:41:39', '2020-04-05 07:41:39'), (3, 49, 'App\\Answer', 1, '2020-04-05 07:41:39', '2020-04-05 07:41:39'), (3, 50, 'App\\Answer', 1, '2020-04-05 07:41:40', '2020-04-05 07:41:40'), (3, 51, 'App\\Answer', 1, '2020-04-05 07:41:40', '2020-04-05 07:41:40'), (3, 52, 'App\\Answer', 1, '2020-04-05 07:41:40', '2020-04-05 07:41:40'), (3, 53, 'App\\Answer', -1, '2020-04-05 07:41:41', '2020-04-05 07:41:41'), (3, 54, 'App\\Answer', 1, '2020-04-05 07:41:41', '2020-04-05 07:41:41'), (3, 58, 'App\\Answer', -1, '2020-04-05 07:41:42', '2020-04-05 07:41:42'), (3, 60, 'App\\Answer', -1, '2020-04-05 07:41:42', '2020-04-05 07:41:42'), (3, 61, 'App\\Answer', -1, '2020-04-05 07:41:43', '2020-04-05 07:41:43'), (3, 63, 'App\\Answer', -1, '2020-04-05 07:41:43', '2020-04-05 07:41:43'), (4, 4, 'App\\Question', 1, '2020-04-05 07:41:23', '2020-04-05 07:41:23'), (4, 9, 'App\\Answer', 1, '2020-04-05 07:41:29', '2020-04-05 07:41:29'), (4, 15, 'App\\Question', -1, '2020-04-05 07:41:26', '2020-04-05 07:41:26'), (4, 19, 'App\\Answer', 1, '2020-04-05 07:41:31', '2020-04-05 07:41:31'), (4, 19, 'App\\Question', 1, '2020-04-05 07:41:27', '2020-04-05 07:41:27'), (4, 22, 'App\\Answer', 1, '2020-04-05 07:41:32', '2020-04-05 07:41:32'), (4, 27, 'App\\Answer', 1, '2020-04-05 07:41:34', '2020-04-05 07:41:34'), (4, 30, 'App\\Answer', 1, '2020-04-05 07:41:35', '2020-04-05 07:41:35'), (4, 43, 'App\\Answer', 1, '2020-04-05 07:41:38', '2020-04-05 07:41:38'), (4, 47, 'App\\Answer', 1, '2020-04-05 07:41:39', '2020-04-05 07:41:39'), (4, 54, 'App\\Answer', 1, '2020-04-05 07:41:41', '2020-04-05 07:41:41'), (4, 60, 'App\\Answer', 1, '2020-04-05 07:41:42', '2020-04-05 07:41:42'), (4, 63, 'App\\Answer', -1, '2020-04-05 07:41:43', '2020-04-05 07:41:43'), (5, 9, 'App\\Answer', 1, '2020-04-05 07:41:29', '2020-04-05 07:41:29'), (5, 19, 'App\\Question', 1, '2020-04-05 07:41:27', '2020-04-05 07:41:27'), (5, 60, 'App\\Answer', -1, '2020-04-05 07:41:42', '2020-04-05 07:41:42'), (6, 16, 'App\\Question', 1, '2020-04-05 07:43:42', '2020-04-05 07:43:50'), (6, 19, 'App\\Question', 1, '2020-04-05 07:55:15', '2020-04-05 07:55:15'), (6, 20, 'App\\Question', 1, '2020-04-05 07:55:01', '2020-04-05 07:55:01'), (6, 23, 'App\\Question', 1, '2020-04-05 11:21:28', '2020-04-05 11:21:28'), (6, 63, 'App\\Answer', 1, '2020-04-05 07:55:23', '2020-04-05 07:55:23'), (6, 66, 'App\\Answer', 1, '2020-04-05 07:54:52', '2020-04-05 07:54:52'), (7, 64, 'App\\Answer', 1, '2020-04-05 07:53:25', '2020-04-05 07:53:25'); -- -- Indexes for dumped tables -- -- -- Indexes for table `answers` -- ALTER TABLE `answers` ADD PRIMARY KEY (`id`); -- -- Indexes for table `failed_jobs` -- ALTER TABLE `failed_jobs` ADD PRIMARY KEY (`id`); -- -- Indexes for table `favorites` -- ALTER TABLE `favorites` ADD UNIQUE KEY `favorites_user_id_question_id_unique` (`user_id`,`question_id`); -- -- Indexes for table `migrations` -- ALTER TABLE `migrations` ADD PRIMARY KEY (`id`); -- -- Indexes for table `password_resets` -- ALTER TABLE `password_resets` ADD KEY `password_resets_email_index` (`email`); -- -- Indexes for table `questions` -- ALTER TABLE `questions` ADD PRIMARY KEY (`id`), ADD UNIQUE KEY `questions_slug_unique` (`slug`), ADD KEY `questions_user_id_foreign` (`user_id`); -- -- Indexes for table `users` -- ALTER TABLE `users` ADD PRIMARY KEY (`id`), ADD UNIQUE KEY `users_email_unique` (`email`); -- -- Indexes for table `votables` -- ALTER TABLE `votables` ADD UNIQUE KEY `votables_user_id_votable_id_votable_type_unique` (`user_id`,`votable_id`,`votable_type`); -- -- AUTO_INCREMENT for dumped tables -- -- -- AUTO_INCREMENT for table `answers` -- ALTER TABLE `answers` MODIFY `id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=70; -- -- AUTO_INCREMENT for table `failed_jobs` -- ALTER TABLE `failed_jobs` MODIFY `id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT; -- -- AUTO_INCREMENT for table `migrations` -- ALTER TABLE `migrations` MODIFY `id` int(10) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=10; -- -- AUTO_INCREMENT for table `questions` -- ALTER TABLE `questions` MODIFY `id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=24; -- -- AUTO_INCREMENT for table `users` -- ALTER TABLE `users` MODIFY `id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=8; -- -- Constraints for dumped tables -- -- -- Constraints for table `questions` -- ALTER TABLE `questions` ADD CONSTRAINT `questions_user_id_foreign` FOREIGN KEY (`user_id`) REFERENCES `users` (`id`) ON DELETE CASCADE; COMMIT; /*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */; /*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */; /*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;

/* Warnings: - You are about to drop the column `age` on the `User` table. All the data in the column will be lost. - You are about to drop the `Post` table. If the table is not empty, all the data it contains will be lost. - A unique constraint covering the columns `[userName]` on the table `User` will be added. If there are existing duplicate values, this will fail. */ -- DropForeignKey ALTER TABLE "Post" DROP CONSTRAINT "Post_authorId_fkey"; -- AlterTable ALTER TABLE "User" DROP COLUMN "age"; -- DropTable DROP TABLE "Post"; -- CreateIndex CREATE UNIQUE INDEX "User_userName_key" ON "User"("userName");

--create table experience CREATE TABLE IF NOT EXISTS experience ( id SERIAL PRIMARY KEY, user_id INTEGER REFERENCES accounts(id), employer VARCHAR (100) NOT NULL, role VARCHAR(200) NOT NULL, start_month SMALLINT NULL, start_year SMALLINT NOT NULL, end_month SMALLINT NULL, end_year SMALLINT NOT NULL CHECK (end_year >= start_year), previous_id INTEGER NOT NULL );

<reponame>RecroGridFramework/Recrovit.RecroGridFramework.Identity<filename>src/Recrovit.RecroGridFramework.Identity/App_Data/Recrovit.RGF/Import/RGF.Identity/Oracle/rgf_identity.sql RGF.CMD.Import RGF.Identity\identity_recrogrid_entity.json / RGF.CMD.Import RGF.Identity\identity_rgf_menu.json /

CREATE TABLE votes ( id integer PRIMARY KEY, option_name varchar(20), number_of_votes integer ); INSERT INTO votes (id, option_name, number_of_votes) VALUES (1, 'cats', 10); INSERT INTO votes (id, option_name, number_of_votes) VALUES (2, 'dogs', 7);

<gh_stars>1-10 # 新建root角色 INSERT INTO T_SYSTEM_ROLE (name, name_show, des, status) VALUES ('root', 'ROOT管理员', null, 1); # 新建root用户 INSERT INTO T_STAFF (name, account, password, status) VALUES ('ROOT用户', 'root', '<PASSWORD>', 1); # 绑定账户与角色 INSERT INTO T_STAFF_ROLE(staff_id, role_id, des) SELECT t1.id, t2.id, '系统初始化' from T_STAFF t1 ,T_SYSTEM_ROLE t2 where t1.account='root' and t2.name='root' # 新建root相关的前端路由信息 INSERT INTO T_SYSTEM_ROUTE (path, parent, async, des) VALUES ('/root', null, 1, 'Root功能'); INSERT INTO T_SYSTEM_ROUTE (path, parent, async, des) VALUES ('/root/permission', 1, 1, '权限细节'); INSERT INTO T_SYSTEM_ROUTE (path, parent, async, des) VALUES ('/root/menu', 1, 1, '路由权限'); INSERT INTO T_SYSTEM_ROUTE (path, parent, async, des) VALUES ('/root/role', 1, 1, '角色管理'); # 绑定路由与角色 INSERT INTO T_SYSTEM_ROUTE_ROLE (route_id, role_id) SELECT t1.id, t2.id FROM T_SYSTEM_ROUTE t1, T_SYSTEM_ROLE t2 WHERE t1.path LIKE '/root%' and t2.name = 'root' # 添加前端组件权限点 INSERT INTO T_SYSTEM_PERMISSION_NODE (name, des, status, module) VALUES ('button_add', '添加用户按钮', 1, 'UserManagement'); INSERT INTO T_SYSTEM_PERMISSION_NODE (name, des, status, module) VALUES ('button_forbidden', '禁用用户按钮', 1, 'UserManagement'); INSERT INTO T_SYSTEM_PERMISSION_NODE (name, des, status, module) VALUES ('button_role_setting', '角色配置按钮', 1, 'UserManagement'); INSERT INTO T_SYSTEM_PERMISSION_NODE (name, des, status, module) VALUES ('button_password_reset', '重置密码按钮', 1, 'UserManagement'); INSERT INTO T_SYSTEM_PERMISSION_NODE (name, des, status, module) VALUES ('button_lift', '用户解禁按钮', 1, 'UserManagement'); INSERT INTO T_SYSTEM_PERMISSION_NODE (name, des, status, module) VALUES ('button_dimission', '用户离职按钮', 1, 'UserManagement'); INSERT INTO T_SYSTEM_PERMISSION_NODE (name, des, status, module) VALUES ('tab_add', '新增公告tab栏', 1, 'InformManagement'); INSERT INTO T_SYSTEM_PERMISSION_NODE (name, des, status, module) VALUES ('top_and_cancel', '置顶公告以及取消置顶', 1, 'InformTable'); INSERT INTO T_SYSTEM_PERMISSION_NODE (name, des, status, module) VALUES ('cancel', '撤销公告', 1, 'InformTable'); INSERT INTO T_SYSTEM_PERMISSION_NODE (name, des, status, module) VALUES ('outdate', '设置公告过期', 1, 'InformTable');

<gh_stars>10-100 -- file:rowsecurity.sql ln:29 expect:true CREATE ROLE regress_rls_group2 NOLOGIN

<filename>vtools/ContourLab/docs/love.cont.ddl //#include <Contour.ddl> Contour Data= { { { { 'O' , True , True , True } , 0 , &Pad0 }, { { 'radius' , True , True , True } , 1 , &Pad1 }, { { 'rat' , True , True , True } , 2 , &Pad2 }, { { 'blen' , True , True , True } , 3 , &Pad3 }, { { 'alen' , True , True , True } , 4 , &Pad4 }, { { 'S1' , True , True , True } , 5 , &Pad5 }, { { 'S2' , True , True , True } , 6 , &Pad6 }, { { 'S3' , True , True , True } , 7 , &Pad7 }, { { 'S4' , True , True , True } , 8 , &Pad8 }, { { 'S5' , True , True , True } , 9 , &Pad9 }, { { 'S6' , True , True , True } , 10 , &Pad10 } }, { { { 'cir' , True , True , False } , 0 , &F0 }, { { 'height' , True , True , True } , 1 , &F1 }, { { 'Top' , True , True , True } , 2 , &F2 }, { { 'anchor' , False , True , False } , 3 , &F3 }, { { 'l' , True , True , False } , 4 , &F4 }, { { 'B' , True , True , True } , 5 , &F5 }, { { 'A' , True , True , True } , 6 , &F6 }, { { 'T1' , True , True , True } , 7 , &F7 }, { { 'T2' , True , True , True } , 8 , &F8 }, { { 'T3' , True , True , True } , 9 , &F9 }, { { 'T4' , True , True , True } , 10 , &F10 }, { { 'T5' , True , True , True } , 11 , &F11 }, { { 'T6' , True , True , True } , 12 , &F12 }, { { 'step1' , True , True , True } , 13 , &F13 }, { { 'step2' , True , True , True } , 14 , &F14 }, { { 'loop' , True , True , True } , 15 , &F15 } } }; Point Pad0 = { {77C0000000000000h,-54} , {5340000000000000h,-54} , 0 }; Length Pad1 = { {4C80000000000000h,-54} , 0 }; Ratio Pad2 = { {6000000000000000h,-63} , 0 }; Length Pad3 = { {6000000000000000h,-55} , 0 }; Length Pad4 = { {4880000000000000h,-55} , 0 }; Point Pad5 = { {6A80000000000000h,-54} , {4C80000000000000h,-55} , 0 }; Point Pad6 = { {5580000000000000h,-54} , {5100000000000000h,-55} , 0 }; Point Pad7 = { {4A00000000000000h,-54} , {6E80000000000000h,-55} , 0 }; Point Pad8 = { {4B00000000000000h,-54} , {4B80000000000000h,-54} , 0 }; Point Pad9 = { {59C0000000000000h,-54} , {5FC0000000000000h,-54} , 0 }; Point Pad10 = { {6940000000000000h,-54} , {6E40000000000000h,-54} , 0 }; CircleOf F0 = { Data.pads+0 , Data.pads+1 }; Mul F1 = { Data.pads+2 , Data.pads+1 }; Up F2 = { Data.formulas+1 , Data.pads+0 }; LoopOf F3 = { { Data.pads+0 , Data.formulas+2 } }; LineOf F4 = { Data.pads+0 , Data.formulas+2 }; Down F5 = { Data.pads+3 , Data.pads+0 }; Up F6 = { Data.pads+4 , Data.pads+0 }; Right F7 = { &F30 , Data.pads+5 }; Mul F30 = { &F32 , &F33 }; Ratio F32 = { {4000000000000000h,-61} , 0 }; LengthOf F33 = { Data.pads+5 , &F35 }; Proj F35 = { Data.formulas+4 , Data.pads+5 }; Right F8 = { &F38 , Data.pads+6 }; Mul F38 = { &F40 , &F41 }; Ratio F40 = { {4000000000000000h,-61} , 0 }; LengthOf F41 = { Data.pads+6 , &F43 }; Proj F43 = { Data.formulas+4 , Data.pads+6 }; Right F9 = { &F46 , Data.pads+7 }; Mul F46 = { &F48 , &F49 }; Ratio F48 = { {4000000000000000h,-61} , 0 }; LengthOf F49 = { Data.pads+7 , &F51 }; Proj F51 = { Data.formulas+4 , Data.pads+7 }; Right F10 = { &F54 , Data.pads+8 }; Mul F54 = { &F56 , &F57 }; Ratio F56 = { {4000000000000000h,-61} , 0 }; LengthOf F57 = { Data.pads+8 , &F59 }; Proj F59 = { Data.formulas+4 , Data.pads+8 }; Right F11 = { &F62 , Data.pads+9 }; Mul F62 = { &F64 , &F65 }; Ratio F64 = { {4000000000000000h,-61} , 0 }; LengthOf F65 = { Data.pads+9 , &F67 }; Proj F67 = { Data.formulas+4 , Data.pads+9 }; Right F12 = { &F70 , Data.pads+10 }; Mul F70 = { &F72 , &F73 }; Ratio F72 = { {4000000000000000h,-61} , 0 }; LengthOf F73 = { Data.pads+10 , &F75 }; Proj F75 = { Data.formulas+4 , Data.pads+10 }; StepOf F13 = { { Data.formulas+6 , Data.pads+5 , Data.pads+6 , Data.pads+7 , Data.pads+8 , Data.pads+9 , Data.pads+10 } }; StepOf F14 = { { Data.formulas+5 , Data.formulas+12 , Data.formulas+11 , Data.formulas+10 , Data.formulas+9 , Data.formulas+8 , Data.formulas+7 } }; BLoopOf F15 = { { Data.formulas+13 , Data.formulas+14 } }; Loop Contour_anchor= { { { { {77C0000000000000h,-54} , {5340000000000000h,-54} , 0 } , False }, { { {77C0000000000000h,-54} , {6780000000000000h,-56} , 0 } , False } }, 0 }; /* SmoothDot Contour_anchor[2]= { { { 490496 , 340992 } , Smooth::DotSimple }, { { 490496 , 105984 } , Smooth::DotSimple } }; */ Loop Contour_loop= { { { { {77C0000000000000h,-54} , {5E00000000000000h,-55} , 0 } , True }, { { {6A80000000000000h,-54} , {4C80000000000000h,-55} , 0 } , False }, { { {5580000000000000h,-54} , {5100000000000000h,-55} , 0 } , False }, { { {4A00000000000000h,-54} , {6E80000000000000h,-55} , 0 } , False }, { { {4B00000000000000h,-54} , {4B80000000000000h,-54} , 0 } , False }, { { {59C0000000000000h,-54} , {5FC0000000000000h,-54} , 0 } , False }, { { {6940000000000000h,-54} , {6E40000000000000h,-54} , 0 } , False }, { { {77C0000000000000h,-54} , {41A0000000000000h,-53} , 0 } , True }, { { {4320000000000000h,-53} , {6E40000000000000h,-54} , 0 } , False }, { { {4AE0000000000000h,-53} , {5FC0000000000000h,-54} , 0 } , False }, { { {5240000000000000h,-53} , {4B80000000000000h,-54} , 0 } , False }, { { {52C0000000000000h,-53} , {6E80000000000000h,-55} , 0 } , False }, { { {4D00000000000000h,-53} , {5100000000000000h,-55} , 0 } , False }, { { {4280000000000000h,-53} , {4C80000000000000h,-55} , 0 } , False } }, 0 }; /* SmoothDot Contour_loop[14]= { { { 490496 , 192512 } , Smooth::DotBreak }, { { 436224 , 156672 } , Smooth::DotSimple }, { { 350208 , 165888 } , Smooth::DotSimple }, { { 303104 , 226304 } , Smooth::DotSimple }, { { 307200 , 309248 } , Smooth::DotSimple }, { { 367616 , 392192 } , Smooth::DotSimple }, { { 431104 , 451584 } , Smooth::DotSimple }, { { 490496 , 537600 } , Smooth::DotBreak }, { { 549888 , 451584 } , Smooth::DotSimple }, { { 613376 , 392192 } , Smooth::DotSimple }, { { 673792 , 309248 } , Smooth::DotSimple }, { { 677888 , 226304 } , Smooth::DotSimple }, { { 630784 , 165888 } , Smooth::DotSimple }, { { 544768 , 156672 } , Smooth::DotSimple } }; */

<filename>services/product/src/main/resources/scripts/jemmy_product.sql<gh_stars>0 CREATE DATABASE IF NOT EXISTS `jemmy_product` /*!40100 DEFAULT CHARACTER SET utf8 */; USE `jemmy_product`; -- MySQL dump 10.13 Distrib 5.7.17, for Win64 (x86_64) -- -- Host: 192.168.99.100 Database: jemmy_product -- ------------------------------------------------------ -- Server version 5.7.22 /*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */; /*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */; /*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */; /*!40101 SET NAMES utf8 */; /*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */; /*!40103 SET TIME_ZONE='+00:00' */; /*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */; /*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */; /*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */; /*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */; -- -- Table structure for table `product` -- DROP TABLE IF EXISTS `product`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `product` ( `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `name` varchar(64) NOT NULL DEFAULT '', `price` decimal(5,2) NOT NULL COMMENT '价格', `num` int(10) unsigned NOT NULL DEFAULT '0' COMMENT '数量', `state` tinyint(4) NOT NULL DEFAULT '0', `create_time` datetime NOT NULL, `update_time` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, `delete_time` datetime DEFAULT NULL, PRIMARY KEY (`id`) ) ENGINE=InnoDB AUTO_INCREMENT=3 DEFAULT CHARSET=utf8 COMMENT='商品表'; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `product` -- LOCK TABLES `product` WRITE; /*!40000 ALTER TABLE `product` DISABLE KEYS */; INSERT INTO `product` VALUES (1,'金条',265.32,10,0,'2018-10-13 12:59:06','2018-10-13 04:59:06',NULL),(2,'项链',56.21,100,0,'0000-00-00 00:00:00','2018-10-13 05:00:03',NULL); /*!40000 ALTER TABLE `product` ENABLE KEYS */; UNLOCK TABLES; /*!40103 SET TIME_ZONE=@OLD_TIME_ZONE */; /*!40101 SET SQL_MODE=@OLD_SQL_MODE */; /*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */; /*!40014 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS */; /*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */; /*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */; /*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */; /*!40111 SET SQL_NOTES=@OLD_SQL_NOTES */; -- Dump completed on 2018-10-14 14:04:21

<reponame>aravi5/drill-test-framework select s_address, s_phone, s_acctbal from `filter/pushdown/varchar_decimal/new_metadata_file/1.14.0/supplier` where not s_acctbal > -900;

<reponame>robertsaxby/migrating_dwh_to_bq select s.* from `da304_staging.Store_sales` s where s.d_date= cast('{{params.partition_date}}' as date)

CREATE TABLE TEST_TABLE_2 ( OID CHARACTER (36) PRIMARY KEY );

<reponame>jensim/sourcegraph BEGIN; -- Add default values for git commit author (name and email) UPDATE changeset_specs SET spec = spec || json_build_object( 'commits', json_build_array( spec->'commits'->0 || '{"authorName": "Sourcegraph", "authorEmail": "<EMAIL>"}' ) )::jsonb WHERE jsonb_array_length(spec->'commits') > 0; COMMIT;

\qecho \qecho === Deploy Schema [schema_name_second] \qecho set schema 'schema_name_second' \include ./service/install_script_2_schema_name_second_BEFORE_0.sql

<filename>Tellma.Database.Application/dbo/User Defined Types/dbo.LookupDefinitionList.sql CREATE TYPE [dbo].[LookupDefinitionList] AS TABLE ( [Index] INT PRIMARY KEY DEFAULT 0, [Id] INT NOT NULL DEFAULT 0, [Code] NVARCHAR (50), [TitleSingular] NVARCHAR (50), [TitleSingular2] NVARCHAR (50), [TitleSingular3] NVARCHAR (50), [TitlePlural] NVARCHAR (50), [TitlePlural2] NVARCHAR (50), [TitlePlural3] NVARCHAR (50), [MainMenuIcon] NVARCHAR (50), [MainMenuSection] NVARCHAR (50), -- Required when the state is "Deployed" [MainMenuSortKey] DECIMAL (9,4) );

/* Navicat Premium Data Transfer Source Server : 本地 Source Server Type : MySQL Source Server Version : 50728 Source Host : localhost:3306 Source Schema : master Target Server Type : MySQL Target Server Version : 50728 File Encoding : 65001 Date: 07/12/2021 21:31:30 */ SET NAMES utf8mb4; SET FOREIGN_KEY_CHECKS = 0; -- ---------------------------- -- Table structure for t_admin -- ---------------------------- DROP TABLE IF EXISTS `t_admin`; CREATE TABLE `t_admin` ( `id` bigint(20) NOT NULL AUTO_INCREMENT COMMENT '主键', `user_name` varchar(63) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NOT NULL DEFAULT '' COMMENT '管理员名称', `avatar` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NULL DEFAULT '' COMMENT '头像图片', `create_time` datetime(0) NULL DEFAULT NULL COMMENT '创建时间', `create_name` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NULL DEFAULT NULL COMMENT '创建者', `update_time` datetime(0) NULL DEFAULT NULL COMMENT '更新时间', `update_name` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NULL DEFAULT NULL COMMENT '修改者', `version` int(11) NOT NULL DEFAULT 0 COMMENT '乐观锁版本号', `deleted` tinyint(1) NOT NULL DEFAULT 0 COMMENT '逻辑删除', `tenant_id` int(11) NULL DEFAULT NULL COMMENT '租户id', PRIMARY KEY (`id`) USING BTREE ) ENGINE = InnoDB AUTO_INCREMENT = 33 CHARACTER SET = utf8mb4 COLLATE = utf8mb4_general_ci COMMENT = '管理员表' ROW_FORMAT = Dynamic; -- ---------------------------- -- Records of t_admin -- ---------------------------- INSERT INTO `t_admin` VALUES (28, '大白', '000', '2021-09-25 16:51:32', 'testInsertName', '2021-09-25 16:51:32', 'testInsertName', 0, 0, 1); INSERT INTO `t_admin` VALUES (29, '小李子', '000', '2021-09-25 16:52:17', 'testInsertName', '2021-09-25 17:00:59', 'testUpdateName', 1, 0, 2); INSERT INTO `t_admin` VALUES (30, '飞刀', '000', '2021-09-25 18:54:00', 'testInsertName', '2021-09-25 18:54:00', 'testInsertName', 0, 0, 1); INSERT INTO `t_admin` VALUES (31, '测试用户369', '000', '2021-09-27 00:15:19', 'testInsertName', '2021-09-27 00:15:19', 'testInsertName', 0, 0, 1); INSERT INTO `t_admin` VALUES (32, '新增管理员', '000', '2021-12-02 23:13:35', 'testInsertName', '2021-12-02 23:13:35', 'testInsertName', 0, 0, 1); SET FOREIGN_KEY_CHECKS = 1;

select name, data_type, key_id, policies, tags_src, tags, partition, region, tier from aws.aws_ssm_parameter where akas::text = '["{{output.resource_aka.value}}"]'

WITH cte_0 AS (SELECT * FROM other_t0), cte_1 AS (SELECT * FROM other_t1 WHERE thing=$1 AND stuff=$2) SELECT * FROM "t";

-- @testpoint:opengauss关键字binary(非保留)，作为数据库名 --关键字不带引号-成功 drop database if exists binary; create database binary; --清理环境 drop database binary; --关键字带双引号-成功 drop database if exists "binary"; create database "binary"; --清理环境 drop database "binary"; --关键字带单引号-合理报错 drop database if exists 'binary'; create database 'binary'; --关键字带反引号-合理报错 drop database if exists `binary`; create database `binary`;

<reponame>opengauss-mirror/Yat -- @testpoint:opengauss关键字offset(保留)，作为序列名 --关键字不带引号-合理报错 drop sequence if exists offset; create sequence offset start 100 cache 50; --关键字带双引号-成功 drop sequence if exists "offset"; create sequence "offset" start 100 cache 50; --清理环境 drop sequence "offset"; --关键字带单引号-合理报错 drop sequence if exists 'offset'; create sequence 'offset' start 100 cache 50; --关键字带反引号-合理报错 drop sequence if exists `offset`; create sequence `offset` start 100 cache 50;

-- phpMyAdmin SQL Dump -- version 5.0.4 -- https://www.phpmyadmin.net/ -- -- Host: 1192.168.127.12 -- Generation Time: Aug 08, 2021 at 08:24 PM -- Server version: 10.4.17-MariaDB -- PHP Version: 8.0.2 SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO"; START TRANSACTION; SET time_zone = "+00:00"; /*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */; /*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */; /*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */; /*!40101 SET NAMES utf8mb4 */; -- -- Database: `todo_app` -- -- -------------------------------------------------------- -- -- Table structure for table `todo` -- CREATE TABLE `todo` ( `id` int(11) NOT NULL, `name` varchar(150) NOT NULL, `short_desc` varchar(255) NOT NULL, `long_desc` text NOT NULL, `date_added` datetime NOT NULL DEFAULT current_timestamp(), `date_modified` datetime DEFAULT NULL ON UPDATE current_timestamp(), `status` tinyint(1) NOT NULL DEFAULT 1 COMMENT '1 : active, 2 : completed' ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4; -- -- Dumping data for table `todo` -- INSERT INTO `todo` (`id`, `name`, `short_desc`, `long_desc`, `date_added`, `date_modified`, `status`) VALUES (1, 'test', 'short description', 'long description', '2021-07-31 13:37:01', '2021-07-31 17:24:57', 2), (2, 'new todo', 'this is short description', 'this is long description\r\n', '2021-07-31 17:28:27', NULL, 1), (3, 'new todo', 'this is short description', 'this is long description\r\n', '2021-07-31 17:28:27', '2021-07-31 17:31:06', 0); -- -- Indexes for dumped tables -- -- -- Indexes for table `todo` -- ALTER TABLE `todo` ADD PRIMARY KEY (`id`); -- -- AUTO_INCREMENT for dumped tables -- -- -- AUTO_INCREMENT for table `todo` -- ALTER TABLE `todo` MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=4; COMMIT; /*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */; /*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */; /*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;

INSERT INTO `users` (`id`, `username`, `lastpoll`) VALUES (1, 'testuser1', NULL); INSERT INTO `users` (`id`, `username`, `lastpoll`) VALUES (2, 'testuser2', NULL); INSERT INTO `profiles` (`id`, `name`) VALUES (1, 'testprofile1'); INSERT INTO `profiles` (`id`, `name`) VALUES (2, 'testprofile2'); INSERT INTO `profile_users` (`id`, `userID`, `profileID`) VALUES (1, 1, 1); INSERT INTO `profile_users` (`id`, `userID`, `profileID`) VALUES (2, 1, 2); INSERT INTO `profile_users` (`id`, `userID`, `profileID`) VALUES (3, 2, 1);

<filename>dump_base_de_datos.sql<gh_stars>0 DROP DATABASE IF EXISTS lechuapp; CREATE DATABASE lechuapp; USE lechuapp; DROP TABLE IF EXISTS client; CREATE TABLE client( id INT NOT NULL AUTO_INCREMENT PRIMARY KEY, nombre VARCHAR(50) NOT NULL, telefono VARCHAR(50) NOT NULL ); INSERT INTO client (nombre,telefono) VALUES ('<NAME>', '3517897553'), ('<NAME>', '4880544'), ('<NAME>', '4444444'), ('<NAME>', '4889765'), ('<NAME>', '4456789'), ('pepsi', '4564433'), ('covid19', '4697645'), ('comadreja', '4778756'), ('no lo se rick', '4533376'), ('parece falso', '4569911'); DROP TABLE IF EXISTS client_detail; CREATE TABLE client_detail ( id INT PRIMARY KEY NOT NULL AUTO_INCREMENT, fecNac DATE, faceBook VARCHAR(100), direccion VARCHAR(100), idCliente INT, FOREIGN KEY (idCliente) REFERENCES client(id) ); INSERT INTO client_detail (fecNac,faceBook,direccion,idCliente) VALUES ('1991-04-27','www.facebook.com/coca','en la coqueria',1), ('1993-05-10','www.facebook.com/juanPerez','enla calle Juan',2), ('1991-06-26','www.facebook.com/casas','en el puente',3), ('2000-04-15','www.facebook.com/juarez','villa juarez',4), ('1992-01-11','www.facebook.com/Paco','villa paco',5), ('1993-04-20','www.facebook.com/Pepsi','en la casa de riki',6), ('2020-03-10','www.facebook.com/COVID','CHINAAAAA',7), ('1991-08-07','www.facebook.com/comadreja','en el arbol',8), ('2018-08-21','www.facebook.com/NOLOSE','EN LA TELE',9), ('2018-08-21','www.facebook.com/FALSO','TELE 2',10); DROP TABLE IF EXISTS category; CREATE TABLE category( id INT AUTO_INCREMENT PRIMARY KEY, nombre VARCHAR(50) NOT NULL, estado BIT NOT NULL ); INSERT INTO category(nombre,estado) VALUES("buzos", 1); INSERT INTO category(nombre,estado) VALUES("remeras", 1); INSERT INTO category(nombre,estado) VALUES("camperas", 1); INSERT INTO category(nombre,estado) VALUES("pantalon", 1); INSERT INTO category(nombre,estado) VALUES("medias", 1); INSERT INTO category(nombre,estado) VALUES("camisas", 0); INSERT INTO category(nombre,estado) VALUES("corbatas", 0); INSERT INTO category(nombre,estado) VALUES("babuchas", 0); INSERT INTO category(nombre,estado) VALUES("calzas", 0); INSERT INTO category(nombre,estado) VALUES("jeans", 0); DROP TABLE IF EXISTS product; CREATE TABLE product( id INT AUTO_INCREMENT PRIMARY KEY, nombre VARCHAR(50) NOT NULL, precio DECIMAL(7,2) NOT NULL, stock INT NOT NULL, color VARCHAR(50) NOT NULL, descripcion VARCHAR (100) NOT NULL, fecha_ingreso DATE NOT NULL, id_category INT NOT NULL, FOREIGN KEY(id_category) REFERENCES category(id) ); INSERT INTO product(nombre,precio,stock,color,descripcion,fecha_ingreso,id_category) VALUES ("remera",100,10,"negro","escote en V","2020-05-06", 1); INSERT INTO product(nombre,precio,stock,color,descripcion,fecha_ingreso,id_category) VALUES ("pantalon",50,10,"negro","chupin","2020-05-06", 10); INSERT INTO product(nombre,precio,stock,color,descripcion,fecha_ingreso,id_category) VALUES ("medias",200,10,"negro","largas","2020-05-06", 2); INSERT INTO product(nombre,precio,stock,color,descripcion,fecha_ingreso,id_category) VALUES ("babucha",80,10,"negro","ancha","2020-05-06", 3); INSERT INTO product(nombre,precio,stock,color,descripcion,fecha_ingreso,id_category) VALUES ("camisas",400,10,"negro","manga larga","2020-05-06", 4); INSERT INTO product(nombre,precio,stock,color,descripcion,fecha_ingreso,id_category) VALUES ("calzas",90,10,"negro","deportivas","2020-05-06", 5); INSERT INTO product(nombre,precio,stock,color,descripcion,fecha_ingreso,id_category) VALUES ("corbatas",100,10,"negro","fiesta","2020-05-06", 6); INSERT INTO product(nombre,precio,stock,color,descripcion,fecha_ingreso,id_category) VALUES ("camperas",500,10,"negro","rompeviento","2020-05-06", 7); INSERT INTO product(nombre,precio,stock,color,descripcion,fecha_ingreso,id_category) VALUES ("buzos",40,10,"negro","cangurito","2020-05-06", 8); INSERT INTO product(nombre,precio,stock,color,descripcion,fecha_ingreso,id_category) VALUES ("jeans",100,10,"negro","pata elefante","2020-05-06", 9); DROP TABLE IF EXISTS purchase; CREATE TABLE purchase ( id INT NOT NULL AUTO_INCREMENT PRIMARY KEY, client_id INT NOT NULL, product_id INT NOT NULL, cantidad INT NOT NULL, FOREIGN KEY (client_id) REFERENCES client(id), FOREIGN KEY (product_id) REFERENCES product(id) ); INSERT INTO purchase (client_id,product_id,cantidad) VALUES (1,1,1), (2,2,2),(3,3,3),(4,4,4),(5,5,5),(6,6,6),(7,7,7),(8,8,8),(9,9,9),(10,10,10);

insert into zoo.User_Role (id, name, created_at, updated_at) values (1, 'ADMIN', '2021-04-25 12:19:37', '2021-04-25 12:19:37'), (2, 'VENDEUR', '2021-04-25 12:19:37', '2021-04-25 12:19:37'), (3, 'AGENT D''ACCUEIL', '2021-04-25 12:19:37', '2021-04-25 12:19:37'), (4, 'AGENT D''ENTRETIENT', '2021-04-25 12:19:37', '2021-04-25 12:19:37'), (5, 'VETERINAIRE', '2021-04-25 12:19:38', '2021-04-25 12:19:38'), (6, 'VISITEUR', '2021-04-25 12:19:38', '2021-04-25 12:19:38');

<gh_stars>1-10 -- We use pattern matching against the chart of accounts. Fill in each of the below according to your structure. Feel free -- to define your own categories here as well by just copying an existing SELECT below and being sure to define the Order value -- and put in your own pattern. DECLARE @EarningsPattern nvarchar(max) = '[4-9]%'; DECLARE @DepreciationPattern nvarchar(max) = '[4-5][2-9]25%'; DECLARE @UnbilledShipmentsPattern nvarchar(max) = '11200'; DECLARE @ChangeInARPattern nvarchar(max) = '1010-000'; DECLARE @ChangeInAPPattern nvarchar(max) = '1205-000'; DECLARE @PrepaidExpensesPattern nvarchar(max) = '1090%'; DECLARE @DividendsPaidPattern nvarchar(max) = '38700'; -- Set the site ID to look at DECLARE @SiteID nvarchar(max) = 'MMC'; -- Define whether each type of account needs to be multiplied by -1 DECLARE @EarningsMultiplier INT = -1; DECLARE @DepreciationMultiplier INT = 1; DECLARE @UnbilledShipmentsMultiplier INT = -1; DECLARE @ChangeInARMultiplier INT = -1; DECLARE @ChangeInAPMultiplier INT = -1; DECLARE @PrepaidExpensesMultiplier INT = 1; DECLARE @DividendsPaidMultiplier INT = -1; -- Earnings SELECT p.ACCT_YEAR AS [Year] , p.ACCT_PERIOD AS Period , 0 as 'Order' , 'Earnings' as 'Description' , ISNULL(((SELECT SUM(CURR_BALANCE) FROM ACCOUNT_BALANCE WHERE ACCT_YEAR = p.ACCT_YEAR AND ACCT_PERIOD = p.ACCT_PERIOD AND ACCOUNT_ID LIKE @EarningsPattern)*@EarningsMultiplier), 0) as 'Value' FROM ACCOUNT_PERIOD p with(nolock) WHERE p.SITE_ID = @SiteID -- Depreciation UNION ALL SELECT p.ACCT_YEAR AS [Year] , p.ACCT_PERIOD AS Period , 1 as 'Order' , 'Depreciation' as 'Description' , ISNULL(((SELECT SUM(CURR_BALANCE) FROM ACCOUNT_BALANCE WHERE ACCT_YEAR = p.ACCT_YEAR AND ACCT_PERIOD = p.ACCT_PERIOD AND ACCOUNT_ID LIKE @DepreciationPattern)*@DepreciationMultiplier), 0) as 'Value' FROM ACCOUNT_PERIOD p with(nolock) WHERE p.SITE_ID = @SiteID -- Unbilled Shipments UNION ALL SELECT p.ACCT_YEAR AS [Year] , p.ACCT_PERIOD AS Period , 2 as 'Order' , 'Unbilled Shipments' as 'Description' , ISNULL(((SELECT SUM(CURR_BALANCE) FROM ACCOUNT_BALANCE WHERE ACCT_YEAR = p.ACCT_YEAR AND ACCT_PERIOD = p.ACCT_PERIOD AND ACCOUNT_ID LIKE @UnbilledShipmentsPattern)*@UnbilledShipmentsMultiplier), 0) as 'Value' FROM ACCOUNT_PERIOD p with(nolock) WHERE p.SITE_ID = @SiteID -- Change In AR UNION ALL SELECT p.ACCT_YEAR AS [Year] , p.ACCT_PERIOD AS Period , 3 as 'Order' , 'Change In AR' as 'Description' , ISNULL(((SELECT SUM(CURR_BALANCE) FROM ACCOUNT_BALANCE WHERE ACCT_YEAR = p.ACCT_YEAR AND ACCT_PERIOD = p.ACCT_PERIOD AND ACCOUNT_ID LIKE @ChangeInARPattern)*@ChangeInARMultiplier), 0) as 'Value' FROM ACCOUNT_PERIOD p with(nolock) WHERE p.SITE_ID = @SiteID -- Change In AP UNION ALL SELECT p.ACCT_YEAR AS [Year] , p.ACCT_PERIOD AS Period , 4 as 'Order' , 'Change In AP' as 'Description' , ISNULL(((SELECT SUM(CURR_BALANCE) FROM ACCOUNT_BALANCE WHERE ACCT_YEAR = p.ACCT_YEAR AND ACCT_PERIOD = p.ACCT_PERIOD AND ACCOUNT_ID LIKE @ChangeInAPPattern)*@ChangeInAPMultiplier), 0) as 'Value' FROM ACCOUNT_PERIOD p with(nolock) WHERE p.SITE_ID = @SiteID -- Prepaid Expenses UNION ALL SELECT p.ACCT_YEAR AS [Year] , p.ACCT_PERIOD AS Period , 5 as 'Order' , 'Prepaid Expenses' as 'Description' , ISNULL(((SELECT SUM(CURR_BALANCE) FROM ACCOUNT_BALANCE WHERE ACCT_YEAR = p.ACCT_YEAR AND ACCT_PERIOD = p.ACCT_PERIOD AND ACCOUNT_ID LIKE @PrepaidExpensesPattern)*@PrepaidExpensesMultiplier), 0) as 'Value' FROM ACCOUNT_PERIOD p with(nolock) WHERE p.SITE_ID = @SiteID -- Dividends Paid UNION ALL SELECT p.ACCT_YEAR AS [Year] , p.ACCT_PERIOD AS Period , 6 as 'Order' , 'Dividends Paid' as 'Description' , ISNULL(((SELECT SUM(CURR_BALANCE) FROM ACCOUNT_BALANCE WHERE ACCT_YEAR = p.ACCT_YEAR AND ACCT_PERIOD = p.ACCT_PERIOD AND ACCOUNT_ID LIKE @DividendsPaidPattern)*@DividendsPaidMultiplier), 0) as 'Value' FROM ACCOUNT_PERIOD p with(nolock) WHERE p.SITE_ID = @SiteID -- Overall sorting ORDER BY p.ACCT_YEAR DESC , p.ACCT_PERIOD , [Order]

-- phpMyAdmin SQL Dump -- version 4.8.4 -- https://www.phpmyadmin.net/ -- -- Host: 127.0.0.1 -- Generation Time: Apr 30, 2019 at 08:07 PM -- Server version: 10.1.37-MariaDB -- PHP Version: 7.3.0 SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO"; SET AUTOCOMMIT = 0; START TRANSACTION; SET time_zone = "+00:00"; /*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */; /*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */; /*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */; /*!40101 SET NAMES utf8mb4 */; -- -- Database: `db_sisfo` -- -- -------------------------------------------------------- -- -- Table structure for table `tb_admin` -- CREATE TABLE `tb_admin` ( `id_admin` int(11) NOT NULL, `username` varchar(50) NOT NULL, `password` varchar(100) NOT NULL, `sekolah` varchar(50) DEFAULT NULL, `status` enum('admin','super_admin') NOT NULL, `online_status` tinyint(1) NOT NULL, `last_login` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP ) ENGINE=InnoDB DEFAULT CHARSET=latin1; -- -- Dumping data for table `tb_admin` -- INSERT INTO `tb_admin` (`id_admin`, `username`, `password`, `sekolah`, `status`, `online_status`, `last_login`) VALUES (1, '<PASSWORD>', '<PASSWORD>', '<PASSWORD>', 'admin', 0, '2019-04-23 14:36:08'), (2, '<PASSWORD>2', 'sma2', 'sma 2', 'admin', 0, '2019-04-23 14:36:08'), (3, 'superadmin', 'superadmin', NULL, 'super_admin', 1, '2019-04-30 14:49:17'); -- -------------------------------------------------------- -- -- Table structure for table `tb_dokumen_soal` -- CREATE TABLE `tb_dokumen_soal` ( `id_dokumen` int(20) NOT NULL, `nama_dokumen_soal` varchar(30) NOT NULL, `file_soal` varchar(200) NOT NULL, `tipe_dokumen_soal` enum('soal','jawaban') NOT NULL, `tipe_soal` enum('IPA','IPS','MTK','INDONESIA','INGRRIS') NOT NULL, `tahun_dokumen_soal` year(4) NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=latin1; -- -- Dumping data for table `tb_dokumen_soal` -- INSERT INTO `tb_dokumen_soal` (`id_dokumen`, `nama_dokumen_soal`, `file_soal`, `tipe_dokumen_soal`, `tipe_soal`, `tahun_dokumen_soal`) VALUES (426014646, 'soal IPA tahun 2010', 'Getting-Started-Recap.pdf', 'soal', 'IPA', 2010); -- -------------------------------------------------------- -- -- Table structure for table `tb_jawaban_soal` -- CREATE TABLE `tb_jawaban_soal` ( `id_jawaban_soal` int(11) NOT NULL, `id_soal` int(11) NOT NULL, `abjad_jawaban` char(1) NOT NULL, `isi_jawaban` text NOT NULL, `gambar_jawaban` varchar(20) NOT NULL, `valid_answer` tinyint(1) NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=latin1; -- -------------------------------------------------------- -- -- Table structure for table `tb_jenis_soal` -- CREATE TABLE `tb_jenis_soal` ( `id_jenis_soal` int(11) NOT NULL, `nama_soal` varchar(10) NOT NULL, `tahun_soal` year(4) NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=latin1; -- -------------------------------------------------------- -- -- Table structure for table `tb_nmrpeserta` -- CREATE TABLE `tb_nmrpeserta` ( `id_nmr` int(11) NOT NULL, `nomor_peserta` int(6) NOT NULL, `status` enum('aktif','nonaktif') NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=latin1; -- -- Dumping data for table `tb_nmrpeserta` -- INSERT INTO `tb_nmrpeserta` (`id_nmr`, `nomor_peserta`, `status`) VALUES (28, 284096, 'aktif'), (29, 445846, 'aktif'), (30, 258481, 'aktif'), (31, 205124, 'aktif'), (32, 974121, 'aktif'), (33, 277008, 'nonaktif'), (34, 687046, 'nonaktif'), (35, 547453, 'nonaktif'), (36, 860469, 'nonaktif'), (37, 226767, 'nonaktif'), (38, 169702, 'nonaktif'), (39, 552823, 'nonaktif'), (40, 715545, 'nonaktif'), (41, 902279, 'nonaktif'), (42, 795899, 'nonaktif'), (43, 637002, 'nonaktif'), (44, 597147, 'nonaktif'), (45, 362269, 'nonaktif'), (46, 730342, 'nonaktif'), (47, 806111, 'nonaktif'), (48, 681253, 'nonaktif'), (49, 403489, 'nonaktif'), (50, 958407, 'nonaktif'), (51, 901940, 'nonaktif'), (52, 753002, 'nonaktif'), (53, 212958, 'nonaktif'), (54, 922634, 'nonaktif'), (55, 345954, 'nonaktif'), (56, 603884, 'nonaktif'), (57, 433447, 'nonaktif'), (58, 583443, 'nonaktif'), (59, 811773, 'nonaktif'), (60, 476886, 'nonaktif'), (61, 440557, 'nonaktif'), (62, 576697, 'nonaktif'), (63, 335430, 'nonaktif'), (64, 748594, 'nonaktif'), (65, 268932, 'nonaktif'), (66, 810597, 'nonaktif'), (67, 994568, 'nonaktif'), (68, 935581, 'nonaktif'), (69, 940932, 'nonaktif'), (70, 362770, 'nonaktif'), (71, 965914, 'nonaktif'), (72, 569960, 'nonaktif'), (73, 474140, 'nonaktif'), (74, 772505, 'nonaktif'), (75, 334696, 'nonaktif'), (76, 772753, 'nonaktif'), (77, 775103, 'nonaktif'), (78, 839213, 'nonaktif'), (79, 438573, 'nonaktif'), (80, 596361, 'nonaktif'), (81, 827798, 'nonaktif'), (82, 768164, 'nonaktif'), (83, 554026, 'nonaktif'), (84, 531795, 'nonaktif'), (85, 905853, 'nonaktif'), (86, 546929, 'nonaktif'), (87, 724139, 'nonaktif'), (88, 419696, 'nonaktif'), (89, 951636, 'nonaktif'), (90, 349592, 'nonaktif'), (91, 529909, 'nonaktif'), (92, 531772, 'nonaktif'), (93, 229559, 'nonaktif'), (94, 533289, 'nonaktif'), (95, 871023, 'nonaktif'), (96, 874701, 'nonaktif'), (97, 808495, 'nonaktif'), (98, 679186, 'nonaktif'), (99, 204134, 'nonaktif'), (100, 455335, 'nonaktif'), (101, 661994, 'nonaktif'), (102, 799285, 'nonaktif'), (103, 726746, 'nonaktif'), (104, 138970, 'nonaktif'), (105, 284714, 'nonaktif'), (106, 402861, 'nonaktif'), (107, 361884, 'nonaktif'), (108, 400149, 'nonaktif'), (109, 829525, 'nonaktif'), (110, 669059, 'nonaktif'), (111, 888062, 'nonaktif'), (112, 533918, 'nonaktif'), (113, 117406, 'nonaktif'), (114, 462414, 'nonaktif'), (115, 332942, 'nonaktif'), (116, 398905, 'nonaktif'), (117, 728406, 'nonaktif'), (118, 452544, 'nonaktif'), (119, 425907, 'nonaktif'), (120, 704868, 'nonaktif'), (121, 346088, 'nonaktif'), (122, 875477, 'nonaktif'), (123, 717979, 'nonaktif'), (124, 260145, 'nonaktif'), (125, 947774, 'nonaktif'), (126, 481485, 'nonaktif'), (127, 564843, 'nonaktif'), (128, 695681, 'nonaktif'), (129, 388294, 'nonaktif'), (130, 782635, 'nonaktif'), (131, 528901, 'nonaktif'), (132, 743962, 'nonaktif'), (133, 701461, 'nonaktif'), (134, 269337, 'nonaktif'), (135, 332013, 'nonaktif'), (136, 161044, 'nonaktif'), (137, 470367, 'nonaktif'), (138, 407989, 'nonaktif'), (139, 528195, 'nonaktif'), (140, 764079, 'nonaktif'), (141, 329203, 'nonaktif'), (142, 826440, 'nonaktif'), (143, 374182, 'nonaktif'), (144, 762123, 'nonaktif'), (145, 591067, 'nonaktif'), (146, 555110, 'nonaktif'), (147, 901887, 'nonaktif'), (148, 209858, 'nonaktif'), (149, 859370, 'nonaktif'), (150, 132224, 'nonaktif'), (151, 277010, 'nonaktif'), (152, 899151, 'nonaktif'), (153, 651166, 'nonaktif'), (154, 898966, 'nonaktif'), (155, 218293, 'nonaktif'), (156, 188249, 'nonaktif'), (157, 991348, 'nonaktif'), (158, 714341, 'nonaktif'), (159, 150867, 'nonaktif'), (160, 184662, 'nonaktif'), (161, 776916, 'nonaktif'), (162, 406057, 'nonaktif'), (163, 185948, 'nonaktif'), (164, 355644, 'nonaktif'), (165, 599380, 'nonaktif'), (166, 656676, 'nonaktif'), (167, 299338, 'nonaktif'), (168, 804542, 'nonaktif'), (169, 213973, 'nonaktif'), (170, 893014, 'nonaktif'), (171, 709999, 'nonaktif'), (172, 186102, 'nonaktif'), (173, 730781, 'nonaktif'), (174, 841470, 'nonaktif'), (175, 487239, 'nonaktif'), (176, 687055, 'nonaktif'), (177, 515635, 'nonaktif'), (178, 774951, 'nonaktif'), (179, 749082, 'nonaktif'), (180, 428044, 'nonaktif'), (181, 685422, 'nonaktif'), (182, 635733, 'nonaktif'), (183, 136921, 'nonaktif'), (184, 454863, 'nonaktif'); -- -------------------------------------------------------- -- -- Table structure for table `tb_peserta` -- CREATE TABLE `tb_peserta` ( `id_peserta` int(11) NOT NULL, `id_nmr` int(11) NOT NULL, `nama_peserta` varchar(50) NOT NULL, `email` varchar(50) NOT NULL, `no_hp` varchar(14) NOT NULL, `id_sekolah` int(50) NOT NULL, `id_ruang` int(11) NOT NULL, `id_tahun` int(11) NOT NULL, `pilihan_soal` enum('teknik','non_teknik') NOT NULL, `status_absen` enum('hadir','tidak_hadir') NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=latin1; -- -- Dumping data for table `tb_peserta` -- INSERT INTO `tb_peserta` (`id_peserta`, `id_nmr`, `nama_peserta`, `email`, `no_hp`, `id_sekolah`, `id_ruang`, `id_tahun`, `pilihan_soal`, `status_absen`) VALUES (7, 28, '<NAME>', '<EMAIL>', '081216686750', 10, 1, 2, 'non_teknik', 'tidak_hadir'), (8, 29, '<NAME>', '<EMAIL>', '', 10, 1, 2, 'non_teknik', 'tidak_hadir'), (9, 30, '<NAME>', '<EMAIL>', '082231620938', 10, 1, 2, 'non_teknik', 'tidak_hadir'), (10, 31, 'Hardian', '<EMAIL>', '085736225706', 10, 1, 2, 'non_teknik', 'tidak_hadir'), (11, 32, '<NAME>', '<EMAIL>', '08816076114', 10, 1, 2, 'non_teknik', 'tidak_hadir'); -- -------------------------------------------------------- -- -- Table structure for table `tb_ruang` -- CREATE TABLE `tb_ruang` ( `id_ruang` int(11) NOT NULL, `nama_ruang` varchar(50) NOT NULL, `letak_ruang` varchar(50) NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=latin1; -- -- Dumping data for table `tb_ruang` -- INSERT INTO `tb_ruang` (`id_ruang`, `nama_ruang`, `letak_ruang`) VALUES (1, '', ''), (2, 'Ruang 1', 'XII IPS 1'), (4, 'Ruang 2', 'XII IPS 2'); -- -------------------------------------------------------- -- -- Table structure for table `tb_sekolah` -- CREATE TABLE `tb_sekolah` ( `id_sekolah` int(11) NOT NULL, `nama_sekolah` varchar(40) NOT NULL, `alamat_sekolah` varchar(200) NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=latin1; -- -- Dumping data for table `tb_sekolah` -- INSERT INTO `tb_sekolah` (`id_sekolah`, `nama_sekolah`, `alamat_sekolah`) VALUES (2, 'SMAN 1 KOTA PROBOLINGGO', 'Jl. Soekarno - Hatta No.137, Curahgrinting, Kanigaran, Kota Probolinggo, Jawa Timur 67212'), (3, 'SMAN 2 KOTA PROBOLINGGO', 'Jl. Ki <NAME>, 01, Kanigaran, Kota Probolinggo, Jawa Timur 67213'), (4, 'SMAN 3 KOTA PROBOLINGGO', 'Jrebeng Kidul, Wonoasih, Kota Probolinggo, Jawa Timur 67232'), (5, 'SMAN 4 KOTA PROBOLINGGO', 'Jl. <NAME>, Kanigaran, Kota Probolinggo, Jawa Timur 67271'), (6, 'SMKN 1 KOTA PROBOLINGGO', 'Jl. Mastrip 357 Kademangan Kota Probolinggo, Jrebeng Wetan, Kedopok, Probolinggo City, East Java 67239'), (7, 'SMKN 2 KOTA PROBOLINGGO', 'Jl. Mastrip No.153, Kanigaran, Kota Probolinggo, Jawa Timur 67213\r\n'), (8, 'SMKN 3 KOTA PROBOLINGGO', 'Jl. Pahlawan No.26A, Kebonsari Kulon, Kanigaran, Kota Probolinggo, Jawa Timur 67214'), (9, 'SMKN 4 KOTA PROBOLINGGO', 'Jl. Semeru No.123, Kademangan, Probolinggo, Kota Probolinggo, Jawa Timur 67224'), (10, 'MAN 1 KOTA PROBOLINGGO', 'Jl. Jeruk No.7, Jrebeng Kidul, Wonoasih, Kota Probolinggo, Jawa Timur 67233'), (11, 'MAN 2 KOTA PROBOLINGGO', 'Jl. Raya Soekarno Hatta No.255, Curahgrinting, Kanigaran, Kota Probolinggo, Jawa Timur 67212'), (12, 'SMA TARUNA DRA. ZULAEHA', 'Jalan Raya Leces No. A3, Leces, Kolla, Leces, Probolinggo, Jawa Timur 67273'), (13, 'SMAN 1 DRINGU', 'JL. Kom L Yos Sudarso Pabean, Dringu, 67271, Wonopaten, Pabean, Dringu, Probolinggo, Jawa Timur 67271'), (14, 'SMAN 1 KRAKSAAN', 'Jalan Imam Bonjol No.13, Klojen, Sidomukti, Kraksaan, Probolinggo, Jawa Timur'), (15, 'SMA TUNAS LUHUR', 'Dusun Sefar, Sumberanyar, Paiton, Probolinggo, Jawa Timur 67291'), (16, 'SMAN 1 TONGAS', 'Krajan, Tongaswetan, Tongas, Probolinggo, Jawa Timur 67252'), (17, 'SMAN 1 LECES', 'Jl. Raya Leces, Gn. Malang, Malasan Kulon, Leces, Probolinggo, Jawa Timur 67273'), (18, 'S<NAME>', 'Jl. D.<NAME> No.62B, Sukabumi, Mayangan, Kota Probolinggo, Jawa Timur 67219'), (19, '<NAME>', 'Area Sawah, Karanggeger, Pajarakan, Probolinggo, Jawa Timur 67281'), (20, 'SMAN 1 PAITON', 'Jl. Pakuniran, RT.14/RW.6, Dusun Kota Sukodadi, Sukodadi, Paiton, Probolinggo, Jawa Timur 67291'), (21, 'SMAN 1 GENDING', 'Jl. Raya Sebaung, Kertah, Sebaung, Gending, Probolinggo, Jawa Timur 67272'); -- -------------------------------------------------------- -- -- Table structure for table `tb_soal` -- CREATE TABLE `tb_soal` ( `id_soal` int(11) NOT NULL, `id_jenis_soal` int(11) NOT NULL, `no_soal` int(11) NOT NULL, `text_soal` text NOT NULL, `gambar_soal` varchar(25) NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=latin1; -- -------------------------------------------------------- -- -- Table structure for table `tb_total_registration` -- CREATE TABLE `tb_total_registration` ( `id` int(11) NOT NULL, `tahun` year(4) NOT NULL, `total_terdaftar` int(30) NOT NULL, `total_hadir` int(30) NOT NULL, `total_tidak_hadir` int(30) NOT NULL, `status` tinyint(1) NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=latin1; -- -- Dumping data for table `tb_total_registration` -- INSERT INTO `tb_total_registration` (`id`, `tahun`, `total_terdaftar`, `total_hadir`, `total_tidak_hadir`, `status`) VALUES (1, 2018, 7, 5, 2, 0), (2, 2019, 6, 2, 4, 0); -- -- Indexes for dumped tables -- -- -- Indexes for table `tb_admin` -- ALTER TABLE `tb_admin` ADD PRIMARY KEY (`id_admin`), ADD KEY `id_admin` (`id_admin`); -- -- Indexes for table `tb_dokumen_soal` -- ALTER TABLE `tb_dokumen_soal` ADD PRIMARY KEY (`id_dokumen`); -- -- Indexes for table `tb_jawaban_soal` -- ALTER TABLE `tb_jawaban_soal` ADD PRIMARY KEY (`id_jawaban_soal`), ADD KEY `id_soal` (`id_soal`); -- -- Indexes for table `tb_jenis_soal` -- ALTER TABLE `tb_jenis_soal` ADD PRIMARY KEY (`id_jenis_soal`); -- -- Indexes for table `tb_nmrpeserta` -- ALTER TABLE `tb_nmrpeserta` ADD PRIMARY KEY (`id_nmr`), ADD KEY `id_nmr` (`id_nmr`), ADD KEY `id_nmr_2` (`id_nmr`); -- -- Indexes for table `tb_peserta` -- ALTER TABLE `tb_peserta` ADD PRIMARY KEY (`id_peserta`), ADD KEY `id_peserta` (`id_peserta`), ADD KEY `id_ruang` (`id_ruang`), ADD KEY `id_nmr` (`id_nmr`), ADD KEY `id_tahun` (`id_tahun`), ADD KEY `id_sekolah` (`id_sekolah`); -- -- Indexes for table `tb_ruang` -- ALTER TABLE `tb_ruang` ADD PRIMARY KEY (`id_ruang`), ADD KEY `id_ruang` (`id_ruang`); -- -- Indexes for table `tb_sekolah` -- ALTER TABLE `tb_sekolah` ADD PRIMARY KEY (`id_sekolah`), ADD UNIQUE KEY `nama_sekolah` (`nama_sekolah`); -- -- Indexes for table `tb_soal` -- ALTER TABLE `tb_soal` ADD PRIMARY KEY (`id_soal`), ADD KEY `id_jenis_soal` (`id_jenis_soal`); -- -- Indexes for table `tb_total_registration` -- ALTER TABLE `tb_total_registration` ADD PRIMARY KEY (`id`); -- -- AUTO_INCREMENT for dumped tables -- -- -- AUTO_INCREMENT for table `tb_admin` -- ALTER TABLE `tb_admin` MODIFY `id_admin` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=4; -- -- AUTO_INCREMENT for table `tb_jenis_soal` -- ALTER TABLE `tb_jenis_soal` MODIFY `id_jenis_soal` int(11) NOT NULL AUTO_INCREMENT; -- -- AUTO_INCREMENT for table `tb_nmrpeserta` -- ALTER TABLE `tb_nmrpeserta` MODIFY `id_nmr` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=185; -- -- AUTO_INCREMENT for table `tb_peserta` -- ALTER TABLE `tb_peserta` MODIFY `id_peserta` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=12; -- -- AUTO_INCREMENT for table `tb_ruang` -- ALTER TABLE `tb_ruang` MODIFY `id_ruang` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=5; -- -- AUTO_INCREMENT for table `tb_sekolah` -- ALTER TABLE `tb_sekolah` MODIFY `id_sekolah` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=22; -- -- AUTO_INCREMENT for table `tb_soal` -- ALTER TABLE `tb_soal` MODIFY `id_soal` int(11) NOT NULL AUTO_INCREMENT; -- -- AUTO_INCREMENT for table `tb_total_registration` -- ALTER TABLE `tb_total_registration` MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=3; -- -- Constraints for dumped tables -- -- -- Constraints for table `tb_jawaban_soal` -- ALTER TABLE `tb_jawaban_soal` ADD CONSTRAINT `tb_jawaban_soal_ibfk_1` FOREIGN KEY (`id_soal`) REFERENCES `tb_soal` (`id_soal`) ON DELETE CASCADE; -- -- Constraints for table `tb_peserta` -- ALTER TABLE `tb_peserta` ADD CONSTRAINT `tb_peserta_ibfk_1` FOREIGN KEY (`id_nmr`) REFERENCES `tb_nmrpeserta` (`id_nmr`) ON DELETE CASCADE ON UPDATE CASCADE, ADD CONSTRAINT `tb_peserta_ibfk_2` FOREIGN KEY (`id_ruang`) REFERENCES `tb_ruang` (`id_ruang`), ADD CONSTRAINT `tb_peserta_ibfk_3` FOREIGN KEY (`id_tahun`) REFERENCES `tb_total_registration` (`id`), ADD CONSTRAINT `tb_peserta_ibfk_4` FOREIGN KEY (`id_sekolah`) REFERENCES `tb_sekolah` (`id_sekolah`); -- -- Constraints for table `tb_soal` -- ALTER TABLE `tb_soal` ADD CONSTRAINT `tb_soal_ibfk_1` FOREIGN KEY (`id_jenis_soal`) REFERENCES `tb_jenis_soal` (`id_jenis_soal`) ON DELETE CASCADE; COMMIT; /*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */; /*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */; /*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;

SELECT e.EmployeeID, e.FirstName, e.LastName, d.Name AS DepartmentName FROM Employees AS e INNER JOIN Departments AS d ON d.DepartmentID = e.DepartmentID AND d.Name = 'Sales' ORDER BY e.EmployeeID

<filename>egov/egov-ptis/src/main/resources/db/migration/main/V20170601190140__ptis_alter_egpt_mutation_add_decree_column.sql alter table egpt_property_mutation add column decree_number character varying(64),add column decree_date timestamp without time zone,add column court_name character varying(128);

<reponame>rickyork/Hot-Toddy SELECT `hCalendarBegin` FROM `hCalendarFiles` WHERE `hCalendarId` = {hCalendarId} AND `hCalendarCategoryId` = {hCalendarCategoryId} AND `hCalendarBegin` > {php.time()} ORDER BY `hCalendarBegin` ASC LIMIT 1

SELECT problem, instance, SolverName, round(elapsedSecs,2) as elapsedSecs, Objective, Optimally , Solved, Searchtype, mif FROM JobResult jr INNER JOIN Config cf ON jr.ConfigId = cf.ID INNER JOIN Solver sv ON jr.SolverId = sv.ID -- group by instance, SPD, Objective where timeout > 10000 and solved = 0 order by problem, instance, elapsedSecs, solverId

<gh_stars>1-10 CREATE TABLE [ZGWOptional].[Directories] ( [Function_SeqID] INT NOT NULL, [Directory] VARCHAR (255) NOT NULL, [Impersonate] INT NOT NULL, [Impersonating_Account] VARCHAR (50) NULL, [Impersonating_Password] VARCHAR (50) NULL, [Added_By] INT NOT NULL, [Added_Date] DATETIME DEFAULT (getdate()) NOT NULL, [Updated_By] INT NULL, [Updated_Date] DATETIME NULL, CONSTRAINT [PK_Directories] PRIMARY KEY CLUSTERED ([Function_SeqID] ASC), CONSTRAINT [FK_Directories_Functions] FOREIGN KEY ([Function_SeqID]) REFERENCES [ZGWSecurity].[Functions] ([Function_SeqID]) ON DELETE CASCADE ON UPDATE CASCADE );

-- file:create_table_like.sql ln:4 expect:true /* * Test double inheritance * * Ensure that defaults are NOT included unless * INCLUDING DEFAULTS is specified */ CREATE TABLE ctla (aa TEXT)

UPDATE gitem_list SET title = ?, channel_title = ?, published = ?, last_checked = ?, thumb_url = ? WHERE gitem_id = ?;

<reponame>FScoward/fan-share-fun -- MySQL Script generated by MySQL Workbench -- 02/14/16 21:58:09 -- Model: New Model Version: 1.0 -- MySQL Workbench Forward Engineering SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0; SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0; SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='TRADITIONAL,ALLOW_INVALID_DATES'; -- ----------------------------------------------------- -- Schema tickets -- ----------------------------------------------------- DROP SCHEMA IF EXISTS `tickets` ; -- ----------------------------------------------------- -- Schema tickets -- ----------------------------------------------------- CREATE SCHEMA IF NOT EXISTS `tickets` DEFAULT CHARACTER SET utf8mb4 ; USE `tickets` ; -- ----------------------------------------------------- -- Table `tickets`.`User` -- ----------------------------------------------------- DROP TABLE IF EXISTS `tickets`.`User` ; CREATE TABLE IF NOT EXISTS `tickets`.`User` ( `user_id` BIGINT(30) NOT NULL AUTO_INCREMENT COMMENT '', `username` VARCHAR(45) NOT NULL COMMENT '', `image_url` TEXT NOT NULL COMMENT '', PRIMARY KEY (`user_id`) COMMENT '') ENGINE = InnoDB; -- ----------------------------------------------------- -- Table `tickets`.`Event` -- ----------------------------------------------------- DROP TABLE IF EXISTS `tickets`.`Event` ; CREATE TABLE IF NOT EXISTS `tickets`.`Event` ( `event_id` BIGINT(30) NOT NULL AUTO_INCREMENT COMMENT '', `event_name` VARCHAR(45) NOT NULL COMMENT '', PRIMARY KEY (`event_id`) COMMENT '') ENGINE = InnoDB; -- ----------------------------------------------------- -- Table `tickets`.`EventDescription` -- ----------------------------------------------------- DROP TABLE IF EXISTS `tickets`.`EventDescription` ; CREATE TABLE IF NOT EXISTS `tickets`.`EventDescription` ( `Event_event_id` BIGINT(30) NOT NULL COMMENT '', `artist` VARCHAR(45) NULL COMMENT '', `location` VARCHAR(45) NULL COMMENT '', `date` VARCHAR(45) NULL COMMENT '', `description` TEXT NULL COMMENT '', PRIMARY KEY (`Event_event_id`) COMMENT '', INDEX `fk_EventDescription_Event_idx` (`Event_event_id` ASC) COMMENT '', CONSTRAINT `fk_EventDescription_Event` FOREIGN KEY (`Event_event_id`) REFERENCES `tickets`.`Event` (`event_id`) ON DELETE NO ACTION ON UPDATE NO ACTION) ENGINE = InnoDB; -- ----------------------------------------------------- -- Table `tickets`.`Group` -- ----------------------------------------------------- DROP TABLE IF EXISTS `tickets`.`Group` ; CREATE TABLE IF NOT EXISTS `tickets`.`Group` ( `group_id` BIGINT(30) NOT NULL AUTO_INCREMENT COMMENT '', `group_name` VARCHAR(45) NULL COMMENT '', PRIMARY KEY (`group_id`) COMMENT '') ENGINE = InnoDB; -- ----------------------------------------------------- -- Table `tickets`.`Group_has_User` -- ----------------------------------------------------- DROP TABLE IF EXISTS `tickets`.`Group_has_User` ; CREATE TABLE IF NOT EXISTS `tickets`.`Group_has_User` ( `Group_group_id` BIGINT(30) NOT NULL COMMENT '', `User_user_id` BIGINT(30) NOT NULL COMMENT '', `is_owner` TINYINT(1) NOT NULL COMMENT '', PRIMARY KEY (`Group_group_id`, `User_user_id`) COMMENT '', INDEX `fk_Group_has_User_User1_idx` (`User_user_id` ASC) COMMENT '', INDEX `fk_Group_has_User_Group1_idx` (`Group_group_id` ASC) COMMENT '', CONSTRAINT `fk_Group_has_User_Group1` FOREIGN KEY (`Group_group_id`) REFERENCES `tickets`.`Group` (`group_id`) ON DELETE NO ACTION ON UPDATE NO ACTION, CONSTRAINT `fk_Group_has_User_User1` FOREIGN KEY (`User_user_id`) REFERENCES `tickets`.`User` (`user_id`) ON DELETE NO ACTION ON UPDATE NO ACTION) ENGINE = InnoDB; -- ----------------------------------------------------- -- Table `tickets`.`Event_has_Group` -- ----------------------------------------------------- DROP TABLE IF EXISTS `tickets`.`Event_has_Group` ; CREATE TABLE IF NOT EXISTS `tickets`.`Event_has_Group` ( `Event_event_id` BIGINT(30) NOT NULL COMMENT '', `Group_group_id` BIGINT(30) NOT NULL COMMENT '', PRIMARY KEY (`Event_event_id`, `Group_group_id`) COMMENT '', INDEX `fk_Event_has_Group_Group1_idx` (`Group_group_id` ASC) COMMENT '', INDEX `fk_Event_has_Group_Event1_idx` (`Event_event_id` ASC) COMMENT '', CONSTRAINT `fk_Event_has_Group_Event1` FOREIGN KEY (`Event_event_id`) REFERENCES `tickets`.`Event` (`event_id`) ON DELETE NO ACTION ON UPDATE NO ACTION, CONSTRAINT `fk_Event_has_Group_Group1` FOREIGN KEY (`Group_group_id`) REFERENCES `tickets`.`Group` (`group_id`) ON DELETE NO ACTION ON UPDATE NO ACTION) ENGINE = InnoDB; SET SQL_MODE=@OLD_SQL_MODE; SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS; SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS;

-- phpMyAdmin SQL Dump -- version 5.0.2 -- https://www.phpmyadmin.net/ -- -- Host: 127.0.0.1 -- Generation Time: Oct 06, 2020 at 08:44 AM -- Server version: 10.4.14-MariaDB -- PHP Version: 7.4.9 SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO"; START TRANSACTION; SET time_zone = "+00:00"; /*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */; /*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */; /*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */; /*!40101 SET NAMES utf8mb4 */; -- -- Database: `login` -- -- -------------------------------------------------------- -- -- Table structure for table `users` -- CREATE TABLE `users` ( `id` int(11) NOT NULL, `username` varchar(50) NOT NULL, `password` varchar(32) NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4; -- -- Dumping data for table `users` -- INSERT INTO `users` (`id`, `username`, `password`) VALUES (1, 'testuser1', '<PASSWORD>'), (2, 'testuser1', '<PASSWORD>'), (3, '<EMAIL>', '<PASSWORD>'), (4, '<EMAIL>', '<PASSWORD>'), (5, '<EMAIL>', '<PASSWORD>'), (6, '<EMAIL>', '<PASSWORD>'); -- -- Indexes for dumped tables -- -- -- Indexes for table `users` -- ALTER TABLE `users` ADD PRIMARY KEY (`id`); -- -- AUTO_INCREMENT for dumped tables -- -- -- AUTO_INCREMENT for table `users` -- ALTER TABLE `users` MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=7; COMMIT; /*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */; /*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */; /*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;

<filename>tables/notificationType.sql<gh_stars>0 SET FOREIGN_KEY_CHECKS=0; DROP TABLE IF EXISTS `notificationType`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `notificationType` ( `id` int(11) NOT NULL AUTO_INCREMENT, `isActive` tinyint(1) NOT NULL DEFAULT '1', `lastUpdated` datetime DEFAULT NULL, `name` varchar(45) DEFAULT '', PRIMARY KEY (`id`) ) ENGINE=InnoDB AUTO_INCREMENT=1 DEFAULT CHARSET=utf8; /*!40101 SET character_set_client = @saved_cs_client */; SET FOREIGN_KEY_CHECKS=1;

-- Your SQL goes here INSERT INTO songs ( title, past_difficulty, present_difficulty, future_difficulty ) VALUES ("Diode", 2, 5, 8), ("FREEF4LL", 4, 7, 8), ("GLORY:ROAD", 4, 7, 10), ("Monochrome Princess", 4, 7, 9), ("Heavenly careless", 3, 7, 9);

CREATE TABLE CPF_USER_GROUPS ( USER_GROUP_ID NUMBER(19) NOT NULL, MODULE_NAME VARCHAR2(255) NOT NULL, USER_GROUP_NAME VARCHAR2(255) NOT NULL, DESCRIPTION VARCHAR2(4000), ACTIVE_IND NUMBER(1,0) NOT NULL, WHO_CREATED VARCHAR2(255) NOT NULL, WHEN_CREATED TIMESTAMP NOT NULL, WHO_UPDATED VARCHAR2(255) NOT NULL, WHEN_UPDATED TIMESTAMP NOT NULL, CONSTRAINT USER_GROUPS_PK PRIMARY KEY (USER_GROUP_ID), CONSTRAINT USER_GROUPS_USER_GROUP_NAME_UK UNIQUE (USER_GROUP_NAME) ); -- Sequence CREATE SEQUENCE CPF_UG_SEQ; -- Grants GRANT DELETE, INSERT, SELECT, UPDATE ON CPF_USER_GROUPS TO CPF_USER; GRANT SELECT ON CPF_UG_SEQ TO CPF_USER; -- Comments COMMENT ON TABLE CPF_USER_GROUPS IS 'USER GROUP represents a named group of CPF or external users that can be granted permissions via USER GROUP PERMISSION. The members of the group are defined in the USER GROUP ACCOUNT XFREF.'; COMMENT ON COLUMN CPF_USER_GROUPS.USER_GROUP_ID IS 'USER GROUP ID is a unique surrogate identifier for the object USER GROUP.'; COMMENT ON COLUMN CPF_USER_GROUPS.MODULE_NAME IS 'MODULE NAME contains the name of the CPF application module the USER GROUP was created for.'; COMMENT ON COLUMN CPF_USER_GROUPS.USER_GROUP_NAME IS 'This is the name of the SECURITY GROUP.'; COMMENT ON COLUMN CPF_USER_GROUPS.DESCRIPTION IS 'This is a description of the security group.'; COMMENT ON COLUMN CPF_USER_GROUPS.ACTIVE_IND IS 'This is the true (1), false (0) indicator if the object is active or has been deleted.'; COMMENT ON COLUMN CPF_USER_GROUPS.WHO_CREATED IS 'This is the database or web user that created the object.'; COMMENT ON COLUMN CPF_USER_GROUPS.WHEN_CREATED IS 'This is the date that the object was created.'; COMMENT ON COLUMN CPF_USER_GROUPS.WHO_UPDATED IS 'This is the database or web user that last updated the object.'; COMMENT ON COLUMN CPF_USER_GROUPS.WHEN_UPDATED IS 'This is the date that the object was last updated.';

CREATE TABLE m_acc_cert_campaign ( definitionRef_relation VARCHAR2(157 CHAR), definitionRef_targetOid VARCHAR2(36 CHAR), definitionRef_type NUMBER(10, 0), endTimestamp TIMESTAMP, handlerUri VARCHAR2(255 CHAR), iteration NUMBER(10, 0) NOT NULL, name_norm VARCHAR2(255 CHAR), name_orig VARCHAR2(255 CHAR), ownerRef_relation VARCHAR2(157 CHAR), ownerRef_targetOid VARCHAR2(36 CHAR), ownerRef_type NUMBER(10, 0), stageNumber NUMBER(10, 0), startTimestamp TIMESTAMP, state NUMBER(10, 0), oid VARCHAR2(36 CHAR) NOT NULL, PRIMARY KEY (oid) ) INITRANS 30; CREATE TABLE m_acc_cert_case ( id NUMBER(10, 0) NOT NULL, owner_oid VARCHAR2(36 CHAR) NOT NULL, administrativeStatus NUMBER(10, 0), archiveTimestamp TIMESTAMP, disableReason VARCHAR2(255 CHAR), disableTimestamp TIMESTAMP, effectiveStatus NUMBER(10, 0), enableTimestamp TIMESTAMP, validFrom TIMESTAMP, validTo TIMESTAMP, validityChangeTimestamp TIMESTAMP, validityStatus NUMBER(10, 0), currentStageOutcome VARCHAR2(255 CHAR), fullObject BLOB, iteration NUMBER(10, 0) NOT NULL, objectRef_relation VARCHAR2(157 CHAR), objectRef_targetOid VARCHAR2(36 CHAR), objectRef_type NUMBER(10, 0), orgRef_relation VARCHAR2(157 CHAR), orgRef_targetOid VARCHAR2(36 CHAR), orgRef_type NUMBER(10, 0), outcome VARCHAR2(255 CHAR), remediedTimestamp TIMESTAMP, reviewDeadline TIMESTAMP, reviewRequestedTimestamp TIMESTAMP, stageNumber NUMBER(10, 0), targetRef_relation VARCHAR2(157 CHAR), targetRef_targetOid VARCHAR2(36 CHAR), targetRef_type NUMBER(10, 0), tenantRef_relation VARCHAR2(157 CHAR), tenantRef_targetOid VARCHAR2(36 CHAR), tenantRef_type NUMBER(10, 0), PRIMARY KEY (owner_oid, id) ) INITRANS 30; CREATE TABLE m_acc_cert_definition ( handlerUri VARCHAR2(255 CHAR), lastCampaignClosedTimestamp TIMESTAMP, lastCampaignStartedTimestamp TIMESTAMP, name_norm VARCHAR2(255 CHAR), name_orig VARCHAR2(255 CHAR), ownerRef_relation VARCHAR2(157 CHAR), ownerRef_targetOid VARCHAR2(36 CHAR), ownerRef_type NUMBER(10, 0), oid VARCHAR2(36 CHAR) NOT NULL, PRIMARY KEY (oid) ) INITRANS 30; CREATE TABLE m_acc_cert_wi ( id NUMBER(10, 0) NOT NULL, owner_id NUMBER(10, 0) NOT NULL, owner_owner_oid VARCHAR2(36 CHAR) NOT NULL, closeTimestamp TIMESTAMP, iteration NUMBER(10, 0) NOT NULL, outcome VARCHAR2(255 CHAR), outputChangeTimestamp TIMESTAMP, performerRef_relation VARCHAR2(157 CHAR), performerRef_targetOid VARCHAR2(36 CHAR), performerRef_type NUMBER(10, 0), stageNumber NUMBER(10, 0), PRIMARY KEY (owner_owner_oid, owner_id, id) ) INITRANS 30; CREATE TABLE m_acc_cert_wi_reference ( owner_id NUMBER(10, 0) NOT NULL, owner_owner_id NUMBER(10, 0) NOT NULL, owner_owner_owner_oid VARCHAR2(36 CHAR) NOT NULL, relation VARCHAR2(157 CHAR) NOT NULL, targetOid VARCHAR2(36 CHAR) NOT NULL, targetType NUMBER(10, 0), PRIMARY KEY (owner_owner_owner_oid, owner_owner_id, owner_id, relation, targetOid) ) INITRANS 30; CREATE TABLE m_assignment ( id NUMBER(10, 0) NOT NULL, owner_oid VARCHAR2(36 CHAR) NOT NULL, administrativeStatus NUMBER(10, 0), archiveTimestamp TIMESTAMP, disableReason VARCHAR2(255 CHAR), disableTimestamp TIMESTAMP, effectiveStatus NUMBER(10, 0), enableTimestamp TIMESTAMP, validFrom TIMESTAMP, validTo TIMESTAMP, validityChangeTimestamp TIMESTAMP, validityStatus NUMBER(10, 0), assignmentOwner NUMBER(10, 0), createChannel VARCHAR2(255 CHAR), createTimestamp TIMESTAMP, creatorRef_relation VARCHAR2(157 CHAR), creatorRef_targetOid VARCHAR2(36 CHAR), creatorRef_type NUMBER(10, 0), lifecycleState VARCHAR2(255 CHAR), modifierRef_relation VARCHAR2(157 CHAR), modifierRef_targetOid VARCHAR2(36 CHAR), modifierRef_type NUMBER(10, 0), modifyChannel VARCHAR2(255 CHAR), modifyTimestamp TIMESTAMP, orderValue NUMBER(10, 0), orgRef_relation VARCHAR2(157 CHAR), orgRef_targetOid VARCHAR2(36 CHAR), orgRef_type NUMBER(10, 0), resourceRef_relation VARCHAR2(157 CHAR), resourceRef_targetOid VARCHAR2(36 CHAR), resourceRef_type NUMBER(10, 0), targetRef_relation VARCHAR2(157 CHAR), targetRef_targetOid VARCHAR2(36 CHAR), targetRef_type NUMBER(10, 0), tenantRef_relation VARCHAR2(157 CHAR), tenantRef_targetOid VARCHAR2(36 CHAR), tenantRef_type NUMBER(10, 0), extId NUMBER(10, 0), extOid VARCHAR2(36 CHAR), PRIMARY KEY (owner_oid, id) ) INITRANS 30; CREATE TABLE m_assignment_ext_boolean ( item_id NUMBER(10, 0) NOT NULL, anyContainer_owner_id NUMBER(10, 0) NOT NULL, anyContainer_owner_owner_oid VARCHAR2(36 CHAR) NOT NULL, booleanValue NUMBER(1, 0) NOT NULL, PRIMARY KEY (anyContainer_owner_owner_oid, anyContainer_owner_id, item_id, booleanValue) ) INITRANS 30; CREATE TABLE m_assignment_ext_date ( item_id NUMBER(10, 0) NOT NULL, anyContainer_owner_id NUMBER(10, 0) NOT NULL, anyContainer_owner_owner_oid VARCHAR2(36 CHAR) NOT NULL, dateValue TIMESTAMP NOT NULL, PRIMARY KEY (anyContainer_owner_owner_oid, anyContainer_owner_id, item_id, dateValue) ) INITRANS 30; CREATE TABLE m_assignment_ext_long ( item_id NUMBER(10, 0) NOT NULL, anyContainer_owner_id NUMBER(10, 0) NOT NULL, anyContainer_owner_owner_oid VARCHAR2(36 CHAR) NOT NULL, longValue NUMBER(19, 0) NOT NULL, PRIMARY KEY (anyContainer_owner_owner_oid, anyContainer_owner_id, item_id, longValue) ) INITRANS 30; CREATE TABLE m_assignment_ext_poly ( item_id NUMBER(10, 0) NOT NULL, anyContainer_owner_id NUMBER(10, 0) NOT NULL, anyContainer_owner_owner_oid VARCHAR2(36 CHAR) NOT NULL, orig VARCHAR2(255 CHAR) NOT NULL, norm VARCHAR2(255 CHAR), PRIMARY KEY (anyContainer_owner_owner_oid, anyContainer_owner_id, item_id, orig) ) INITRANS 30; CREATE TABLE m_assignment_ext_reference ( item_id NUMBER(10, 0) NOT NULL, anyContainer_owner_id NUMBER(10, 0) NOT NULL, anyContainer_owner_owner_oid VARCHAR2(36 CHAR) NOT NULL, targetoid VARCHAR2(36 CHAR) NOT NULL, relation VARCHAR2(157 CHAR), targetType NUMBER(10, 0), PRIMARY KEY (anyContainer_owner_owner_oid, anyContainer_owner_id, item_id, targetoid) ) INITRANS 30; CREATE TABLE m_assignment_ext_string ( item_id NUMBER(10, 0) NOT NULL, anyContainer_owner_id NUMBER(10, 0) NOT NULL, anyContainer_owner_owner_oid VARCHAR2(36 CHAR) NOT NULL, stringValue VARCHAR2(255 CHAR) NOT NULL, PRIMARY KEY (anyContainer_owner_owner_oid, anyContainer_owner_id, item_id, stringValue) ) INITRANS 30; CREATE TABLE m_assignment_extension ( owner_id NUMBER(10, 0) NOT NULL, owner_owner_oid VARCHAR2(36 CHAR) NOT NULL, booleansCount NUMBER(5, 0), datesCount NUMBER(5, 0), longsCount NUMBER(5, 0), polysCount NUMBER(5, 0), referencesCount NUMBER(5, 0), stringsCount NUMBER(5, 0), PRIMARY KEY (owner_owner_oid, owner_id) ) INITRANS 30; CREATE TABLE m_assignment_policy_situation ( assignment_id NUMBER(10, 0) NOT NULL, assignment_oid VARCHAR2(36 CHAR) NOT NULL, policySituation VARCHAR2(255 CHAR) ) INITRANS 30; CREATE TABLE m_assignment_reference ( owner_id NUMBER(10, 0) NOT NULL, owner_owner_oid VARCHAR2(36 CHAR) NOT NULL, reference_type NUMBER(10, 0) NOT NULL, relation VARCHAR2(157 CHAR) NOT NULL, targetOid VARCHAR2(36 CHAR) NOT NULL, targetType NUMBER(10, 0), PRIMARY KEY (owner_owner_oid, owner_id, reference_type, relation, targetOid) ) INITRANS 30; CREATE TABLE m_audit_delta ( checksum VARCHAR2(32 CHAR) NOT NULL, record_id NUMBER(19, 0) NOT NULL, delta BLOB, deltaOid VARCHAR2(36 CHAR), deltaType NUMBER(10, 0), fullResult BLOB, objectName_norm VARCHAR2(255 CHAR), objectName_orig VARCHAR2(255 CHAR), resourceName_norm VARCHAR2(255 CHAR), resourceName_orig VARCHAR2(255 CHAR), resourceOid VARCHAR2(36 CHAR), status NUMBER(10, 0), PRIMARY KEY (record_id, checksum) ) INITRANS 30; CREATE TABLE m_audit_event ( id NUMBER(19, 0) GENERATED AS IDENTITY, attorneyName VARCHAR2(255 CHAR), attorneyOid VARCHAR2(36 CHAR), channel VARCHAR2(255 CHAR), eventIdentifier VARCHAR2(255 CHAR), eventStage NUMBER(10, 0), eventType NUMBER(10, 0), hostIdentifier VARCHAR2(255 CHAR), initiatorName VARCHAR2(255 CHAR), initiatorOid VARCHAR2(36 CHAR), initiatorType NUMBER(10, 0), message VARCHAR2(1024 CHAR), nodeIdentifier VARCHAR2(255 CHAR), outcome NUMBER(10, 0), parameter VARCHAR2(255 CHAR), remoteHostAddress VARCHAR2(255 CHAR), result VARCHAR2(255 CHAR), sessionIdentifier VARCHAR2(255 CHAR), targetName VARCHAR2(255 CHAR), targetOid VARCHAR2(36 CHAR), targetOwnerName VARCHAR2(255 CHAR), targetOwnerOid VARCHAR2(36 CHAR), targetOwnerType NUMBER(10, 0), targetType NUMBER(10, 0), taskIdentifier VARCHAR2(255 CHAR), taskOID VARCHAR2(255 CHAR), timestampValue TIMESTAMP, PRIMARY KEY (id) ) INITRANS 30; CREATE TABLE m_audit_item ( changedItemPath VARCHAR2(255 CHAR) NOT NULL, record_id NUMBER(19, 0) NOT NULL, PRIMARY KEY (record_id, changedItemPath) ) INITRANS 30; CREATE TABLE m_audit_prop_value ( id NUMBER(19, 0) GENERATED AS IDENTITY, name VARCHAR2(255 CHAR), record_id NUMBER(19, 0), value VARCHAR2(1024 CHAR), PRIMARY KEY (id) ) INITRANS 30; CREATE TABLE m_audit_ref_value ( id NUMBER(19, 0) GENERATED AS IDENTITY, name VARCHAR2(255 CHAR), oid VARCHAR2(36 CHAR), record_id NUMBER(19, 0), targetName_norm VARCHAR2(255 CHAR), targetName_orig VARCHAR2(255 CHAR), type VARCHAR2(255 CHAR), PRIMARY KEY (id) ) INITRANS 30; CREATE TABLE m_case_wi ( id NUMBER(10, 0) NOT NULL, owner_oid VARCHAR2(36 CHAR) NOT NULL, closeTimestamp TIMESTAMP, deadline TIMESTAMP, originalAssigneeRef_relation VARCHAR2(157 CHAR), originalAssigneeRef_targetOid VARCHAR2(36 CHAR), originalAssigneeRef_type NUMBER(10, 0), outcome VARCHAR2(255 CHAR), performerRef_relation VARCHAR2(157 CHAR), performerRef_targetOid VARCHAR2(36 CHAR), performerRef_type NUMBER(10, 0), stageNumber NUMBER(10, 0), PRIMARY KEY (owner_oid, id) ) INITRANS 30; CREATE TABLE m_case_wi_reference ( owner_id NUMBER(10, 0) NOT NULL, owner_owner_oid VARCHAR2(36 CHAR) NOT NULL, relation VARCHAR2(157 CHAR) NOT NULL, targetOid VARCHAR2(36 CHAR) NOT NULL, targetType NUMBER(10, 0), PRIMARY KEY (owner_owner_oid, owner_id, targetOid, relation) ) INITRANS 30; CREATE TABLE m_connector_target_system ( connector_oid VARCHAR2(36 CHAR) NOT NULL, targetSystemType VARCHAR2(255 CHAR) ) INITRANS 30; CREATE TABLE m_ext_item ( id NUMBER(10, 0) GENERATED AS IDENTITY, kind NUMBER(10, 0), itemName VARCHAR2(157 CHAR), itemType VARCHAR2(157 CHAR), PRIMARY KEY (id) ) INITRANS 30; CREATE TABLE m_focus_photo ( owner_oid VARCHAR2(36 CHAR) NOT NULL, photo BLOB, PRIMARY KEY (owner_oid) ) INITRANS 30; CREATE TABLE m_focus_policy_situation ( focus_oid VARCHAR2(36 CHAR) NOT NULL, policySituation VARCHAR2(255 CHAR) ) INITRANS 30; CREATE TABLE m_object ( oid VARCHAR2(36 CHAR) NOT NULL, booleansCount NUMBER(5, 0), createChannel VARCHAR2(255 CHAR), createTimestamp TIMESTAMP, creatorRef_relation VARCHAR2(157 CHAR), creatorRef_targetOid VARCHAR2(36 CHAR), creatorRef_type NUMBER(10, 0), datesCount NUMBER(5, 0), fullObject BLOB, lifecycleState VARCHAR2(255 CHAR), longsCount NUMBER(5, 0), modifierRef_relation VARCHAR2(157 CHAR), modifierRef_targetOid VARCHAR2(36 CHAR), modifierRef_type NUMBER(10, 0), modifyChannel VARCHAR2(255 CHAR), modifyTimestamp TIMESTAMP, name_norm VARCHAR2(255 CHAR), name_orig VARCHAR2(255 CHAR), objectTypeClass NUMBER(10, 0), polysCount NUMBER(5, 0), referencesCount NUMBER(5, 0), stringsCount NUMBER(5, 0), tenantRef_relation VARCHAR2(157 CHAR), tenantRef_targetOid VARCHAR2(36 CHAR), tenantRef_type NUMBER(10, 0), version NUMBER(10, 0) NOT NULL, PRIMARY KEY (oid) ) INITRANS 30; CREATE TABLE m_object_ext_boolean ( item_id NUMBER(10, 0) NOT NULL, owner_oid VARCHAR2(36 CHAR) NOT NULL, ownerType NUMBER(10, 0) NOT NULL, booleanValue NUMBER(1, 0) NOT NULL, PRIMARY KEY (owner_oid, ownerType, item_id, booleanValue) ) INITRANS 30; CREATE TABLE m_object_ext_date ( item_id NUMBER(10, 0) NOT NULL, owner_oid VARCHAR2(36 CHAR) NOT NULL, ownerType NUMBER(10, 0) NOT NULL, dateValue TIMESTAMP NOT NULL, PRIMARY KEY (owner_oid, ownerType, item_id, dateValue) ) INITRANS 30; CREATE TABLE m_object_ext_long ( item_id NUMBER(10, 0) NOT NULL, owner_oid VARCHAR2(36 CHAR) NOT NULL, ownerType NUMBER(10, 0) NOT NULL, longValue NUMBER(19, 0) NOT NULL, PRIMARY KEY (owner_oid, ownerType, item_id, longValue) ) INITRANS 30; CREATE TABLE m_object_ext_poly ( item_id NUMBER(10, 0) NOT NULL, owner_oid VARCHAR2(36 CHAR) NOT NULL, ownerType NUMBER(10, 0) NOT NULL, orig VARCHAR2(255 CHAR) NOT NULL, norm VARCHAR2(255 CHAR), PRIMARY KEY (owner_oid, ownerType, item_id, orig) ) INITRANS 30; CREATE TABLE m_object_ext_reference ( item_id NUMBER(10, 0) NOT NULL, owner_oid VARCHAR2(36 CHAR) NOT NULL, ownerType NUMBER(10, 0) NOT NULL, targetoid VARCHAR2(36 CHAR) NOT NULL, relation VARCHAR2(157 CHAR), targetType NUMBER(10, 0), PRIMARY KEY (owner_oid, ownerType, item_id, targetoid) ) INITRANS 30; CREATE TABLE m_object_ext_string ( item_id NUMBER(10, 0) NOT NULL, owner_oid VARCHAR2(36 CHAR) NOT NULL, ownerType NUMBER(10, 0) NOT NULL, stringValue VARCHAR2(255 CHAR) NOT NULL, PRIMARY KEY (owner_oid, ownerType, item_id, stringValue) ) INITRANS 30; CREATE TABLE m_object_subtype ( object_oid VARCHAR2(36 CHAR) NOT NULL, subtype VARCHAR2(255 CHAR) ) INITRANS 30; CREATE TABLE m_object_text_info ( owner_oid VARCHAR2(36 CHAR) NOT NULL, text VARCHAR2(255 CHAR) NOT NULL, PRIMARY KEY (owner_oid, text) ) INITRANS 30; CREATE TABLE m_operation_execution ( id NUMBER(10, 0) NOT NULL, owner_oid VARCHAR2(36 CHAR) NOT NULL, initiatorRef_relation VARCHAR2(157 CHAR), initiatorRef_targetOid VARCHAR2(36 CHAR), initiatorRef_type NUMBER(10, 0), status NUMBER(10, 0), taskRef_relation VARCHAR2(157 CHAR), taskRef_targetOid VARCHAR2(36 CHAR), taskRef_type NUMBER(10, 0), timestampValue TIMESTAMP, PRIMARY KEY (owner_oid, id) ) INITRANS 30; CREATE TABLE m_org_closure ( ancestor_oid VARCHAR2(36 CHAR) NOT NULL, descendant_oid VARCHAR2(36 CHAR) NOT NULL, val NUMBER(10, 0), PRIMARY KEY (ancestor_oid, descendant_oid) ) INITRANS 30; CREATE TABLE m_org_org_type ( org_oid VARCHAR2(36 CHAR) NOT NULL, orgType VARCHAR2(255 CHAR) ) INITRANS 30; CREATE TABLE m_reference ( owner_oid VARCHAR2(36 CHAR) NOT NULL, reference_type NUMBER(10, 0) NOT NULL, relation VARCHAR2(157 CHAR) NOT NULL, targetOid VARCHAR2(36 CHAR) NOT NULL, targetType NUMBER(10, 0), PRIMARY KEY (owner_oid, reference_type, relation, targetOid) ) INITRANS 30; CREATE TABLE m_service_type ( service_oid VARCHAR2(36 CHAR) NOT NULL, serviceType VARCHAR2(255 CHAR) ) INITRANS 30; CREATE TABLE m_shadow ( attemptNumber NUMBER(10, 0), dead NUMBER(1, 0), exist NUMBER(1, 0), failedOperationType NUMBER(10, 0), fullSynchronizationTimestamp TIMESTAMP, intent VARCHAR2(255 CHAR), kind NUMBER(10, 0), name_norm VARCHAR2(255 CHAR), name_orig VARCHAR2(255 CHAR), objectClass VARCHAR2(157 CHAR), pendingOperationCount NUMBER(10, 0), resourceRef_relation VARCHAR2(157 CHAR), resourceRef_targetOid VARCHAR2(36 CHAR), resourceRef_type NUMBER(10, 0), status NUMBER(10, 0), synchronizationSituation NUMBER(10, 0), synchronizationTimestamp TIMESTAMP, oid VARCHAR2(36 CHAR) NOT NULL, PRIMARY KEY (oid) ) INITRANS 30; CREATE TABLE m_task ( binding NUMBER(10, 0), canRunOnNode VARCHAR2(255 CHAR), category VARCHAR2(255 CHAR), completionTimestamp TIMESTAMP, executionStatus NUMBER(10, 0), fullResult BLOB, handlerUri VARCHAR2(255 CHAR), lastRunFinishTimestamp TIMESTAMP, lastRunStartTimestamp TIMESTAMP, name_norm VARCHAR2(255 CHAR), name_orig VARCHAR2(255 CHAR), node VARCHAR2(255 CHAR), objectRef_relation VARCHAR2(157 CHAR), objectRef_targetOid VARCHAR2(36 CHAR), objectRef_type NUMBER(10, 0), ownerRef_relation VARCHAR2(157 CHAR), ownerRef_targetOid VARCHAR2(36 CHAR), ownerRef_type NUMBER(10, 0), parent VARCHAR2(255 CHAR), recurrence NUMBER(10, 0), status NUMBER(10, 0), taskIdentifier VARCHAR2(255 CHAR), threadStopAction NUMBER(10, 0), waitingReason NUMBER(10, 0), wfEndTimestamp TIMESTAMP, wfObjectRef_relation VARCHAR2(157 CHAR), wfObjectRef_targetOid VARCHAR2(36 CHAR), wfObjectRef_type NUMBER(10, 0), wfProcessInstanceId VARCHAR2(255 CHAR), wfRequesterRef_relation VARCHAR2(157 CHAR), wfRequesterRef_targetOid VARCHAR2(36 CHAR), wfRequesterRef_type NUMBER(10, 0), wfStartTimestamp TIMESTAMP, wfTargetRef_relation VARCHAR2(157 CHAR), wfTargetRef_targetOid VARCHAR2(36 CHAR), wfTargetRef_type NUMBER(10, 0), oid VARCHAR2(36 CHAR) NOT NULL, PRIMARY KEY (oid) ) INITRANS 30; CREATE TABLE m_task_dependent ( task_oid VARCHAR2(36 CHAR) NOT NULL, dependent VARCHAR2(255 CHAR) ) INITRANS 30; CREATE TABLE m_user_employee_type ( user_oid VARCHAR2(36 CHAR) NOT NULL, employeeType VARCHAR2(255 CHAR) ) INITRANS 30; CREATE TABLE m_user_organization ( user_oid VARCHAR2(36 CHAR) NOT NULL, norm VARCHAR2(255 CHAR), orig VARCHAR2(255 CHAR) ) INITRANS 30; CREATE TABLE m_user_organizational_unit ( user_oid VARCHAR2(36 CHAR) NOT NULL, norm VARCHAR2(255 CHAR), orig VARCHAR2(255 CHAR) ) INITRANS 30; CREATE TABLE m_abstract_role ( approvalProcess VARCHAR2(255 CHAR), autoassign_enabled NUMBER(1, 0), displayName_norm VARCHAR2(255 CHAR), displayName_orig VARCHAR2(255 CHAR), identifier VARCHAR2(255 CHAR), ownerRef_relation VARCHAR2(157 CHAR), ownerRef_targetOid VARCHAR2(36 CHAR), ownerRef_type NUMBER(10, 0), requestable NUMBER(1, 0), riskLevel VARCHAR2(255 CHAR), oid VARCHAR2(36 CHAR) NOT NULL, PRIMARY KEY (oid) ) INITRANS 30; CREATE TABLE m_archetype ( name_norm VARCHAR2(255 CHAR), name_orig VARCHAR2(255 CHAR), oid VARCHAR2(36 CHAR) NOT NULL, PRIMARY KEY (oid) ) INITRANS 30; CREATE TABLE m_case ( name_norm VARCHAR2(255 CHAR), name_orig VARCHAR2(255 CHAR), objectRef_relation VARCHAR2(157 CHAR), objectRef_targetOid VARCHAR2(36 CHAR), objectRef_type NUMBER(10, 0), state VARCHAR2(255 CHAR), oid VARCHAR2(36 CHAR) NOT NULL, PRIMARY KEY (oid) ) INITRANS 30; CREATE TABLE m_connector ( connectorBundle VARCHAR2(255 CHAR), connectorHostRef_relation VARCHAR2(157 CHAR), connectorHostRef_targetOid VARCHAR2(36 CHAR), connectorHostRef_type NUMBER(10, 0), connectorType VARCHAR2(255 CHAR), connectorVersion VARCHAR2(255 CHAR), framework VARCHAR2(255 CHAR), name_norm VARCHAR2(255 CHAR), name_orig VARCHAR2(255 CHAR), oid VARCHAR2(36 CHAR) NOT NULL, PRIMARY KEY (oid) ) INITRANS 30; CREATE TABLE m_connector_host ( hostname VARCHAR2(255 CHAR), name_norm VARCHAR2(255 CHAR), name_orig VARCHAR2(255 CHAR), port VARCHAR2(255 CHAR), oid VARCHAR2(36 CHAR) NOT NULL, PRIMARY KEY (oid) ) INITRANS 30; CREATE TABLE m_focus ( administrativeStatus NUMBER(10, 0), archiveTimestamp TIMESTAMP, disableReason VARCHAR2(255 CHAR), disableTimestamp TIMESTAMP, effectiveStatus NUMBER(10, 0), enableTimestamp TIMESTAMP, validFrom TIMESTAMP, validTo TIMESTAMP, validityChangeTimestamp TIMESTAMP, validityStatus NUMBER(10, 0), costCenter VARCHAR2(255 CHAR), emailAddress VARCHAR2(255 CHAR), hasPhoto NUMBER(1, 0) DEFAULT 0 NOT NULL, locale VARCHAR2(255 CHAR), locality_norm VARCHAR2(255 CHAR), locality_orig VARCHAR2(255 CHAR), preferredLanguage VARCHAR2(255 CHAR), telephoneNumber VARCHAR2(255 CHAR), timezone VARCHAR2(255 CHAR), oid VARCHAR2(36 CHAR) NOT NULL, PRIMARY KEY (oid) ) INITRANS 30; CREATE TABLE m_form ( name_norm VARCHAR2(255 CHAR), name_orig VARCHAR2(255 CHAR), oid VARCHAR2(36 CHAR) NOT NULL, PRIMARY KEY (oid) ) INITRANS 30; CREATE TABLE m_function_library ( name_norm VARCHAR2(255 CHAR), name_orig VARCHAR2(255 CHAR), oid VARCHAR2(36 CHAR) NOT NULL, PRIMARY KEY (oid) ) INITRANS 30; CREATE TABLE m_generic_object ( name_norm VARCHAR2(255 CHAR), name_orig VARCHAR2(255 CHAR), objectType VARCHAR2(255 CHAR), oid VARCHAR2(36 CHAR) NOT NULL, PRIMARY KEY (oid) ) INITRANS 30; CREATE TABLE m_global_metadata ( name VARCHAR2(255 CHAR) NOT NULL, value VARCHAR2(255 CHAR), PRIMARY KEY (name) ) INITRANS 30; CREATE TABLE m_lookup_table ( name_norm VARCHAR2(255 CHAR), name_orig VARCHAR2(255 CHAR), oid VARCHAR2(36 CHAR) NOT NULL, PRIMARY KEY (oid) ) INITRANS 30; CREATE TABLE m_lookup_table_row ( id NUMBER(10, 0) NOT NULL, owner_oid VARCHAR2(36 CHAR) NOT NULL, row_key VARCHAR2(255 CHAR), label_norm VARCHAR2(255 CHAR), label_orig VARCHAR2(255 CHAR), lastChangeTimestamp TIMESTAMP, row_value VARCHAR2(255 CHAR), PRIMARY KEY (owner_oid, id) ) INITRANS 30; CREATE TABLE m_node ( name_norm VARCHAR2(255 CHAR), name_orig VARCHAR2(255 CHAR), nodeIdentifier VARCHAR2(255 CHAR), oid VARCHAR2(36 CHAR) NOT NULL, PRIMARY KEY (oid) ) INITRANS 30; CREATE TABLE m_object_collection ( name_norm VARCHAR2(255 CHAR), name_orig VARCHAR2(255 CHAR), oid VARCHAR2(36 CHAR) NOT NULL, PRIMARY KEY (oid) ) INITRANS 30; CREATE TABLE m_object_template ( name_norm VARCHAR2(255 CHAR), name_orig VARCHAR2(255 CHAR), type NUMBER(10, 0), oid VARCHAR2(36 CHAR) NOT NULL, PRIMARY KEY (oid) ) INITRANS 30; CREATE TABLE m_org ( displayOrder NUMBER(10, 0), name_norm VARCHAR2(255 CHAR), name_orig VARCHAR2(255 CHAR), tenant NUMBER(1, 0), oid VARCHAR2(36 CHAR) NOT NULL, PRIMARY KEY (oid) ) INITRANS 30; CREATE TABLE m_report ( export NUMBER(10, 0), name_norm VARCHAR2(255 CHAR), name_orig VARCHAR2(255 CHAR), orientation NUMBER(10, 0), parent NUMBER(1, 0), useHibernateSession NUMBER(1, 0), oid VARCHAR2(36 CHAR) NOT NULL, PRIMARY KEY (oid) ) INITRANS 30; CREATE TABLE m_report_output ( name_norm VARCHAR2(255 CHAR), name_orig VARCHAR2(255 CHAR), reportRef_relation VARCHAR2(157 CHAR), reportRef_targetOid VARCHAR2(36 CHAR), reportRef_type NUMBER(10, 0), oid VARCHAR2(36 CHAR) NOT NULL, PRIMARY KEY (oid) ) INITRANS 30; CREATE TABLE m_resource ( administrativeState NUMBER(10, 0), connectorRef_relation VARCHAR2(157 CHAR), connectorRef_targetOid VARCHAR2(36 CHAR), connectorRef_type NUMBER(10, 0), name_norm VARCHAR2(255 CHAR), name_orig VARCHAR2(255 CHAR), o16_lastAvailabilityStatus NUMBER(10, 0), oid VARCHAR2(36 CHAR) NOT NULL, PRIMARY KEY (oid) ) INITRANS 30; CREATE TABLE m_role ( name_norm VARCHAR2(255 CHAR), name_orig VARCHAR2(255 CHAR), roleType VARCHAR2(255 CHAR), oid VARCHAR2(36 CHAR) NOT NULL, PRIMARY KEY (oid) ) INITRANS 30; CREATE TABLE m_security_policy ( name_norm VARCHAR2(255 CHAR), name_orig VARCHAR2(255 CHAR), oid VARCHAR2(36 CHAR) NOT NULL, PRIMARY KEY (oid) ) INITRANS 30; CREATE TABLE m_sequence ( name_norm VARCHAR2(255 CHAR), name_orig VARCHAR2(255 CHAR), oid VARCHAR2(36 CHAR) NOT NULL, PRIMARY KEY (oid) ) INITRANS 30; CREATE TABLE m_service ( displayOrder NUMBER(10, 0), name_norm VARCHAR2(255 CHAR), name_orig VARCHAR2(255 CHAR), oid VARCHAR2(36 CHAR) NOT NULL, PRIMARY KEY (oid) ) INITRANS 30; CREATE TABLE m_system_configuration ( name_norm VARCHAR2(255 CHAR), name_orig VARCHAR2(255 CHAR), oid VARCHAR2(36 CHAR) NOT NULL, PRIMARY KEY (oid) ) INITRANS 30; CREATE TABLE m_trigger ( id NUMBER(10, 0) NOT NULL, owner_oid VARCHAR2(36 CHAR) NOT NULL, handlerUri VARCHAR2(255 CHAR), timestampValue TIMESTAMP, PRIMARY KEY (owner_oid, id) ) INITRANS 30; CREATE TABLE m_user ( additionalName_norm VARCHAR2(255 CHAR), additionalName_orig VARCHAR2(255 CHAR), employeeNumber VARCHAR2(255 CHAR), familyName_norm VARCHAR2(255 CHAR), familyName_orig VARCHAR2(255 CHAR), fullName_norm VARCHAR2(255 CHAR), fullName_orig VARCHAR2(255 CHAR), givenName_norm VARCHAR2(255 CHAR), givenName_orig VARCHAR2(255 CHAR), honorificPrefix_norm VARCHAR2(255 CHAR), honorificPrefix_orig VARCHAR2(255 CHAR), honorificSuffix_norm VARCHAR2(255 CHAR), honorificSuffix_orig VARCHAR2(255 CHAR), name_norm VARCHAR2(255 CHAR), name_orig VARCHAR2(255 CHAR), nickName_norm VARCHAR2(255 CHAR), nickName_orig VARCHAR2(255 CHAR), title_norm VARCHAR2(255 CHAR), title_orig VARCHAR2(255 CHAR), oid VARCHAR2(36 CHAR) NOT NULL, PRIMARY KEY (oid) ) INITRANS 30; CREATE TABLE m_value_policy ( name_norm VARCHAR2(255 CHAR), name_orig VARCHAR2(255 CHAR), oid VARCHAR2(36 CHAR) NOT NULL, PRIMARY KEY (oid) ) INITRANS 30; CREATE INDEX iCertCampaignNameOrig ON m_acc_cert_campaign (name_orig) INITRANS 30; ALTER TABLE m_acc_cert_campaign ADD CONSTRAINT uc_acc_cert_campaign_name UNIQUE (name_norm); CREATE INDEX iCaseObjectRefTargetOid ON m_acc_cert_case (objectRef_targetOid) INITRANS 30; CREATE INDEX iCaseTargetRefTargetOid ON m_acc_cert_case (targetRef_targetOid) INITRANS 30; CREATE INDEX iCaseTenantRefTargetOid ON m_acc_cert_case (tenantRef_targetOid) INITRANS 30; CREATE INDEX iCaseOrgRefTargetOid ON m_acc_cert_case (orgRef_targetOid) INITRANS 30; CREATE INDEX iCertDefinitionNameOrig ON m_acc_cert_definition (name_orig) INITRANS 30; ALTER TABLE m_acc_cert_definition ADD CONSTRAINT uc_acc_cert_definition_name UNIQUE (name_norm); CREATE INDEX iCertWorkItemRefTargetOid ON m_acc_cert_wi_reference (targetOid) INITRANS 30; CREATE INDEX iAssignmentAdministrative ON m_assignment (administrativeStatus) INITRANS 30; CREATE INDEX iAssignmentEffective ON m_assignment (effectiveStatus) INITRANS 30; CREATE INDEX iAssignmentValidFrom ON m_assignment (validFrom) INITRANS 30; CREATE INDEX iAssignmentValidTo ON m_assignment (validTo) INITRANS 30; CREATE INDEX iTargetRefTargetOid ON m_assignment (targetRef_targetOid) INITRANS 30; CREATE INDEX iTenantRefTargetOid ON m_assignment (tenantRef_targetOid) INITRANS 30; CREATE INDEX iOrgRefTargetOid ON m_assignment (orgRef_targetOid) INITRANS 30; CREATE INDEX iResourceRefTargetOid ON m_assignment (resourceRef_targetOid) INITRANS 30; CREATE INDEX iAExtensionBoolean ON m_assignment_ext_boolean (booleanValue) INITRANS 30; CREATE INDEX iAExtensionDate ON m_assignment_ext_date (dateValue) INITRANS 30; CREATE INDEX iAExtensionLong ON m_assignment_ext_long (longValue) INITRANS 30; CREATE INDEX iAExtensionPolyString ON m_assignment_ext_poly (orig) INITRANS 30; CREATE INDEX iAExtensionReference ON m_assignment_ext_reference (targetoid) INITRANS 30; CREATE INDEX iAExtensionString ON m_assignment_ext_string (stringValue) INITRANS 30; CREATE INDEX iAssignmentReferenceTargetOid ON m_assignment_reference (targetOid) INITRANS 30; CREATE INDEX iAuditDeltaRecordId ON m_audit_delta (record_id) INITRANS 30; CREATE INDEX iTimestampValue ON m_audit_event (timestampValue) INITRANS 30; CREATE INDEX iChangedItemPath ON m_audit_item (changedItemPath) INITRANS 30; CREATE INDEX iAuditItemRecordId ON m_audit_item (record_id) INITRANS 30; CREATE INDEX iAuditPropValRecordId ON m_audit_prop_value (record_id) INITRANS 30; CREATE INDEX iAuditRefValRecordId ON m_audit_ref_value (record_id) INITRANS 30; CREATE INDEX iCaseWorkItemRefTargetOid ON m_case_wi_reference (targetOid) INITRANS 30; ALTER TABLE m_ext_item ADD CONSTRAINT iExtItemDefinition UNIQUE (itemName, itemType, kind); CREATE INDEX iObjectNameOrig ON m_object (name_orig) INITRANS 30; CREATE INDEX iObjectNameNorm ON m_object (name_norm) INITRANS 30; CREATE INDEX iObjectTypeClass ON m_object (objectTypeClass) INITRANS 30; CREATE INDEX iObjectCreateTimestamp ON m_object (createTimestamp) INITRANS 30; CREATE INDEX iObjectLifecycleState ON m_object (lifecycleState) INITRANS 30; CREATE INDEX iExtensionBoolean ON m_object_ext_boolean (booleanValue) INITRANS 30; CREATE INDEX iExtensionDate ON m_object_ext_date (dateValue) INITRANS 30; CREATE INDEX iExtensionLong ON m_object_ext_long (longValue) INITRANS 30; CREATE INDEX iExtensionPolyString ON m_object_ext_poly (orig) INITRANS 30; CREATE INDEX iExtensionReference ON m_object_ext_reference (targetoid) INITRANS 30; CREATE INDEX iExtensionString ON m_object_ext_string (stringValue) INITRANS 30; CREATE INDEX iOpExecTaskOid ON m_operation_execution (taskRef_targetOid) INITRANS 30; CREATE INDEX iOpExecInitiatorOid ON m_operation_execution (initiatorRef_targetOid) INITRANS 30; CREATE INDEX iOpExecStatus ON m_operation_execution (status) INITRANS 30; CREATE INDEX iOpExecOwnerOid ON m_operation_execution (owner_oid) INITRANS 30; CREATE INDEX iAncestor ON m_org_closure (ancestor_oid) INITRANS 30; CREATE INDEX iDescendant ON m_org_closure (descendant_oid) INITRANS 30; CREATE INDEX iDescendantAncestor ON m_org_closure (descendant_oid, ancestor_oid) INITRANS 30; CREATE INDEX iReferenceTargetTypeRelation ON m_reference (targetOid, reference_type, relation) INITRANS 30; CREATE INDEX iShadowResourceRef ON m_shadow (resourceRef_targetOid) INITRANS 30; CREATE INDEX iShadowDead ON m_shadow (dead) INITRANS 30; CREATE INDEX iShadowKind ON m_shadow (kind) INITRANS 30; CREATE INDEX iShadowIntent ON m_shadow (intent) INITRANS 30; CREATE INDEX iShadowObjectClass ON m_shadow (objectClass) INITRANS 30; CREATE INDEX iShadowFailedOperationType ON m_shadow (failedOperationType) INITRANS 30; CREATE INDEX iShadowSyncSituation ON m_shadow (synchronizationSituation) INITRANS 30; CREATE INDEX iShadowPendingOperationCount ON m_shadow (pendingOperationCount) INITRANS 30; CREATE INDEX iShadowNameOrig ON m_shadow (name_orig) INITRANS 30; CREATE INDEX iShadowNameNorm ON m_shadow (name_norm) INITRANS 30; CREATE INDEX iParent ON m_task (parent) INITRANS 30; CREATE INDEX iTaskWfProcessInstanceId ON m_task (wfProcessInstanceId) INITRANS 30; CREATE INDEX iTaskWfStartTimestamp ON m_task (wfStartTimestamp) INITRANS 30; CREATE INDEX iTaskWfEndTimestamp ON m_task (wfEndTimestamp) INITRANS 30; CREATE INDEX iTaskWfRequesterOid ON m_task (wfRequesterRef_targetOid) INITRANS 30; CREATE INDEX iTaskWfObjectOid ON m_task (wfObjectRef_targetOid) INITRANS 30; CREATE INDEX iTaskWfTargetOid ON m_task (wfTargetRef_targetOid) INITRANS 30; CREATE INDEX iTaskNameOrig ON m_task (name_orig) INITRANS 30; ALTER TABLE m_task ADD CONSTRAINT uc_task_identifier UNIQUE (taskIdentifier); CREATE INDEX iAbstractRoleIdentifier ON m_abstract_role (identifier) INITRANS 30; CREATE INDEX iRequestable ON m_abstract_role (requestable) INITRANS 30; CREATE INDEX iAutoassignEnabled ON m_abstract_role(autoassign_enabled) INITRANS 30; CREATE INDEX iArchetypeNameOrig ON m_archetype(name_orig) INITRANS 30; CREATE INDEX iArchetypeNameNorm ON m_archetype(name_norm) INITRANS 30; CREATE INDEX iCaseNameOrig ON m_case (name_orig) INITRANS 30; ALTER TABLE m_case ADD CONSTRAINT uc_case_name UNIQUE (name_norm); CREATE INDEX iConnectorNameOrig ON m_connector (name_orig) INITRANS 30; CREATE INDEX iConnectorNameNorm ON m_connector (name_norm) INITRANS 30; CREATE INDEX iConnectorHostNameOrig ON m_connector_host (name_orig) INITRANS 30; ALTER TABLE m_connector_host ADD CONSTRAINT uc_connector_host_name UNIQUE (name_norm); CREATE INDEX iFocusAdministrative ON m_focus (administrativeStatus) INITRANS 30; CREATE INDEX iFocusEffective ON m_focus (effectiveStatus) INITRANS 30; CREATE INDEX iLocality ON m_focus (locality_orig) INITRANS 30; CREATE INDEX iFocusValidFrom ON m_focus (validFrom) INITRANS 30; CREATE INDEX iFocusValidTo ON m_focus (validTo) INITRANS 30; CREATE INDEX iFormNameOrig ON m_form (name_orig) INITRANS 30; ALTER TABLE m_form ADD CONSTRAINT uc_form_name UNIQUE (name_norm); CREATE INDEX iFunctionLibraryNameOrig ON m_function_library (name_orig) INITRANS 30; ALTER TABLE m_function_library ADD CONSTRAINT uc_function_library_name UNIQUE (name_norm); CREATE INDEX iGenericObjectNameOrig ON m_generic_object (name_orig) INITRANS 30; ALTER TABLE m_generic_object ADD CONSTRAINT uc_generic_object_name UNIQUE (name_norm); CREATE INDEX iLookupTableNameOrig ON m_lookup_table (name_orig) INITRANS 30; ALTER TABLE m_lookup_table ADD CONSTRAINT uc_lookup_name UNIQUE (name_norm); ALTER TABLE m_lookup_table_row ADD CONSTRAINT uc_row_key UNIQUE (owner_oid, row_key); CREATE INDEX iNodeNameOrig ON m_node (name_orig) INITRANS 30; ALTER TABLE m_node ADD CONSTRAINT uc_node_name UNIQUE (name_norm); CREATE INDEX iObjectCollectionNameOrig ON m_object_collection (name_orig) INITRANS 30; ALTER TABLE m_object_collection ADD CONSTRAINT uc_object_collection_name UNIQUE (name_norm); CREATE INDEX iObjectTemplateNameOrig ON m_object_template (name_orig) INITRANS 30; ALTER TABLE m_object_template ADD CONSTRAINT uc_object_template_name UNIQUE (name_norm); CREATE INDEX iDisplayOrder ON m_org (displayOrder) INITRANS 30; CREATE INDEX iOrgNameOrig ON m_org (name_orig) INITRANS 30; ALTER TABLE m_org ADD CONSTRAINT uc_org_name UNIQUE (name_norm); CREATE INDEX iReportParent ON m_report (parent) INITRANS 30; CREATE INDEX iReportNameOrig ON m_report (name_orig) INITRANS 30; ALTER TABLE m_report ADD CONSTRAINT uc_report_name UNIQUE (name_norm); CREATE INDEX iReportOutputNameOrig ON m_report_output (name_orig) INITRANS 30; CREATE INDEX iReportOutputNameNorm ON m_report_output (name_norm) INITRANS 30; CREATE INDEX iResourceNameOrig ON m_resource (name_orig) INITRANS 30; ALTER TABLE m_resource ADD CONSTRAINT uc_resource_name UNIQUE (name_norm); CREATE INDEX iRoleNameOrig ON m_role (name_orig) INITRANS 30; ALTER TABLE m_role ADD CONSTRAINT uc_role_name UNIQUE (name_norm); CREATE INDEX iSecurityPolicyNameOrig ON m_security_policy (name_orig) INITRANS 30; ALTER TABLE m_security_policy ADD CONSTRAINT uc_security_policy_name UNIQUE (name_norm); CREATE INDEX iSequenceNameOrig ON m_sequence (name_orig) INITRANS 30; ALTER TABLE m_sequence ADD CONSTRAINT uc_sequence_name UNIQUE (name_norm); CREATE INDEX iServiceNameOrig ON m_service (name_orig) INITRANS 30; CREATE INDEX iServiceNameNorm ON m_service (name_norm) INITRANS 30; CREATE INDEX iSystemConfigurationNameOrig ON m_system_configuration (name_orig) INITRANS 30; ALTER TABLE m_system_configuration ADD CONSTRAINT uc_system_configuration_name UNIQUE (name_norm); CREATE INDEX iTriggerTimestamp ON m_trigger (timestampValue) INITRANS 30; CREATE INDEX iFullName ON m_user (fullName_orig) INITRANS 30; CREATE INDEX iFamilyName ON m_user (familyName_orig) INITRANS 30; CREATE INDEX iGivenName ON m_user (givenName_orig) INITRANS 30; CREATE INDEX iEmployeeNumber ON m_user (employeeNumber) INITRANS 30; CREATE INDEX iUserNameOrig ON m_user (name_orig) INITRANS 30; ALTER TABLE m_user ADD CONSTRAINT uc_user_name UNIQUE (name_norm); CREATE INDEX iValuePolicyNameOrig ON m_value_policy (name_orig) INITRANS 30; ALTER TABLE m_value_policy ADD CONSTRAINT uc_value_policy_name UNIQUE (name_norm); ALTER TABLE m_acc_cert_campaign ADD CONSTRAINT fk_acc_cert_campaign FOREIGN KEY (oid) REFERENCES m_object; ALTER TABLE m_acc_cert_case ADD CONSTRAINT fk_acc_cert_case_owner FOREIGN KEY (owner_oid) REFERENCES m_acc_cert_campaign; ALTER TABLE m_acc_cert_definition ADD CONSTRAINT fk_acc_cert_definition FOREIGN KEY (oid) REFERENCES m_object; ALTER TABLE m_acc_cert_wi ADD CONSTRAINT fk_acc_cert_wi_owner FOREIGN KEY (owner_owner_oid, owner_id) REFERENCES m_acc_cert_case; ALTER TABLE m_acc_cert_wi_reference ADD CONSTRAINT fk_acc_cert_wi_ref_owner FOREIGN KEY (owner_owner_owner_oid, owner_owner_id, owner_id) REFERENCES m_acc_cert_wi; ALTER TABLE m_assignment ADD CONSTRAINT fk_assignment_owner FOREIGN KEY (owner_oid) REFERENCES m_object; ALTER TABLE m_assignment_ext_boolean ADD CONSTRAINT fk_a_ext_boolean_owner FOREIGN KEY (anyContainer_owner_owner_oid, anyContainer_owner_id) REFERENCES m_assignment_extension; ALTER TABLE m_assignment_ext_boolean ADD CONSTRAINT fk_a_ext_boolean_item FOREIGN KEY (item_id) REFERENCES m_ext_item; ALTER TABLE m_assignment_ext_date ADD CONSTRAINT fk_a_ext_date_owner FOREIGN KEY (anyContainer_owner_owner_oid, anyContainer_owner_id) REFERENCES m_assignment_extension; ALTER TABLE m_assignment_ext_date ADD CONSTRAINT fk_a_ext_date_item FOREIGN KEY (item_id) REFERENCES m_ext_item; ALTER TABLE m_assignment_ext_long ADD CONSTRAINT fk_a_ext_long_owner FOREIGN KEY (anyContainer_owner_owner_oid, anyContainer_owner_id) REFERENCES m_assignment_extension; ALTER TABLE m_assignment_ext_long ADD CONSTRAINT fk_a_ext_long_item FOREIGN KEY (item_id) REFERENCES m_ext_item; ALTER TABLE m_assignment_ext_poly ADD CONSTRAINT fk_a_ext_poly_owner FOREIGN KEY (anyContainer_owner_owner_oid, anyContainer_owner_id) REFERENCES m_assignment_extension; ALTER TABLE m_assignment_ext_poly ADD CONSTRAINT fk_a_ext_poly_item FOREIGN KEY (item_id) REFERENCES m_ext_item; ALTER TABLE m_assignment_ext_reference ADD CONSTRAINT fk_a_ext_reference_owner FOREIGN KEY (anyContainer_owner_owner_oid, anyContainer_owner_id) REFERENCES m_assignment_extension; ALTER TABLE m_assignment_ext_reference ADD CONSTRAINT fk_a_ext_boolean_reference FOREIGN KEY (item_id) REFERENCES m_ext_item; ALTER TABLE m_assignment_ext_string ADD CONSTRAINT fk_a_ext_string_owner FOREIGN KEY (anyContainer_owner_owner_oid, anyContainer_owner_id) REFERENCES m_assignment_extension; ALTER TABLE m_assignment_ext_string ADD CONSTRAINT fk_a_ext_string_item FOREIGN KEY (item_id) REFERENCES m_ext_item; ALTER TABLE m_assignment_policy_situation ADD CONSTRAINT fk_assignment_policy_situation FOREIGN KEY (assignment_oid, assignment_id) REFERENCES m_assignment; ALTER TABLE m_assignment_reference ADD CONSTRAINT fk_assignment_reference FOREIGN KEY (owner_owner_oid, owner_id) REFERENCES m_assignment; ALTER TABLE m_audit_delta ADD CONSTRAINT fk_audit_delta FOREIGN KEY (record_id) REFERENCES m_audit_event; ALTER TABLE m_audit_item ADD CONSTRAINT fk_audit_item FOREIGN KEY (record_id) REFERENCES m_audit_event; ALTER TABLE m_audit_prop_value ADD CONSTRAINT fk_audit_prop_value FOREIGN KEY (record_id) REFERENCES m_audit_event; ALTER TABLE m_audit_ref_value ADD CONSTRAINT fk_audit_ref_value FOREIGN KEY (record_id) REFERENCES m_audit_event; ALTER TABLE m_case_wi ADD CONSTRAINT fk_case_wi_owner FOREIGN KEY (owner_oid) REFERENCES m_case; ALTER TABLE m_case_wi_reference ADD CONSTRAINT fk_case_wi_reference_owner FOREIGN KEY (owner_owner_oid, owner_id) REFERENCES m_case_wi; ALTER TABLE m_connector_target_system ADD CONSTRAINT fk_connector_target_system FOREIGN KEY (connector_oid) REFERENCES m_connector; ALTER TABLE m_focus_photo ADD CONSTRAINT fk_focus_photo FOREIGN KEY (owner_oid) REFERENCES m_focus; ALTER TABLE m_focus_policy_situation ADD CONSTRAINT fk_focus_policy_situation FOREIGN KEY (focus_oid) REFERENCES m_focus; ALTER TABLE m_object_ext_boolean ADD CONSTRAINT fk_o_ext_boolean_owner FOREIGN KEY (owner_oid) REFERENCES m_object; ALTER TABLE m_object_ext_boolean ADD CONSTRAINT fk_o_ext_boolean_item FOREIGN KEY (item_id) REFERENCES m_ext_item; ALTER TABLE m_object_ext_date ADD CONSTRAINT fk_o_ext_date_owner FOREIGN KEY (owner_oid) REFERENCES m_object; ALTER TABLE m_object_ext_date ADD CONSTRAINT fk_o_ext_date_item FOREIGN KEY (item_id) REFERENCES m_ext_item; ALTER TABLE m_object_ext_long ADD CONSTRAINT fk_object_ext_long FOREIGN KEY (owner_oid) REFERENCES m_object; ALTER TABLE m_object_ext_long ADD CONSTRAINT fk_o_ext_long_item FOREIGN KEY (item_id) REFERENCES m_ext_item; ALTER TABLE m_object_ext_poly ADD CONSTRAINT fk_o_ext_poly_owner FOREIGN KEY (owner_oid) REFERENCES m_object; ALTER TABLE m_object_ext_poly ADD CONSTRAINT fk_o_ext_poly_item FOREIGN KEY (item_id) REFERENCES m_ext_item; ALTER TABLE m_object_ext_reference ADD CONSTRAINT fk_o_ext_reference_owner FOREIGN KEY (owner_oid) REFERENCES m_object; ALTER TABLE m_object_ext_reference ADD CONSTRAINT fk_o_ext_reference_item FOREIGN KEY (item_id) REFERENCES m_ext_item; ALTER TABLE m_object_ext_string ADD CONSTRAINT fk_object_ext_string FOREIGN KEY (owner_oid) REFERENCES m_object; ALTER TABLE m_object_ext_string ADD CONSTRAINT fk_o_ext_string_item FOREIGN KEY (item_id) REFERENCES m_ext_item; ALTER TABLE m_object_subtype ADD CONSTRAINT fk_object_subtype FOREIGN KEY (object_oid) REFERENCES m_object; ALTER TABLE m_object_text_info ADD CONSTRAINT fk_object_text_info_owner FOREIGN KEY (owner_oid) REFERENCES m_object; ALTER TABLE m_operation_execution ADD CONSTRAINT fk_op_exec_owner FOREIGN KEY (owner_oid) REFERENCES m_object; ALTER TABLE m_org_closure ADD CONSTRAINT fk_ancestor FOREIGN KEY (ancestor_oid) REFERENCES m_object; ALTER TABLE m_org_closure ADD CONSTRAINT fk_descendant FOREIGN KEY (descendant_oid) REFERENCES m_object; ALTER TABLE m_org_org_type ADD CONSTRAINT fk_org_org_type FOREIGN KEY (org_oid) REFERENCES m_org; ALTER TABLE m_reference ADD CONSTRAINT fk_reference_owner FOREIGN KEY (owner_oid) REFERENCES m_object; ALTER TABLE m_service_type ADD CONSTRAINT fk_service_type FOREIGN KEY (service_oid) REFERENCES m_service; ALTER TABLE m_shadow ADD CONSTRAINT fk_shadow FOREIGN KEY (oid) REFERENCES m_object; ALTER TABLE m_task ADD CONSTRAINT fk_task FOREIGN KEY (oid) REFERENCES m_object; ALTER TABLE m_task_dependent ADD CONSTRAINT fk_task_dependent FOREIGN KEY (task_oid) REFERENCES m_task; ALTER TABLE m_user_employee_type ADD CONSTRAINT fk_user_employee_type FOREIGN KEY (user_oid) REFERENCES m_user; ALTER TABLE m_user_organization ADD CONSTRAINT fk_user_organization FOREIGN KEY (user_oid) REFERENCES m_user; ALTER TABLE m_user_organizational_unit ADD CONSTRAINT fk_user_org_unit FOREIGN KEY (user_oid) REFERENCES m_user; ALTER TABLE m_abstract_role ADD CONSTRAINT fk_abstract_role FOREIGN KEY (oid) REFERENCES m_focus; ALTER TABLE m_archetype ADD CONSTRAINT fk_archetype FOREIGN KEY (oid) REFERENCES m_abstract_role; ALTER TABLE m_case ADD CONSTRAINT fk_case FOREIGN KEY (oid) REFERENCES m_object; ALTER TABLE m_connector ADD CONSTRAINT fk_connector FOREIGN KEY (oid) REFERENCES m_object; ALTER TABLE m_connector_host ADD CONSTRAINT fk_connector_host FOREIGN KEY (oid) REFERENCES m_object; ALTER TABLE m_focus ADD CONSTRAINT fk_focus FOREIGN KEY (oid) REFERENCES m_object; ALTER TABLE m_form ADD CONSTRAINT fk_form FOREIGN KEY (oid) REFERENCES m_object; ALTER TABLE m_function_library ADD CONSTRAINT fk_function_library FOREIGN KEY (oid) REFERENCES m_object; ALTER TABLE m_generic_object ADD CONSTRAINT fk_generic_object FOREIGN KEY (oid) REFERENCES m_focus; ALTER TABLE m_lookup_table ADD CONSTRAINT fk_lookup_table FOREIGN KEY (oid) REFERENCES m_object; ALTER TABLE m_lookup_table_row ADD CONSTRAINT fk_lookup_table_owner FOREIGN KEY (owner_oid) REFERENCES m_lookup_table; ALTER TABLE m_node ADD CONSTRAINT fk_node FOREIGN KEY (oid) REFERENCES m_object; ALTER TABLE m_object_collection ADD CONSTRAINT fk_object_collection FOREIGN KEY (oid) REFERENCES m_object; ALTER TABLE m_object_template ADD CONSTRAINT fk_object_template FOREIGN KEY (oid) REFERENCES m_object; ALTER TABLE m_org ADD CONSTRAINT fk_org FOREIGN KEY (oid) REFERENCES m_abstract_role; ALTER TABLE m_report ADD CONSTRAINT fk_report FOREIGN KEY (oid) REFERENCES m_object; ALTER TABLE m_report_output ADD CONSTRAINT fk_report_output FOREIGN KEY (oid) REFERENCES m_object; ALTER TABLE m_resource ADD CONSTRAINT fk_resource FOREIGN KEY (oid) REFERENCES m_object; ALTER TABLE m_role ADD CONSTRAINT fk_role FOREIGN KEY (oid) REFERENCES m_abstract_role; ALTER TABLE m_security_policy ADD CONSTRAINT fk_security_policy FOREIGN KEY (oid) REFERENCES m_object; ALTER TABLE m_sequence ADD CONSTRAINT fk_sequence FOREIGN KEY (oid) REFERENCES m_object; ALTER TABLE m_service ADD CONSTRAINT fk_service FOREIGN KEY (oid) REFERENCES m_abstract_role; ALTER TABLE m_system_configuration ADD CONSTRAINT fk_system_configuration FOREIGN KEY (oid) REFERENCES m_object; ALTER TABLE m_trigger ADD CONSTRAINT fk_trigger_owner FOREIGN KEY (owner_oid) REFERENCES m_object; ALTER TABLE m_user ADD CONSTRAINT fk_user FOREIGN KEY (oid) REFERENCES m_focus; ALTER TABLE m_value_policy ADD CONSTRAINT fk_value_policy FOREIGN KEY (oid) REFERENCES m_object; INSERT INTO m_global_metadata VALUES ('databaseSchemaVersion', '4.0'); -- -- A hint submitted by a user: Oracle DB MUST be created as "shared" and the -- job_queue_processes parameter must be greater than 2 -- However, these settings are pretty much standard after any -- Oracle install, so most users need not worry about this. -- -- Many other users (including the primary author of Quartz) have had success -- running in dedicated mode, so only consider the above as a hint -- CREATE TABLE qrtz_job_details ( SCHED_NAME VARCHAR2(120) NOT NULL, JOB_NAME VARCHAR2(200) NOT NULL, JOB_GROUP VARCHAR2(200) NOT NULL, DESCRIPTION VARCHAR2(250) NULL, JOB_CLASS_NAME VARCHAR2(250) NOT NULL, IS_DURABLE VARCHAR2(1) NOT NULL, IS_NONCONCURRENT VARCHAR2(1) NOT NULL, IS_UPDATE_DATA VARCHAR2(1) NOT NULL, REQUESTS_RECOVERY VARCHAR2(1) NOT NULL, JOB_DATA BLOB NULL, CONSTRAINT QRTZ_JOB_DETAILS_PK PRIMARY KEY (SCHED_NAME,JOB_NAME,JOB_GROUP) ); CREATE TABLE qrtz_triggers ( SCHED_NAME VARCHAR2(120) NOT NULL, TRIGGER_NAME VARCHAR2(200) NOT NULL, TRIGGER_GROUP VARCHAR2(200) NOT NULL, JOB_NAME VARCHAR2(200) NOT NULL, JOB_GROUP VARCHAR2(200) NOT NULL, DESCRIPTION VARCHAR2(250) NULL, NEXT_FIRE_TIME NUMBER(13) NULL, PREV_FIRE_TIME NUMBER(13) NULL, PRIORITY NUMBER(13) NULL, EXECUTION_GROUP VARCHAR2(200) NULL, TRIGGER_STATE VARCHAR2(16) NOT NULL, TRIGGER_TYPE VARCHAR2(8) NOT NULL, START_TIME NUMBER(13) NOT NULL, END_TIME NUMBER(13) NULL, CALENDAR_NAME VARCHAR2(200) NULL, MISFIRE_INSTR NUMBER(2) NULL, JOB_DATA BLOB NULL, CONSTRAINT QRTZ_TRIGGERS_PK PRIMARY KEY (SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP), CONSTRAINT QRTZ_TRIGGER_TO_JOBS_FK FOREIGN KEY (SCHED_NAME,JOB_NAME,JOB_GROUP) REFERENCES QRTZ_JOB_DETAILS(SCHED_NAME,JOB_NAME,JOB_GROUP) ); CREATE TABLE qrtz_simple_triggers ( SCHED_NAME VARCHAR2(120) NOT NULL, TRIGGER_NAME VARCHAR2(200) NOT NULL, TRIGGER_GROUP VARCHAR2(200) NOT NULL, REPEAT_COUNT NUMBER(7) NOT NULL, REPEAT_INTERVAL NUMBER(12) NOT NULL, TIMES_TRIGGERED NUMBER(10) NOT NULL, CONSTRAINT QRTZ_SIMPLE_TRIG_PK PRIMARY KEY (SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP), CONSTRAINT QRTZ_SIMPLE_TRIG_TO_TRIG_FK FOREIGN KEY (SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP) REFERENCES QRTZ_TRIGGERS(SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP) ); CREATE TABLE qrtz_cron_triggers ( SCHED_NAME VARCHAR2(120) NOT NULL, TRIGGER_NAME VARCHAR2(200) NOT NULL, TRIGGER_GROUP VARCHAR2(200) NOT NULL, CRON_EXPRESSION VARCHAR2(120) NOT NULL, TIME_ZONE_ID VARCHAR2(80), CONSTRAINT QRTZ_CRON_TRIG_PK PRIMARY KEY (SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP), CONSTRAINT QRTZ_CRON_TRIG_TO_TRIG_FK FOREIGN KEY (SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP) REFERENCES QRTZ_TRIGGERS(SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP) ); CREATE TABLE qrtz_simprop_triggers ( SCHED_NAME VARCHAR2(120) NOT NULL, TRIGGER_NAME VARCHAR2(200) NOT NULL, TRIGGER_GROUP VARCHAR2(200) NOT NULL, STR_PROP_1 VARCHAR2(512) NULL, STR_PROP_2 VARCHAR2(512) NULL, STR_PROP_3 VARCHAR2(512) NULL, INT_PROP_1 NUMBER(10) NULL, INT_PROP_2 NUMBER(10) NULL, LONG_PROP_1 NUMBER(13) NULL, LONG_PROP_2 NUMBER(13) NULL, DEC_PROP_1 NUMERIC(13,4) NULL, DEC_PROP_2 NUMERIC(13,4) NULL, BOOL_PROP_1 VARCHAR2(1) NULL, BOOL_PROP_2 VARCHAR2(1) NULL, CONSTRAINT QRTZ_SIMPROP_TRIG_PK PRIMARY KEY (SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP), CONSTRAINT QRTZ_SIMPROP_TRIG_TO_TRIG_FK FOREIGN KEY (SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP) REFERENCES QRTZ_TRIGGERS(SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP) ); CREATE TABLE qrtz_blob_triggers ( SCHED_NAME VARCHAR2(120) NOT NULL, TRIGGER_NAME VARCHAR2(200) NOT NULL, TRIGGER_GROUP VARCHAR2(200) NOT NULL, BLOB_DATA BLOB NULL, CONSTRAINT QRTZ_BLOB_TRIG_PK PRIMARY KEY (SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP), CONSTRAINT QRTZ_BLOB_TRIG_TO_TRIG_FK FOREIGN KEY (SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP) REFERENCES QRTZ_TRIGGERS(SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP) ); CREATE TABLE qrtz_calendars ( SCHED_NAME VARCHAR2(120) NOT NULL, CALENDAR_NAME VARCHAR2(200) NOT NULL, CALENDAR BLOB NOT NULL, CONSTRAINT QRTZ_CALENDARS_PK PRIMARY KEY (SCHED_NAME,CALENDAR_NAME) ); CREATE TABLE qrtz_paused_trigger_grps ( SCHED_NAME VARCHAR2(120) NOT NULL, TRIGGER_GROUP VARCHAR2(200) NOT NULL, CONSTRAINT QRTZ_PAUSED_TRIG_GRPS_PK PRIMARY KEY (SCHED_NAME,TRIGGER_GROUP) ); CREATE TABLE qrtz_fired_triggers ( SCHED_NAME VARCHAR2(120) NOT NULL, ENTRY_ID VARCHAR2(95) NOT NULL, TRIGGER_NAME VARCHAR2(200) NOT NULL, TRIGGER_GROUP VARCHAR2(200) NOT NULL, INSTANCE_NAME VARCHAR2(200) NOT NULL, FIRED_TIME NUMBER(13) NOT NULL, SCHED_TIME NUMBER(13) NOT NULL, PRIORITY NUMBER(13) NOT NULL, EXECUTION_GROUP VARCHAR2(200) NULL, STATE VARCHAR2(16) NOT NULL, JOB_NAME VARCHAR2(200) NULL, JOB_GROUP VARCHAR2(200) NULL, IS_NONCONCURRENT VARCHAR2(1) NULL, REQUESTS_RECOVERY VARCHAR2(1) NULL, CONSTRAINT QRTZ_FIRED_TRIGGER_PK PRIMARY KEY (SCHED_NAME,ENTRY_ID) ); CREATE TABLE qrtz_scheduler_state ( SCHED_NAME VARCHAR2(120) NOT NULL, INSTANCE_NAME VARCHAR2(200) NOT NULL, LAST_CHECKIN_TIME NUMBER(13) NOT NULL, CHECKIN_INTERVAL NUMBER(13) NOT NULL, CONSTRAINT QRTZ_SCHEDULER_STATE_PK PRIMARY KEY (SCHED_NAME,INSTANCE_NAME) ); CREATE TABLE qrtz_locks ( SCHED_NAME VARCHAR2(120) NOT NULL, LOCK_NAME VARCHAR2(40) NOT NULL, CONSTRAINT QRTZ_LOCKS_PK PRIMARY KEY (SCHED_NAME,LOCK_NAME) ); create index idx_qrtz_j_req_recovery on qrtz_job_details(SCHED_NAME,REQUESTS_RECOVERY); create index idx_qrtz_j_grp on qrtz_job_details(SCHED_NAME,JOB_GROUP); create index idx_qrtz_t_j on qrtz_triggers(SCHED_NAME,JOB_NAME,JOB_GROUP); create index idx_qrtz_t_jg on qrtz_triggers(SCHED_NAME,JOB_GROUP); create index idx_qrtz_t_c on qrtz_triggers(SCHED_NAME,CALENDAR_NAME); create index idx_qrtz_t_g on qrtz_triggers(SCHED_NAME,TRIGGER_GROUP); create index idx_qrtz_t_state on qrtz_triggers(SCHED_NAME,TRIGGER_STATE); create index idx_qrtz_t_n_state on qrtz_triggers(SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP,TRIGGER_STATE); create index idx_qrtz_t_n_g_state on qrtz_triggers(SCHED_NAME,TRIGGER_GROUP,TRIGGER_STATE); create index idx_qrtz_t_next_fire_time on qrtz_triggers(SCHED_NAME,NEXT_FIRE_TIME); create index idx_qrtz_t_nft_st on qrtz_triggers(SCHED_NAME,TRIGGER_STATE,NEXT_FIRE_TIME); create index idx_qrtz_t_nft_misfire on qrtz_triggers(SCHED_NAME,MISFIRE_INSTR,NEXT_FIRE_TIME); create index idx_qrtz_t_nft_st_misfire on qrtz_triggers(SCHED_NAME,MISFIRE_INSTR,NEXT_FIRE_TIME,TRIGGER_STATE); create index idx_qrtz_t_nft_st_misfire_grp on qrtz_triggers(SCHED_NAME,MISFIRE_INSTR,NEXT_FIRE_TIME,TRIGGER_GROUP,TRIGGER_STATE); create index idx_qrtz_ft_trig_inst_name on qrtz_fired_triggers(SCHED_NAME,INSTANCE_NAME); create index idx_qrtz_ft_inst_job_req_rcvry on qrtz_fired_triggers(SCHED_NAME,INSTANCE_NAME,REQUESTS_RECOVERY); create index idx_qrtz_ft_j_g on qrtz_fired_triggers(SCHED_NAME,JOB_NAME,JOB_GROUP); create index idx_qrtz_ft_jg on qrtz_fired_triggers(SCHED_NAME,JOB_GROUP); create index idx_qrtz_ft_t_g on qrtz_fired_triggers(SCHED_NAME,TRIGGER_NAME,TRIGGER_GROUP); create index idx_qrtz_ft_tg on qrtz_fired_triggers(SCHED_NAME,TRIGGER_GROUP); create table ACT_GE_PROPERTY ( NAME_ NVARCHAR2(64), VALUE_ NVARCHAR2(300), REV_ INTEGER, primary key (NAME_) ); insert into ACT_GE_PROPERTY values ('schema.version', '5.22.0.0', 1); insert into ACT_GE_PROPERTY values ('schema.history', 'create(5.22.0.0)', 1); insert into ACT_GE_PROPERTY values ('next.dbid', '1', 1); create table ACT_GE_BYTEARRAY ( ID_ NVARCHAR2(64), REV_ INTEGER, NAME_ NVARCHAR2(255), DEPLOYMENT_ID_ NVARCHAR2(64), BYTES_ BLOB, GENERATED_ NUMBER(1,0) CHECK (GENERATED_ IN (1,0)), primary key (ID_) ); create table ACT_RE_DEPLOYMENT ( ID_ NVARCHAR2(64), NAME_ NVARCHAR2(255), CATEGORY_ NVARCHAR2(255), TENANT_ID_ NVARCHAR2(255) DEFAULT '', DEPLOY_TIME_ TIMESTAMP(6), primary key (ID_) ); create table ACT_RE_MODEL ( ID_ NVARCHAR2(64) not null, REV_ INTEGER, NAME_ NVARCHAR2(255), KEY_ NVARCHAR2(255), CATEGORY_ NVARCHAR2(255), CREATE_TIME_ TIMESTAMP(6), LAST_UPDATE_TIME_ TIMESTAMP(6), VERSION_ INTEGER, META_INFO_ NVARCHAR2(2000), DEPLOYMENT_ID_ NVARCHAR2(64), EDITOR_SOURCE_VALUE_ID_ NVARCHAR2(64), EDITOR_SOURCE_EXTRA_VALUE_ID_ NVARCHAR2(64), TENANT_ID_ NVARCHAR2(255) DEFAULT '', primary key (ID_) ); create table ACT_RU_EXECUTION ( ID_ NVARCHAR2(64), REV_ INTEGER, PROC_INST_ID_ NVARCHAR2(64), BUSINESS_KEY_ NVARCHAR2(255), PARENT_ID_ NVARCHAR2(64), PROC_DEF_ID_ NVARCHAR2(64), SUPER_EXEC_ NVARCHAR2(64), ACT_ID_ NVARCHAR2(255), IS_ACTIVE_ NUMBER(1,0) CHECK (IS_ACTIVE_ IN (1,0)), IS_CONCURRENT_ NUMBER(1,0) CHECK (IS_CONCURRENT_ IN (1,0)), IS_SCOPE_ NUMBER(1,0) CHECK (IS_SCOPE_ IN (1,0)), IS_EVENT_SCOPE_ NUMBER(1,0) CHECK (IS_EVENT_SCOPE_ IN (1,0)), SUSPENSION_STATE_ INTEGER, CACHED_ENT_STATE_ INTEGER, TENANT_ID_ NVARCHAR2(255) DEFAULT '', NAME_ NVARCHAR2(255), LOCK_TIME_ TIMESTAMP(6), primary key (ID_) ); create table ACT_RU_JOB ( ID_ NVARCHAR2(64) NOT NULL, REV_ INTEGER, TYPE_ NVARCHAR2(255) NOT NULL, LOCK_EXP_TIME_ TIMESTAMP(6), LOCK_OWNER_ NVARCHAR2(255), EXCLUSIVE_ NUMBER(1,0) CHECK (EXCLUSIVE_ IN (1,0)), EXECUTION_ID_ NVARCHAR2(64), PROCESS_INSTANCE_ID_ NVARCHAR2(64), PROC_DEF_ID_ NVARCHAR2(64), RETRIES_ INTEGER, EXCEPTION_STACK_ID_ NVARCHAR2(64), EXCEPTION_MSG_ NVARCHAR2(2000), DUEDATE_ TIMESTAMP(6), REPEAT_ NVARCHAR2(255), HANDLER_TYPE_ NVARCHAR2(255), HANDLER_CFG_ NVARCHAR2(2000), TENANT_ID_ NVARCHAR2(255) DEFAULT '', primary key (ID_) ); create table ACT_RE_PROCDEF ( ID_ NVARCHAR2(64) NOT NULL, REV_ INTEGER, CATEGORY_ NVARCHAR2(255), NAME_ NVARCHAR2(255), KEY_ NVARCHAR2(255) NOT NULL, VERSION_ INTEGER NOT NULL, DEPLOYMENT_ID_ NVARCHAR2(64), RESOURCE_NAME_ NVARCHAR2(2000), DGRM_RESOURCE_NAME_ varchar(4000), DESCRIPTION_ NVARCHAR2(2000), HAS_START_FORM_KEY_ NUMBER(1,0) CHECK (HAS_START_FORM_KEY_ IN (1,0)), HAS_GRAPHICAL_NOTATION_ NUMBER(1,0) CHECK (HAS_GRAPHICAL_NOTATION_ IN (1,0)), SUSPENSION_STATE_ INTEGER, TENANT_ID_ NVARCHAR2(255) DEFAULT '', primary key (ID_) ); create table ACT_RU_TASK ( ID_ NVARCHAR2(64), REV_ INTEGER, EXECUTION_ID_ NVARCHAR2(64), PROC_INST_ID_ NVARCHAR2(64), PROC_DEF_ID_ NVARCHAR2(64), NAME_ NVARCHAR2(255), PARENT_TASK_ID_ NVARCHAR2(64), DESCRIPTION_ NVARCHAR2(2000), TASK_DEF_KEY_ NVARCHAR2(255), OWNER_ NVARCHAR2(255), ASSIGNEE_ NVARCHAR2(255), DELEGATION_ NVARCHAR2(64), PRIORITY_ INTEGER, CREATE_TIME_ TIMESTAMP(6), DUE_DATE_ TIMESTAMP(6), CATEGORY_ NVARCHAR2(255), SUSPENSION_STATE_ INTEGER, TENANT_ID_ NVARCHAR2(255) DEFAULT '', FORM_KEY_ NVARCHAR2(255), primary key (ID_) ); create table ACT_RU_IDENTITYLINK ( ID_ NVARCHAR2(64), REV_ INTEGER, GROUP_ID_ NVARCHAR2(255), TYPE_ NVARCHAR2(255), USER_ID_ NVARCHAR2(255), TASK_ID_ NVARCHAR2(64), PROC_INST_ID_ NVARCHAR2(64), PROC_DEF_ID_ NVARCHAR2(64), primary key (ID_) ); create table ACT_RU_VARIABLE ( ID_ NVARCHAR2(64) not null, REV_ INTEGER, TYPE_ NVARCHAR2(255) not null, NAME_ NVARCHAR2(255) not null, EXECUTION_ID_ NVARCHAR2(64), PROC_INST_ID_ NVARCHAR2(64), TASK_ID_ NVARCHAR2(64), BYTEARRAY_ID_ NVARCHAR2(64), DOUBLE_ NUMBER(*,10), LONG_ NUMBER(19,0), TEXT_ NVARCHAR2(2000), TEXT2_ NVARCHAR2(2000), primary key (ID_) ); create table ACT_RU_EVENT_SUBSCR ( ID_ NVARCHAR2(64) not null, REV_ integer, EVENT_TYPE_ NVARCHAR2(255) not null, EVENT_NAME_ NVARCHAR2(255), EXECUTION_ID_ NVARCHAR2(64), PROC_INST_ID_ NVARCHAR2(64), ACTIVITY_ID_ NVARCHAR2(64), CONFIGURATION_ NVARCHAR2(255), CREATED_ TIMESTAMP(6) not null, PROC_DEF_ID_ NVARCHAR2(64), TENANT_ID_ NVARCHAR2(255) DEFAULT '', primary key (ID_) ); create table ACT_EVT_LOG ( LOG_NR_ NUMBER(19), TYPE_ NVARCHAR2(64), PROC_DEF_ID_ NVARCHAR2(64), PROC_INST_ID_ NVARCHAR2(64), EXECUTION_ID_ NVARCHAR2(64), TASK_ID_ NVARCHAR2(64), TIME_STAMP_ TIMESTAMP(6) not null, USER_ID_ NVARCHAR2(255), DATA_ BLOB, LOCK_OWNER_ NVARCHAR2(255), LOCK_TIME_ TIMESTAMP(6) null, IS_PROCESSED_ NUMBER(3) default 0, primary key (LOG_NR_) ); create sequence act_evt_log_seq; create table ACT_PROCDEF_INFO ( ID_ NVARCHAR2(64) not null, PROC_DEF_ID_ NVARCHAR2(64) not null, REV_ integer, INFO_JSON_ID_ NVARCHAR2(64), primary key (ID_) ); create index ACT_IDX_EXEC_BUSKEY on ACT_RU_EXECUTION(BUSINESS_KEY_); create index ACT_IDX_TASK_CREATE on ACT_RU_TASK(CREATE_TIME_); create index ACT_IDX_IDENT_LNK_USER on ACT_RU_IDENTITYLINK(USER_ID_); create index ACT_IDX_IDENT_LNK_GROUP on ACT_RU_IDENTITYLINK(GROUP_ID_); create index ACT_IDX_EVENT_SUBSCR_CONFIG_ on ACT_RU_EVENT_SUBSCR(CONFIGURATION_); create index ACT_IDX_VARIABLE_TASK_ID on ACT_RU_VARIABLE(TASK_ID_); create index ACT_IDX_BYTEAR_DEPL on ACT_GE_BYTEARRAY(DEPLOYMENT_ID_); alter table ACT_GE_BYTEARRAY add constraint ACT_FK_BYTEARR_DEPL foreign key (DEPLOYMENT_ID_) references ACT_RE_DEPLOYMENT (ID_); alter table ACT_RE_PROCDEF add constraint ACT_UNIQ_PROCDEF unique (KEY_,VERSION_, TENANT_ID_); create index ACT_IDX_EXE_PROCINST on ACT_RU_EXECUTION(PROC_INST_ID_); alter table ACT_RU_EXECUTION add constraint ACT_FK_EXE_PROCINST foreign key (PROC_INST_ID_) references ACT_RU_EXECUTION (ID_); create index ACT_IDX_EXE_PARENT on ACT_RU_EXECUTION(PARENT_ID_); alter table ACT_RU_EXECUTION add constraint ACT_FK_EXE_PARENT foreign key (PARENT_ID_) references ACT_RU_EXECUTION (ID_); create index ACT_IDX_EXE_SUPER on ACT_RU_EXECUTION(SUPER_EXEC_); alter table ACT_RU_EXECUTION add constraint ACT_FK_EXE_SUPER foreign key (SUPER_EXEC_) references ACT_RU_EXECUTION (ID_); create index ACT_IDX_EXE_PROCDEF on ACT_RU_EXECUTION(PROC_DEF_ID_); alter table ACT_RU_EXECUTION add constraint ACT_FK_EXE_PROCDEF foreign key (PROC_DEF_ID_) references ACT_RE_PROCDEF (ID_); create index ACT_IDX_TSKASS_TASK on ACT_RU_IDENTITYLINK(TASK_ID_); alter table ACT_RU_IDENTITYLINK add constraint ACT_FK_TSKASS_TASK foreign key (TASK_ID_) references ACT_RU_TASK (ID_); create index ACT_IDX_ATHRZ_PROCEDEF on ACT_RU_IDENTITYLINK(PROC_DEF_ID_); alter table ACT_RU_IDENTITYLINK add constraint ACT_FK_ATHRZ_PROCEDEF foreign key (PROC_DEF_ID_) references ACT_RE_PROCDEF (ID_); create index ACT_IDX_IDL_PROCINST on ACT_RU_IDENTITYLINK(PROC_INST_ID_); alter table ACT_RU_IDENTITYLINK add constraint ACT_FK_IDL_PROCINST foreign key (PROC_INST_ID_) references ACT_RU_EXECUTION (ID_); create index ACT_IDX_TASK_EXEC on ACT_RU_TASK(EXECUTION_ID_); alter table ACT_RU_TASK add constraint ACT_FK_TASK_EXE foreign key (EXECUTION_ID_) references ACT_RU_EXECUTION (ID_); create index ACT_IDX_TASK_PROCINST on ACT_RU_TASK(PROC_INST_ID_); alter table ACT_RU_TASK add constraint ACT_FK_TASK_PROCINST foreign key (PROC_INST_ID_) references ACT_RU_EXECUTION (ID_); create index ACT_IDX_TASK_PROCDEF on ACT_RU_TASK(PROC_DEF_ID_); alter table ACT_RU_TASK add constraint ACT_FK_TASK_PROCDEF foreign key (PROC_DEF_ID_) references ACT_RE_PROCDEF (ID_); create index ACT_IDX_VAR_EXE on ACT_RU_VARIABLE(EXECUTION_ID_); alter table ACT_RU_VARIABLE add constraint ACT_FK_VAR_EXE foreign key (EXECUTION_ID_) references ACT_RU_EXECUTION (ID_); create index ACT_IDX_VAR_PROCINST on ACT_RU_VARIABLE(PROC_INST_ID_); alter table ACT_RU_VARIABLE add constraint ACT_FK_VAR_PROCINST foreign key (PROC_INST_ID_) references ACT_RU_EXECUTION(ID_); create index ACT_IDX_VAR_BYTEARRAY on ACT_RU_VARIABLE(BYTEARRAY_ID_); alter table ACT_RU_VARIABLE add constraint ACT_FK_VAR_BYTEARRAY foreign key (BYTEARRAY_ID_) references ACT_GE_BYTEARRAY (ID_); create index ACT_IDX_JOB_EXCEPTION on ACT_RU_JOB(EXCEPTION_STACK_ID_); alter table ACT_RU_JOB add constraint ACT_FK_JOB_EXCEPTION foreign key (EXCEPTION_STACK_ID_) references ACT_GE_BYTEARRAY (ID_); create index ACT_IDX_EVENT_SUBSCR on ACT_RU_EVENT_SUBSCR(EXECUTION_ID_); alter table ACT_RU_EVENT_SUBSCR add constraint ACT_FK_EVENT_EXEC foreign key (EXECUTION_ID_) references ACT_RU_EXECUTION(ID_); create index ACT_IDX_MODEL_SOURCE on ACT_RE_MODEL(EDITOR_SOURCE_VALUE_ID_); alter table ACT_RE_MODEL add constraint ACT_FK_MODEL_SOURCE foreign key (EDITOR_SOURCE_VALUE_ID_) references ACT_GE_BYTEARRAY (ID_); create index ACT_IDX_MODEL_SOURCE_EXTRA on ACT_RE_MODEL(EDITOR_SOURCE_EXTRA_VALUE_ID_); alter table ACT_RE_MODEL add constraint ACT_FK_MODEL_SOURCE_EXTRA foreign key (EDITOR_SOURCE_EXTRA_VALUE_ID_) references ACT_GE_BYTEARRAY (ID_); create index ACT_IDX_MODEL_DEPLOYMENT on ACT_RE_MODEL(DEPLOYMENT_ID_); alter table ACT_RE_MODEL add constraint ACT_FK_MODEL_DEPLOYMENT foreign key (DEPLOYMENT_ID_) references ACT_RE_DEPLOYMENT (ID_); create index ACT_IDX_PROCDEF_INFO_JSON on ACT_PROCDEF_INFO(INFO_JSON_ID_); alter table ACT_PROCDEF_INFO add constraint ACT_FK_INFO_JSON_BA foreign key (INFO_JSON_ID_) references ACT_GE_BYTEARRAY (ID_); create index ACT_IDX_PROCDEF_INFO_PROC on ACT_PROCDEF_INFO(PROC_DEF_ID_); alter table ACT_PROCDEF_INFO add constraint ACT_FK_INFO_PROCDEF foreign key (PROC_DEF_ID_) references ACT_RE_PROCDEF (ID_); alter table ACT_PROCDEF_INFO add constraint ACT_UNIQ_INFO_PROCDEF unique (PROC_DEF_ID_); create table ACT_HI_PROCINST ( ID_ NVARCHAR2(64) not null, PROC_INST_ID_ NVARCHAR2(64) not null, BUSINESS_KEY_ NVARCHAR2(255), PROC_DEF_ID_ NVARCHAR2(64) not null, START_TIME_ TIMESTAMP(6) not null, END_TIME_ TIMESTAMP(6), DURATION_ NUMBER(19,0), START_USER_ID_ NVARCHAR2(255), START_ACT_ID_ NVARCHAR2(255), END_ACT_ID_ NVARCHAR2(255), SUPER_PROCESS_INSTANCE_ID_ NVARCHAR2(64), DELETE_REASON_ NVARCHAR2(2000), TENANT_ID_ NVARCHAR2(255) default '', NAME_ NVARCHAR2(255), primary key (ID_), unique (PROC_INST_ID_) ); create table ACT_HI_ACTINST ( ID_ NVARCHAR2(64) not null, PROC_DEF_ID_ NVARCHAR2(64) not null, PROC_INST_ID_ NVARCHAR2(64) not null, EXECUTION_ID_ NVARCHAR2(64) not null, ACT_ID_ NVARCHAR2(255) not null, TASK_ID_ NVARCHAR2(64), CALL_PROC_INST_ID_ NVARCHAR2(64), ACT_NAME_ NVARCHAR2(255), ACT_TYPE_ NVARCHAR2(255) not null, ASSIGNEE_ NVARCHAR2(255), START_TIME_ TIMESTAMP(6) not null, END_TIME_ TIMESTAMP(6), DURATION_ NUMBER(19,0), TENANT_ID_ NVARCHAR2(255) default '', primary key (ID_) ); create table ACT_HI_TASKINST ( ID_ NVARCHAR2(64) not null, PROC_DEF_ID_ NVARCHAR2(64), TASK_DEF_KEY_ NVARCHAR2(255), PROC_INST_ID_ NVARCHAR2(64), EXECUTION_ID_ NVARCHAR2(64), PARENT_TASK_ID_ NVARCHAR2(64), NAME_ NVARCHAR2(255), DESCRIPTION_ NVARCHAR2(2000), OWNER_ NVARCHAR2(255), ASSIGNEE_ NVARCHAR2(255), START_TIME_ TIMESTAMP(6) not null, CLAIM_TIME_ TIMESTAMP(6), END_TIME_ TIMESTAMP(6), DURATION_ NUMBER(19,0), DELETE_REASON_ NVARCHAR2(2000), PRIORITY_ INTEGER, DUE_DATE_ TIMESTAMP(6), FORM_KEY_ NVARCHAR2(255), CATEGORY_ NVARCHAR2(255), TENANT_ID_ NVARCHAR2(255) default '', primary key (ID_) ); create table ACT_HI_VARINST ( ID_ NVARCHAR2(64) not null, PROC_INST_ID_ NVARCHAR2(64), EXECUTION_ID_ NVARCHAR2(64), TASK_ID_ NVARCHAR2(64), NAME_ NVARCHAR2(255) not null, VAR_TYPE_ NVARCHAR2(100), REV_ INTEGER, BYTEARRAY_ID_ NVARCHAR2(64), DOUBLE_ NUMBER(*,10), LONG_ NUMBER(19,0), TEXT_ NVARCHAR2(2000), TEXT2_ NVARCHAR2(2000), CREATE_TIME_ TIMESTAMP(6), LAST_UPDATED_TIME_ TIMESTAMP(6), primary key (ID_) ); create table ACT_HI_DETAIL ( ID_ NVARCHAR2(64) not null, TYPE_ NVARCHAR2(255) not null, PROC_INST_ID_ NVARCHAR2(64), EXECUTION_ID_ NVARCHAR2(64), TASK_ID_ NVARCHAR2(64), ACT_INST_ID_ NVARCHAR2(64), NAME_ NVARCHAR2(255) not null, VAR_TYPE_ NVARCHAR2(64), REV_ INTEGER, TIME_ TIMESTAMP(6) not null, BYTEARRAY_ID_ NVARCHAR2(64), DOUBLE_ NUMBER(*,10), LONG_ NUMBER(19,0), TEXT_ NVARCHAR2(2000), TEXT2_ NVARCHAR2(2000), primary key (ID_) ); create table ACT_HI_COMMENT ( ID_ NVARCHAR2(64) not null, TYPE_ NVARCHAR2(255), TIME_ TIMESTAMP(6) not null, USER_ID_ NVARCHAR2(255), TASK_ID_ NVARCHAR2(64), PROC_INST_ID_ NVARCHAR2(64), ACTION_ NVARCHAR2(255), MESSAGE_ NVARCHAR2(2000), FULL_MSG_ BLOB, primary key (ID_) ); create table ACT_HI_ATTACHMENT ( ID_ NVARCHAR2(64) not null, REV_ INTEGER, USER_ID_ NVARCHAR2(255), NAME_ NVARCHAR2(255), DESCRIPTION_ NVARCHAR2(2000), TYPE_ NVARCHAR2(255), TASK_ID_ NVARCHAR2(64), PROC_INST_ID_ NVARCHAR2(64), URL_ NVARCHAR2(2000), CONTENT_ID_ NVARCHAR2(64), TIME_ TIMESTAMP(6), primary key (ID_) ); create table ACT_HI_IDENTITYLINK ( ID_ NVARCHAR2(64), GROUP_ID_ NVARCHAR2(255), TYPE_ NVARCHAR2(255), USER_ID_ NVARCHAR2(255), TASK_ID_ NVARCHAR2(64), PROC_INST_ID_ NVARCHAR2(64), primary key (ID_) ); create index ACT_IDX_HI_PRO_INST_END on ACT_HI_PROCINST(END_TIME_); create index ACT_IDX_HI_PRO_I_BUSKEY on ACT_HI_PROCINST(BUSINESS_KEY_); create index ACT_IDX_HI_ACT_INST_START on ACT_HI_ACTINST(START_TIME_); create index ACT_IDX_HI_ACT_INST_END on ACT_HI_ACTINST(END_TIME_); create index ACT_IDX_HI_DETAIL_PROC_INST on ACT_HI_DETAIL(PROC_INST_ID_); create index ACT_IDX_HI_DETAIL_ACT_INST on ACT_HI_DETAIL(ACT_INST_ID_); create index ACT_IDX_HI_DETAIL_TIME on ACT_HI_DETAIL(TIME_); create index ACT_IDX_HI_DETAIL_NAME on ACT_HI_DETAIL(NAME_); create index ACT_IDX_HI_DETAIL_TASK_ID on ACT_HI_DETAIL(TASK_ID_); create index ACT_IDX_HI_PROCVAR_PROC_INST on ACT_HI_VARINST(PROC_INST_ID_); create index ACT_IDX_HI_PROCVAR_NAME_TYPE on ACT_HI_VARINST(NAME_, VAR_TYPE_); create index ACT_IDX_HI_PROCVAR_TASK_ID on ACT_HI_VARINST(TASK_ID_); create index ACT_IDX_HI_IDENT_LNK_USER on ACT_HI_IDENTITYLINK(USER_ID_); create index ACT_IDX_HI_IDENT_LNK_TASK on ACT_HI_IDENTITYLINK(TASK_ID_); create index ACT_IDX_HI_IDENT_LNK_PROCINST on ACT_HI_IDENTITYLINK(PROC_INST_ID_); create index ACT_IDX_HI_ACT_INST_PROCINST on ACT_HI_ACTINST(PROC_INST_ID_, ACT_ID_); create index ACT_IDX_HI_ACT_INST_EXEC on ACT_HI_ACTINST(EXECUTION_ID_, ACT_ID_); create index ACT_IDX_HI_TASK_INST_PROCINST on ACT_HI_TASKINST(PROC_INST_ID_); create table ACT_ID_GROUP ( ID_ NVARCHAR2(64), REV_ INTEGER, NAME_ NVARCHAR2(255), TYPE_ NVARCHAR2(255), primary key (ID_) ); create table ACT_ID_MEMBERSHIP ( USER_ID_ NVARCHAR2(64), GROUP_ID_ NVARCHAR2(64), primary key (USER_ID_, GROUP_ID_) ); create table ACT_ID_USER ( ID_ NVARCHAR2(64), REV_ INTEGER, FIRST_ NVARCHAR2(255), LAST_ NVARCHAR2(255), EMAIL_ NVARCHAR2(255), PWD_ NVARCHAR2(255), PICTURE_ID_ NVARCHAR2(64), primary key (ID_) ); create table ACT_ID_INFO ( ID_ NVARCHAR2(64), REV_ INTEGER, USER_ID_ NVARCHAR2(64), TYPE_ NVARCHAR2(64), KEY_ NVARCHAR2(255), VALUE_ NVARCHAR2(255), PASSWORD_ BLOB, PARENT_ID_ NVARCHAR2(255), primary key (ID_) ); create index ACT_IDX_MEMB_GROUP on ACT_ID_MEMBERSHIP(GROUP_ID_); alter table ACT_ID_MEMBERSHIP add constraint ACT_FK_MEMB_GROUP foreign key (GROUP_ID_) references ACT_ID_GROUP (ID_); create index ACT_IDX_MEMB_USER on ACT_ID_MEMBERSHIP(USER_ID_); alter table ACT_ID_MEMBERSHIP add constraint ACT_FK_MEMB_USER foreign key (USER_ID_) references ACT_ID_USER (ID_); commit;

<reponame>banboy38/Team-Cosmic<filename>UserData/UserData.sql -- MySQL dump 10.13 Distrib 8.0.22, for Win64 (x86_64) -- -- Host: 127.0.0.1 Database: cosmic -- ------------------------------------------------------ -- Server version 8.0.22 /*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */; /*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */; /*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */; /*!50503 SET NAMES utf8 */; /*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */; /*!40103 SET TIME_ZONE='+00:00' */; /*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */; /*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */; /*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */; /*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */; -- -- Table structure for table `blogs` -- DROP TABLE IF EXISTS `blogs`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!50503 SET character_set_client = utf8mb4 */; CREATE TABLE `blogs` ( `id` int NOT NULL AUTO_INCREMENT, `name` varchar(255) DEFAULT NULL, `blog` longblob, PRIMARY KEY (`id`) ) ENGINE=InnoDB AUTO_INCREMENT=271 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `blogs` -- LOCK TABLES `blogs` WRITE; /*!40000 ALTER TABLE `blogs` DISABLE KEYS */; INSERT INTO `blogs` VALUES (243,'<NAME>',_binary 'hallo'),(244,'<NAME>',_binary '<h1>Hello World</h1>\r\n<p>Halp me plox</p>\r\n<i>We are all smol</i>\r\n'),(245,'<NAME>',_binary 'adaw'),(246,'<NAME>',_binary 'adaw'),(247,'<NAME>',_binary 'halp me plox'),(248,'<NAME>',_binary 'halp\r\noijid\r\n'),(249,'<NAME>',_binary 'sddd\r\nasda'),(250,'<NAME>',_binary 'halp'),(251,'<NAME>',_binary 'yolo <br> yolo tolo\r\n'),(252,'<NAME>',_binary '<h1>Purpose of Life</h1> Life jhand ho rakhi hai btech karne se.'),(254,'<NAME>',_binary 'asd asdasdasd'),(255,'<NAME>',_binary '<h1>Ek din marr jayega</h1> kutte ki maut'),(256,'<NAME>',_binary '<h1>Ek din marr jayega</h1> kutte ki maut'),(257,'<NAME>',_binary '<h1>Test 257</h1> First line\r\nSecond line'),(258,'<NAME>',_binary '<h1>Test 258</h1> First line\r\n\r\nSecond line with 2 br.\r\n Third line with space'),(259,'<NAME>',_binary '<h1>hello</h1> qwert\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n<i>yuiop</i>'),(260,'<NAME>',_binary '<h1>Hello</h1> <b>[your content]</b>'),(261,'<NAME>',_binary '<h1>test 261</h1> hello\r\n\r\nalternate test case, trying out 261'),(262,'<NAME>',_binary '<h1>Print</h1> I.am.a.boy.I.am.a.girl.\r\n'),(263,'<NAME>',_binary '<h1>null</h1> Hello, mere gharwaale pure mental hain. Ek saala bolta hi nhi, ek ka muh band hi nhi hota. Help me escape from here plox.'),(264,'<NAME>',_binary '<h1>null</h1> Hello, mere gharwaale pure mental hain. Ek saala bolta hi nhi, ek ka muh band hi nhi hota. Help me escape from here plox.'),(265,'<NAME>',_binary '<h1>s</h1> Hello, mere gharwaale pure mental hain. Ek saala bolta hi nhi, ek ka muh band hi nhi hota. Help me escape from here plox.'),(266,'<NAME>',_binary '<h1>null</h1> Hello, mere gharwaale pure mental hain. Ek saala bolta hi nhi, ek ka muh band hi nhi hota. Help me escape from here plox.'),(267,'<NAME>',_binary '<h1>sad</h1> adwef'),(268,'<NAME>',_binary '<h1>null</h1> Hello, mere gharwaale pure mental hain. Ek saala bolta hi nhi, ek ka muh band hi nhi hota. Help me escape from here plox.'),(269,'<NAME>',_binary '<h1>adsewfew</h1> ewf'),(270,'<NAME>ty',_binary '<h1>null</h1> Hello, mere gharwaale pure mental hain. Ek saala bolta hi nhi, ek ka muh band hi nhi hota. Help me escape from here plox.'); /*!40000 ALTER TABLE `blogs` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `content` -- DROP TABLE IF EXISTS `content`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!50503 SET character_set_client = utf8mb4 */; CREATE TABLE `content` ( `id` int NOT NULL AUTO_INCREMENT, `user` varchar(255) DEFAULT NULL, `email` varchar(255) DEFAULT NULL, `blog` longblob, `heading` varchar(255) DEFAULT NULL, PRIMARY KEY (`id`) ) ENGINE=InnoDB AUTO_INCREMENT=5 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `content` -- LOCK TABLES `content` WRITE; /*!40000 ALTER TABLE `content` DISABLE KEYS */; INSERT INTO `content` VALUES (1,'mc420','<EMAIL>',_binary 'Knowing God is a classic by JI Packer, having sold over a million copies. Its possibly the best selling Contemporary Evangelical book. The book is a study in theology proper, that is, a study of God. The language is simple and accessible to the lay reader and hence its popularity. This book is also endorsed by many evangelical voices such as RC Sproul, <NAME>, and <NAME>.\r\n\r\nThe book is divided into three sections. “Know the Lord”, “Behold Your God”, and “If God is for us”. The first section contains six chapters introducing the book and explains what it means to know God and how can we know Him. The author makes a distinction between the knowledge about God and the knowledge of God. The former being an intellectual profession and the latter being something who end is God Himself. The second section lays down different attributes that are found in scripture, Immutability, Wisdom, Majesty, Grace, Wrath, etc. Finally, in the last section, he shows how these attributes come together in the gospel and by extension in our lives. He explains the privileges that come by being the child of God on, handling trials, and concludes with a chapter on the adequacy of God.\r\n\r\nThe book is quite readable and should be considered as an introductory book on understanding the Godhead. His work is not exhaustive. I think important attributes of God such as his sovereignty, the election of sinners needed separate chapters. Nevertheless, this book was helpful in reminding me of many attributes of God. One quote that impressed me was <i>“He never abandons anyone on whom he has set his love … It is as false as it is irreverent to accuse God of forgetting, or overlooking, or losing interest in, the state and needs of his own people. If you have been resigning yourself to the thought that God has left you high and dry, seek grace to be ashamed of yourself. Such unbelieving pessimism deeply dishonors our great God and Savior “</i>\r\n\r\nIn short, I think this is a book that I would recommend anyone to read.','Knowing God – JI Packer'),(2,'banboy38','<EMAIL>',_binary 'There is a constant debate on the implications of the genre of Genesis 1-11 on the historicity of the events detailed in it. This book presents three views by three different scholars on the genre of Genesis and its implications to three events: creation, flood and the tower of Babel\r\n\r\nBook overview\r\nThe first view is by <NAME>. He essentially espouses the view that all of Genesis is essentially a historically accurate narrative. his main defense lies in the presence of geographical incidentals found in these chapters. He also explains the similarity of Genesis with other Ancient Near East (ANE) is only due to the recollection of a single event and not because the bible borrowed it from them.\r\n\r\nThe second view, by <NAME>, claims that Genesis 1-11 is protohistory. In his own words, ‘history is the photograph\r\nof the past, fiction is like a movie, whereas protohistory is a portrait of the past.’ He, however, does not explain in clear words whether he believes the historicity of Genesis. I think he tries to take a middle ground and ends up confusing the audience.\r\n\r\nThe third view, by <NAME>, claims that Genesis 1-11 is essentially a myth. Sparks lays down some of his presuppositions clearly, which include, the notion that interpretation of scripture should be subservient to modern scientific discovery, the bible could contains elements that are wrong or contradictory, etc. Naturally, with these assumptions, he comes to a different conclusion on Genesis.\r\n\r\nMy review\r\nI think that Hoffmeier uses weak arguments to prove his point. He never resorts to the fact that Genesis is the word of God to defend the historicity of the events. Wenham simply fails to explain what he actually believes in. Even Sparks points this out in his rebuttal to Wenham. Even simple questions as to whether a worldwide flood happened or not, was not answered. He keeps beating around the bush. Finally, I have to reject Sparks’ interpretation because he essentially has non-Christian presuppositions. (Although, I think that his writing was the clearest of them all).\r\n\r\nIn all, I would not recommend anyone to pick up this book unless they are doing extensive research on this subject. It does not offer any substantial value to an average Christian.','Genesis: History, Fiction, or Neither?'),(3,'tanker','',_binary 'Life is a characteristic that distinguishes physical entities that have biological processes, such as signaling and self-sustaining processes, from those that do not, either because such functions have ceased (they have died), or because they never had such functions and are classified as inanimate. Various forms of life exist, such as plants, animals, fungi, protists, archaea, and bacteria. Biology is the science concerned with the study of life.\r\n\r\nThere is currently no consensus regarding the definition of life. One popular definition is that organisms are open systems that maintain homeostasis, are composed of cells, have a life cycle, undergo metabolism, can grow, adapt to their environment, respond to stimuli, reproduce and evolve. Other definitions sometimes include non-cellular life forms such as viruses and viroids.\r\n\r\nAbiogenesis is the natural process of life arising from non-living matter, such as simple organic compounds. The prevailing scientific hypothesis is that the transition from non-living to living entities was not a single event, but a gradual process of increasing complexity. Life on Earth first appeared as early as 4.28 billion years ago, soon after ocean formation 4.41 billion years ago, and not long after the formation of the Earth 4.54 billion years ago.[1][2][3][4] The earliest known life forms are microfossils of bacteria.[5][6] Researchers generally think that current life on Earth descends from an RNA world,[7] although RNA-based life may not have been the first life to have existed.[8][9] The classic 1952 Miller–Urey experiment and similar research demonstrated that most amino acids, the chemical constituents of the proteins used in all living organisms, can be synthesized from inorganic compounds under conditions intended to replicate those of the early Earth. Complex organic molecules occur in the Solar System and in interstellar space, and these molecules may have provided starting material for the development of life on Earth.','The Way Life is'),(4,'babu','<EMAIL>',_binary '“Blog” is an abbreviated version of “weblog,” which is a term used to describe websites that maintain an ongoing chronicle of information. A blog features diary-type commentary and links to articles on other websites, usually presented as a list of entries in reverse chronological order. Blogs range from the personal to the political, and can focus on one narrow subject or a whole range of subjects.\r\n\r\nMany blogs focus on a particular topic, such as web design, home staging, sports, or mobile technology. Some are more eclectic, presenting links to all types of other sites. And others are more like personal journals, presenting the author’s daily life and thoughts.\r\n\r\nGenerally speaking (although there are exceptions), blogs tend to have a few things in common:\r\n\r\n-> A main content area with articles listed chronologically, newest on top. Often, the articles are organized \r\n into categories.An archive of older articles.\r\n-> A way for people to leave comments about the articles.\r\n-> A list of links to other related sites, sometimes','Introduction to Blogging'); /*!40000 ALTER TABLE `content` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `faq` -- DROP TABLE IF EXISTS `faq`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!50503 SET character_set_client = utf8mb4 */; CREATE TABLE `faq` ( `id` int NOT NULL AUTO_INCREMENT, `name` varchar(255) DEFAULT NULL, `email` varchar(255) DEFAULT NULL, `query` text, PRIMARY KEY (`id`) ) ENGINE=InnoDB AUTO_INCREMENT=7 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `faq` -- LOCK TABLES `faq` WRITE; /*!40000 ALTER TABLE `faq` DISABLE KEYS */; INSERT INTO `faq` VALUES (1,'<NAME>','<EMAIL>','Mera site andha hang karra hai'),(2,'<NAME>','<EMAIL>','Blog kahan likhoon be'),(3,'<NAME>','<EMAIL>','Bhaiiiii site dikh toh achha lag raha hai, backend nhi samajh aara bas'),(4,'<NAME>','<EMAIL>','Test query'),(5,'<NAME>','<EMAIL>','aaja mere khwaja'),(6,'Futanari','<EMAIL>','Zindagi jhand hai'); /*!40000 ALTER TABLE `faq` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `people` -- DROP TABLE IF EXISTS `people`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!50503 SET character_set_client = utf8mb4 */; CREATE TABLE `people` ( `id` int NOT NULL AUTO_INCREMENT, `user` varchar(255) DEFAULT NULL, `pass` varchar(255) DEFAULT NULL, `email` varchar(255) DEFAULT NULL, `name` varchar(255) DEFAULT NULL, PRIMARY KEY (`id`) ) ENGINE=InnoDB AUTO_INCREMENT=6 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `people` -- LOCK TABLES `people` WRITE; /*!40000 ALTER TABLE `people` DISABLE KEYS */; INSERT INTO `people` VALUES (1,'babu','theSUNisalsoastar<3','<EMAIL>',NULL),(2,'tanker','youngdumbbroke',NULL,NULL),(3,'elhaaaam____','frenchfries','<EMAIL>',NULL),(4,'banboy38','Purtyisthebest<3','<EMAIL>','<NAME>'),(5,'mc420','halp','<EMAIL>',NULL); /*!40000 ALTER TABLE `people` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `subscriptions` -- DROP TABLE IF EXISTS `subscriptions`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!50503 SET character_set_client = utf8mb4 */; CREATE TABLE `subscriptions` ( `id` int NOT NULL AUTO_INCREMENT, `email` varchar(255) DEFAULT NULL, `phone` varchar(255) DEFAULT NULL, PRIMARY KEY (`id`) ) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `subscriptions` -- LOCK TABLES `subscriptions` WRITE; /*!40000 ALTER TABLE `subscriptions` DISABLE KEYS */; INSERT INTO `subscriptions` VALUES (1,'<EMAIL>','+91 9971380284'); /*!40000 ALTER TABLE `subscriptions` ENABLE KEYS */; UNLOCK TABLES; /*!40103 SET TIME_ZONE=@OLD_TIME_ZONE */; /*!40101 SET SQL_MODE=@OLD_SQL_MODE */; /*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */; /*!40014 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS */; /*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */; /*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */; /*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */; /*!40111 SET SQL_NOTES=@OLD_SQL_NOTES */; -- Dump completed on 2020-11-10 2:45:12

<gh_stars>1000+ ------------------------------------------------------------------------------- -- disk file ------------------------------------------------------------------------------- CREATE TABLE DISK_FILE( ID BIGINT NOT NULL, NAME VARCHAR(200), FILE_SIZE BIGINT, VALUE VARCHAR(200), TYPE VARCHAR(10), PART_INDEX INT, FILE_CODE BIGINT, REF_COUNT INT, HASH_CODE VARCHAR(64), CREATOR VARCHAR(64), CREATE_TIME DATETIME, UPDATER VARCHAR(64), UPDATE_TIME DATETIME, STATUS VARCHAR(50), USER_ID VARCHAR(64), FOLDER_PATH VARCHAR(200), CONSTRAINT PK_DISK_FILE PRIMARY KEY(ID) ) ENGINE=INNODB CHARSET=UTF8; CREATE INDEX IDX_DISK_FILE_HASHCODE ON DISK_FILE(HASH_CODE);

-- @testpoint: opengauss关键字enum(非保留)，作为同义词对象名，部分测试点合理报错 --前置条件 drop table if exists enum_test; create table enum_test(id int,name varchar(10)); --关键字不带引号-成功 drop synonym if exists enum; create synonym enum for enum_test; insert into enum values (1,'ada'),(2, 'bob'); update enum set enum.name='cici' where enum.id=2; select * from enum; drop synonym if exists enum; --关键字带双引号-成功 drop synonym if exists "enum"; create synonym "enum" for enum_test; drop synonym if exists "enum"; --关键字带单引号-合理报错 drop synonym if exists 'enum'; create synonym 'enum' for enum_test; insert into 'enum' values (1,'ada'),(2, 'bob'); update 'enum' set 'enum'.name='cici' where 'enum'.id=2; select * from 'enum'; --关键字带反引号-合理报错 drop synonym if exists `enum`; create synonym `enum` for enum_test; insert into `enum` values (1,'ada'),(2, 'bob'); update `enum` set `enum`.name='cici' where `enum`.id=2; select * from `enum`; drop table if exists enum_test;

<gh_stars>0 -- @testpoint: 创建多个表，创建相同索引名，合理报错 drop table if exists table_ind_confs_004; create table table_ind_confs_004( c_id int, c_integer integer, c_real real,c_float float, c_double int, c_decimal decimal(38), c_number number(38),c_number1 number,c_number2 number(20,10),c_numeric numeric(38), c_char char(50) default null, c_varchar varchar(20), c_varchar2 varchar2(4000), c_clob clob, c_raw raw(20),c_blob blob, c_timestamp timestamp ); drop table if exists table_ind_confs_1_004; create table table_ind_confs_1_004( c_id int, c_integer integer, c_real real,c_float float, c_double int, c_decimal decimal(38), c_number number(38),c_number1 number,c_number2 number(20,10),c_numeric numeric(38), c_char char(50) default null, c_varchar varchar(20), c_varchar2 varchar2(4000), c_clob clob, c_raw raw(20),c_blob blob, c_timestamp timestamp ); drop index if exists index_ind_confs_004 cascade; create index index_ind_confs_004 on table_ind_confs_004 (c_id,c_varchar); create index index_ind_confs_004 on table_ind_confs_004 (c_number1); drop index if exists index_ind_confs_004 ; drop index if exists index_ind_confs_004 ; drop table if exists table_ind_confs_004; drop table if exists table_ind_confs_1_004;

<gh_stars>0 ### Schema DROP DATABASE IF EXISTS todo_db; CREATE DATABASE todo_db; USE todo_db; CREATE TABLE todo ( id INT NOT NULL AUTO_INCREMENT, name VARCHAR(255) NOT NULL, complete BOOLEAN DEFAULT false, PRIMARY KEY (id) );

<reponame>Coslate/MySQL-Bootcamp<gh_stars>0 CREATE TABLE users( email VARCHAR(255) PRIMARY KEY NOT NULL, created_at TIMESTAMP NOT NULL DEFAULT NOW() ); INSERT INTO users(email) VALUES ('<EMAIL>'), ('<EMAIL>');

<filename>process shortsReal.sql /* share short data procedure -- to add imported short data to the share data -- and link them. -- WARNING can take up to 24 hours to run the process -- author PE 2014 */ -------------------------------------------------------------------- -- populate shares table with short and -- percentage short change per day -- value for dates declare @mydate datetime, @epic varchar(20), @id int, @short float while ((select count(id) from shares where shortReal is null) > 0) begin select top 1 @id = id, @mydate = [date], @epic = epic from shares where shortReal is null order by id desc select @short = isnull(short2,0) FROM short INNER JOIN epic ON short.ISIN = epic.ISIN where TIDM = @epic and [position date] in ( select max([position date]) FROM short INNER JOIN epic ON short.ISIN = epic.ISIN where TIDM = @epic and [position date] <= @mydate ) update shares set shortReal = @short where id = @id set @short = 0 end -- process value change shorts declare @mydate datetime, @epic varchar(20), @id int, @short float set @Epic = '' While (Select Count(*) From shares Where percentChangeshortReal is NULL) > 0 Begin Select Top 1 @Epic = Epic From shares Where percentChangeshortReal is NULL update [current] Set percentChangeshortReal = cast((ISNULL([next].[shortReal], [current].[shortReal]) - [current].[shortReal]) as decimal(18,2)) FROM shares AS [current] LEFT JOIN shares AS [next] ON [next].id = (SELECT MIN(id) FROM shares WHERE id > [current].id and epic = @Epic) WHERE [current].epic = @Epic End -- process value change price update shares set percentChangePrice = NULL Declare @Date datetime, @Epic nchar(10), @short float While (Select Count(*) From shares Where percentChangePrice is NULL) > 0 Begin Select Top 1 @Epic = Epic From shares Where percentChangePrice is NULL update [current] Set percentChangePrice = cast((ISNULL([next].[close], [current].[close]) - [current].[close]) as decimal(18,2)) FROM shares AS [current] LEFT JOIN shares AS [next] ON [next].id = (SELECT MIN(id) FROM shares WHERE id > [current].id and epic = @Epic) WHERE [current].epic = @Epic End Declare @Epic nchar(10), @CulminativeChangePrice float While (Select Count(*) From shares Where CulminativeChangePrice is NULL) > 0 Begin Select Top 1 @Epic = Epic From shares Where CulminativeChangePrice is NULL set @CulminativeChangePrice = 0 UPDATE shares SET @CulminativeChangePrice = CulminativeChangePrice = @CulminativeChangePrice + PercentChangePrice FROM shares where epic = @Epic End -- test select * from shares where epic = 'SKY'

-- Adminer 4.2.1 MySQL dump SET NAMES utf8; SET time_zone = '+00:00'; SET foreign_key_checks = 0; SET sql_mode = 'NO_AUTO_VALUE_ON_ZERO'; DROP TABLE IF EXISTS `comments`; CREATE TABLE `comments` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `comment` text COLLATE utf8_unicode_ci NOT NULL, `project_id` int(10) unsigned NOT NULL, `user_name` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `user_id` int(10) unsigned DEFAULT NULL, `approved_by` int(10) unsigned DEFAULT NULL, `replaces_id` int(10) unsigned DEFAULT NULL, `state` int(10) unsigned NOT NULL, `refusal_msg` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `created_at` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00', `updated_at` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00', PRIMARY KEY (`id`), KEY `comments_project_id_foreign` (`project_id`), KEY `comments_user_id_foreign` (`user_id`), KEY `comments_approved_by_foreign` (`approved_by`), KEY `comments_replaces_id_foreign` (`replaces_id`), CONSTRAINT `comments_approved_by_foreign` FOREIGN KEY (`approved_by`) REFERENCES `users` (`id`) ON DELETE CASCADE, CONSTRAINT `comments_project_id_foreign` FOREIGN KEY (`project_id`) REFERENCES `projects` (`id`) ON DELETE CASCADE, CONSTRAINT `comments_replaces_id_foreign` FOREIGN KEY (`replaces_id`) REFERENCES `comments` (`id`) ON DELETE CASCADE, CONSTRAINT `comments_user_id_foreign` FOREIGN KEY (`user_id`) REFERENCES `users` (`id`) ON DELETE CASCADE ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; DROP TABLE IF EXISTS `institutions`; CREATE TABLE `institutions` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `name` varchar(255) COLLATE utf8_unicode_ci NOT NULL, PRIMARY KEY (`id`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; INSERT INTO `institutions` (`id`, `name`) VALUES (1, 'Instituto Politécnico de Leiria'), (2, 'Instituto Politécnico de Santarém'), (3, 'Instituto Politécnico de Lisboa'), (4, 'Instituto Politécnico do Porto'), (5, 'Instituto Politécnico de Tomar'), (6, 'Instituto Politécnico de Beja'), (7, 'Universidade de Lisboa'), (8, 'Universidade de Coimbra'), (9, 'Universidade de Porto'), (10, 'Universidade de Aveiro'), (11, 'Universidade do Minho'), (12, 'Universidade do Algarve'), (13, 'Universidade da Beira Interior'), (14, 'Centro de Investigação em Informática e Comunicações'), (15, 'INESC'), (16, 'Instituto de Telecomunicações'); DROP TABLE IF EXISTS `institution_project`; CREATE TABLE `institution_project` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `institution_id` int(10) unsigned NOT NULL, `project_id` int(10) unsigned NOT NULL, `created_at` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00', `updated_at` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00', PRIMARY KEY (`id`), UNIQUE KEY `institution_project_institution_id_project_id_unique` (`institution_id`,`project_id`), KEY `institution_project_project_id_foreign` (`project_id`), CONSTRAINT `institution_project_institution_id_foreign` FOREIGN KEY (`institution_id`) REFERENCES `institutions` (`id`) ON DELETE CASCADE, CONSTRAINT `institution_project_project_id_foreign` FOREIGN KEY (`project_id`) REFERENCES `projects` (`id`) ON DELETE CASCADE ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; DROP TABLE IF EXISTS `media`; CREATE TABLE `media` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `project_id` int(10) unsigned NOT NULL, `title` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `description` text COLLATE utf8_unicode_ci NOT NULL, `alt` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `flags` smallint(6) NOT NULL, `mime_type` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `ext_url` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `int_file` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `public_name` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `created_by` int(10) unsigned NOT NULL, `approved_by` int(10) unsigned NOT NULL, `replaces_id` int(10) unsigned DEFAULT NULL, `state` int(10) unsigned NOT NULL, `refusal_msg` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `created_at` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00', `updated_at` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00', PRIMARY KEY (`id`), KEY `media_project_id_foreign` (`project_id`), KEY `media_created_by_foreign` (`created_by`), KEY `media_approved_by_foreign` (`approved_by`), KEY `media_replaces_id_foreign` (`replaces_id`), CONSTRAINT `media_approved_by_foreign` FOREIGN KEY (`approved_by`) REFERENCES `users` (`id`) ON DELETE CASCADE, CONSTRAINT `media_created_by_foreign` FOREIGN KEY (`created_by`) REFERENCES `users` (`id`) ON DELETE CASCADE, CONSTRAINT `media_project_id_foreign` FOREIGN KEY (`project_id`) REFERENCES `projects` (`id`) ON DELETE CASCADE, CONSTRAINT `media_replaces_id_foreign` FOREIGN KEY (`replaces_id`) REFERENCES `media` (`id`) ON DELETE CASCADE ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; INSERT INTO `media` (`id`, `project_id`, `title`, `description`, `alt`, `flags`, `mime_type`, `ext_url`, `int_file`, `public_name`, `created_by`, `approved_by`, `replaces_id`, `state`, `refusal_msg`, `created_at`, `updated_at`) VALUES (7, 3, 'Deleniti numquam nesciunt qui.', 'Maxime vero ut minima rerum numquam ut. Vitae doloremque natus molestiae ipsam quo praesentium. Aut error quisquam hic molestiae ea consequatur.', 'Quia repellat omnis officiis quas eveniet.', 0, 'image/jpg', NULL, 'projects/Dehole6.jpg', 'projects/Dehole6.jpg', 17, 3, NULL, 1, NULL, '2015-06-17 23:51:06', '2015-06-17 23:51:06'), (10, 3, 'Voluptatem id nihil repudiandae.', 'Dolores minima minus dolor veritatis officiis inventore. Iure error esse eos quis unde dolorum praesentium.', 'Molestiae mollitia est quisquam et.', 0, 'image/jpg', NULL, 'projects/Dehole9.jpg', 'projects/Dehole9.jpg', 6, 15, NULL, 1, NULL, '2015-06-17 23:51:11', '2015-06-17 23:51:11'), (11, 4, 'Nihil incidunt molestiae nostrum.', 'Iure accusantium suscipit est ipsa. Consequatur temporibus distinctio laborum est est sint maxime. Et quod ut quo at saepe quidem.', 'Ullam quis minus.', 0, 'image/jpg', NULL, 'projects/Ivale10.jpg', 'projects/Ivale10.jpg', 10, 15, NULL, 1, NULL, '2015-06-17 23:51:12', '2015-06-17 23:51:12'), (14, 2, 'Et numquam rerum iste.', 'Nisi quis.', 'Asperiores natus ex omnis.', 0, 'image/jpg', NULL, 'projects/Uip13.jpg', 'projects/Uip13.jpg', 3, 16, NULL, 1, NULL, '2015-06-17 23:51:15', '2015-06-17 23:51:15'), (17, 4, 'Facilis neque consequatur.', 'Ut tenetur dolor in rerum. Vel vel laudantium rerum quis. Minus odio soluta repellendus et et officia quisquam.', 'Ipsam consequuntur distinctio eum beatae quibusdam.', 0, 'image/jpg', NULL, 'projects/Ivale16.jpg', 'projects/Ivale16.jpg', 15, 5, NULL, 1, NULL, '2015-06-17 23:51:18', '2015-06-17 23:51:18'), (18, 2, 'Fugiat porro accusantium.', 'Sed.', 'Unde sed sunt nisi totam.', 0, 'image/jpg', NULL, 'projects/Uip17.jpg', 'projects/Uip17.jpg', 19, 20, NULL, 1, NULL, '2015-06-17 23:51:19', '2015-06-17 23:51:19'), (20, 4, 'Aut dolor id aut.', 'Facilis provident aspernatur inventore. Explicabo magni esse quos quas incidunt. Voluptatum voluptates consequatur ducimus nemo. Illum quis modi aut fugit voluptates qui.', 'Accusamus doloremque minus veritatis.', 0, 'image/jpg', NULL, 'projects/Ivale19.jpg', 'projects/Ivale19.jpg', 15, 14, NULL, 1, NULL, '2015-06-17 23:51:20', '2015-06-17 23:51:20'); DROP TABLE IF EXISTS `migrations`; CREATE TABLE `migrations` ( `migration` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `batch` int(11) NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; INSERT INTO `migrations` (`migration`, `batch`) VALUES ('2015_03_01_000001_create_institutions_table', 1), ('2015_03_01_000002_create_tags_table', 1), ('2015_03_01_000010_create_users_table', 1), ('2015_03_01_000100_create_projects_table', 1), ('2015_03_01_001000_create_institution_project_table', 1), ('2015_03_01_002000_create_project_tag_table', 1), ('2015_03_01_003000_create_project_user_table', 1), ('2015_03_01_004000_create_media_table', 1), ('2015_03_01_005000_create_comments_table', 1); DROP TABLE IF EXISTS `projects`; CREATE TABLE `projects` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `name` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `acronym` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `description` text COLLATE utf8_unicode_ci NOT NULL, `type` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `theme` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `keywords` text COLLATE utf8_unicode_ci, `started_at` date NOT NULL, `finished_at` date DEFAULT NULL, `created_by` int(10) unsigned NOT NULL, `updated_by` int(10) unsigned NOT NULL, `approved_by` int(10) unsigned DEFAULT NULL, `used_software` text COLLATE utf8_unicode_ci, `used_hardware` text COLLATE utf8_unicode_ci, `observations` text COLLATE utf8_unicode_ci, `featured_until` date DEFAULT NULL, `replaces_id` int(10) unsigned DEFAULT NULL, `state` int(10) unsigned NOT NULL, `refusal_msg` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `deleted_at` timestamp NULL DEFAULT NULL, `created_at` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00', `updated_at` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00', PRIMARY KEY (`id`), KEY `projects_created_by_foreign` (`created_by`), KEY `projects_updated_by_foreign` (`updated_by`), KEY `projects_approved_by_foreign` (`approved_by`), KEY `projects_replaces_id_foreign` (`replaces_id`), CONSTRAINT `projects_approved_by_foreign` FOREIGN KEY (`approved_by`) REFERENCES `users` (`id`) ON DELETE CASCADE, CONSTRAINT `projects_created_by_foreign` FOREIGN KEY (`created_by`) REFERENCES `users` (`id`) ON DELETE CASCADE, CONSTRAINT `projects_replaces_id_foreign` FOREIGN KEY (`replaces_id`) REFERENCES `projects` (`id`) ON DELETE CASCADE, CONSTRAINT `projects_updated_by_foreign` FOREIGN KEY (`updated_by`) REFERENCES `users` (`id`) ON DELETE CASCADE ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; INSERT INTO `projects` (`id`, `name`, `acronym`, `description`, `type`, `theme`, `keywords`, `started_at`, `finished_at`, `created_by`, `updated_by`, `approved_by`, `used_software`, `used_hardware`, `observations`, `featured_until`, `replaces_id`, `state`, `refusal_msg`, `deleted_at`, `created_at`, `updated_at`) VALUES (1, 'Assimilated attitude-oriented conglomeration', 'Aaco', 'Eaque dolorem odit architecto error velit. Modi qui quas praesentium et est quam. Placeat molestiae voluptate sed aliquid.', 'Ratione ratione qui et enim aliquam.', 'et', 'vero, velit', '2014-08-31', NULL, 6, 13, NULL, 'Mozilla/5.0 (Windows NT 6.1) AppleWebKit/5350 (KHTML, like Gecko) Chrome/39.0.807.0 Mobile Safari/5350', NULL, NULL, '2017-02-02', NULL, 1, NULL, NULL, '2015-06-17 23:51:00', '2015-06-17 23:51:00'), (2, 'Upgradable impactful processimprovement', 'Uip', 'Magnam odio et reprehenderit dolore sunt. Non quia tempora eum sunt. Incidunt blanditiis omnis aut dolorum.\r\nEt impedit dolor odit saepe asperiores non et. Est quod quidem aut laborum cumque pariatur quia. Sequi eaque sapiente reprehenderit laboriosam.\r\nDolorem autem voluptas enim aut est. Inventore dolor sapiente et odit harum corrupti architecto. Explicabo debitis perspiciatis et.', 'Quis commodi eum.', 'blanditiis', 'iste, accusamus, placeat, quidem, voluptas', '2011-06-05', NULL, 12, 20, NULL, NULL, NULL, 'Maiores et nam asperiores error eveniet.', '2017-10-29', NULL, 1, NULL, NULL, '2015-06-17 23:51:00', '2015-06-17 23:51:00'), (3, 'Decentralized homogeneous leverage', 'Dehole', 'Error perspiciatis placeat numquam asperiores. Nihil blanditiis vel laboriosam eaque. Aliquid aut sit perspiciatis molestias voluptates amet.\r\nAlias et laboriosam quae eius. Consectetur at et nulla accusantium nemo deleniti. Et quos laborum sit illum. In et beatae dolores ullam tempora eligendi.', 'Qui consectetur neque nostrum officiis.', 'facilis', 'consequatur, consequatur, odit, similique', '2014-08-30', NULL, 3, 14, NULL, 'Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10_6_8) AppleWebKit/5310 (KHTML, like Gecko) Chrome/38.0.813.0 Mobile Safari/5310', NULL, NULL, NULL, NULL, 1, NULL, NULL, '2015-06-17 23:51:00', '2015-06-17 23:51:00'), (4, 'Implemented value-added leverage', 'Ivale', 'Accusantium nihil numquam mollitia quaerat. Itaque facilis eius nisi tempore consequatur. Sed quae consequuntur officiis eum et pariatur quam. Maiores voluptates expedita hic harum.', 'Odit ut reprehenderit eos voluptatum.', 'aut', 'debitis, illo, eligendi', '2012-02-11', NULL, 11, 14, NULL, 'Opera/9.55 (X11; Linux i686; en-US) Presto/2.9.201 Version/10.00', NULL, NULL, NULL, NULL, 1, NULL, NULL, '2015-06-17 23:51:00', '2015-06-17 23:51:00'); DROP TABLE IF EXISTS `project_tag`; CREATE TABLE `project_tag` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `project_id` int(10) unsigned NOT NULL, `tag_id` int(10) unsigned NOT NULL, `state` int(11) NOT NULL, `added_by` int(10) unsigned NOT NULL, `approved_by` int(10) unsigned DEFAULT NULL, `created_at` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00', `updated_at` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00', PRIMARY KEY (`id`), UNIQUE KEY `project_tag_project_id_tag_id_unique` (`project_id`,`tag_id`), KEY `project_tag_tag_id_foreign` (`tag_id`), KEY `project_tag_added_by_foreign` (`added_by`), KEY `project_tag_approved_by_foreign` (`approved_by`), CONSTRAINT `project_tag_added_by_foreign` FOREIGN KEY (`added_by`) REFERENCES `users` (`id`) ON DELETE CASCADE, CONSTRAINT `project_tag_approved_by_foreign` FOREIGN KEY (`approved_by`) REFERENCES `users` (`id`) ON DELETE CASCADE, CONSTRAINT `project_tag_project_id_foreign` FOREIGN KEY (`project_id`) REFERENCES `projects` (`id`) ON DELETE CASCADE, CONSTRAINT `project_tag_tag_id_foreign` FOREIGN KEY (`tag_id`) REFERENCES `tags` (`id`) ON DELETE CASCADE ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; INSERT INTO `project_tag` (`id`, `project_id`, `tag_id`, `state`, `added_by`, `approved_by`, `created_at`, `updated_at`) VALUES (1, 1, 1, 1, 16, 8, '2015-06-17 23:51:00', '2015-06-17 23:51:00'), (2, 1, 2, 1, 11, 8, '2015-06-17 23:51:00', '2015-06-17 23:51:00'), (3, 2, 5, 1, 1, 8, '2015-06-17 23:51:00', '2015-06-17 23:51:00'), (4, 2, 1, 1, 15, 8, '2015-06-17 23:51:00', '2015-06-17 23:51:00'), (5, 2, 6, 1, 16, 8, '2015-06-17 23:51:00', '2015-06-17 23:51:00'), (6, 3, 8, 1, 20, 8, '2015-06-17 23:51:00', '2015-06-17 23:51:00'), (8, 4, 9, 1, 6, 8, '2015-06-17 23:51:00', '2015-06-17 23:51:00'), (9, 4, 10, 1, 15, 8, '2015-06-17 23:51:00', '2015-06-17 23:51:00'); DROP TABLE IF EXISTS `project_user`; CREATE TABLE `project_user` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `user_id` int(10) unsigned NOT NULL, `project_id` int(10) unsigned NOT NULL, `position` smallint(5) unsigned NOT NULL, `created_at` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00', `updated_at` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00', PRIMARY KEY (`id`), UNIQUE KEY `project_user_user_id_project_id_unique` (`user_id`,`project_id`), KEY `project_user_project_id_foreign` (`project_id`), CONSTRAINT `project_user_project_id_foreign` FOREIGN KEY (`project_id`) REFERENCES `projects` (`id`) ON DELETE CASCADE, CONSTRAINT `project_user_user_id_foreign` FOREIGN KEY (`user_id`) REFERENCES `users` (`id`) ON DELETE CASCADE ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; INSERT INTO `project_user` (`id`, `user_id`, `project_id`, `position`, `created_at`, `updated_at`) VALUES (1, 12, 1, 0, '0000-00-00 00:00:00', '0000-00-00 00:00:00'), (2, 2, 1, 0, '0000-00-00 00:00:00', '0000-00-00 00:00:00'), (3, 20, 1, 0, '0000-00-00 00:00:00', '0000-00-00 00:00:00'), (4, 19, 2, 0, '0000-00-00 00:00:00', '0000-00-00 00:00:00'), (5, 5, 2, 0, '0000-00-00 00:00:00', '0000-00-00 00:00:00'), (6, 9, 3, 0, '0000-00-00 00:00:00', '0000-00-00 00:00:00'), (7, 2, 3, 0, '0000-00-00 00:00:00', '0000-00-00 00:00:00'), (8, 2, 4, 0, '0000-00-00 00:00:00', '0000-00-00 00:00:00'), (9, 11, 4, 0, '0000-00-00 00:00:00', '0000-00-00 00:00:00'), (10, 6, 4, 0, '0000-00-00 00:00:00', '0000-00-00 00:00:00'); DROP TABLE IF EXISTS `tags`; CREATE TABLE `tags` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `tag` varchar(255) COLLATE utf8_unicode_ci NOT NULL, PRIMARY KEY (`id`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; INSERT INTO `tags` (`id`, `tag`) VALUES (1, 'Web'), (2, 'Engenharia de Software'), (3, 'Computação Móvel'), (4, 'Cloud'), (5, 'Segurança'), (6, 'Programação'), (7, 'Investigação'), (8, 'Licenciatura'), (9, 'Mestrado'), (10, 'Curso de Especialização Tecnológica'); DROP TABLE IF EXISTS `users`; CREATE TABLE `users` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT, `name` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `email` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `alt_email` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `password` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `institution_id` int(10) unsigned NOT NULL, `position` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `photo_url` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `profile_url` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `flags` smallint(6) NOT NULL, `role` int(10) unsigned NOT NULL, `remember_token` varchar(100) COLLATE utf8_unicode_ci DEFAULT NULL, `created_at` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00', `updated_at` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00', PRIMARY KEY (`id`), UNIQUE KEY `users_email_unique` (`email`), UNIQUE KEY `users_alt_email_unique` (`alt_email`), KEY `users_institution_id_foreign` (`institution_id`), CONSTRAINT `users_institution_id_foreign` FOREIGN KEY (`institution_id`) REFERENCES `institutions` (`id`) ON DELETE CASCADE ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; INSERT INTO `users` (`id`, `name`, `email`, `alt_email`, `password`, `institution_id`, `position`, `photo_url`, `profile_url`, `flags`, `role`, `remember_token`, `created_at`, `updated_at`) VALUES (1, '<NAME>', '<EMAIL>', NULL, '$2y$10$zYZD8j3Kg.jBKooQAv8.T.hoAX.q0.4wodrefwaKF/yNvJiYLxUGO', 2, 'evolve innovative webservices', 'ralmeida.jpg', 'http://batista.com/non-neque-pariatur-fuga', 1, 2, NULL, '2015-06-19 13:37:45', '2015-06-19 13:37:45'), (2, '<NAME>', '<EMAIL>', NULL, '$2y$10$ILcivw8LiNzSxWYXT44zmeCXuVlJrHZjQvyXYWaZpmF9Qq3TMjPDO', 13, 'streamline revolutionary systems', 'lara.torres.jpg', 'http://www.jesus.com/alias-numquam-excepturi-dignissimos-nesciunt-exercitationem-perferendis', 0, 2, NULL, '2015-06-17 23:50:44', '2015-06-17 23:50:44'), (3, '<NAME>', '<EMAIL>', NULL, '$2y$10$jd5QG07sNbGZ6rsB4OGUtezRnyThupzhHWiNEToqk/vjc4zksZqiS', 3, 'engage customized supply-chains', 'domingues.renata.jpg', 'http://marques.com/', 0, 2, NULL, '2015-06-17 23:50:45', '2015-06-17 23:50:45'), (5, '<NAME>', '<EMAIL>', NULL, '$2y$10$cqWIkYTDv85rWr3y.IGSIO9KHXIZoRcQD7H/QOni2zbMRQaCOCzIu', 1, 'maximize front-end systems', 'clara.miranda.jpg', 'http://www.magalhaes.com/quo-non-quia-doloribus-mollitia-aut-voluptatem-laborum.html', 0, 2, NULL, '2015-06-17 23:50:47', '2015-06-17 23:50:47'), (6, '<NAME>', '<EMAIL>', NULL, '$2y$10$ZgsPNMJwHFGlKryHsFf1u.Qfl5Ur7o1lO3DV4VKPu6052jXehjgO6', 4, 'harness open-source methodologies', 'margarida.henriques.jpg', 'http://www.vaz.biz/', 0, 1, NULL, '2015-06-17 23:50:48', '2015-06-17 23:50:48'), (7, '<NAME>', '<EMAIL>', NULL, '$2y$10$gJbTw9cG8pQClBmUoT4Zdu9k1SDX.xFDbQbsoiF/kJ3QzS8NiYh1K', 11, 'repurpose viral channels', 'iassuncao.jpg', 'http://magalhaes.com/soluta-voluptas-qui-id-esse-ut-nisi', 0, 2, NULL, '2015-06-17 23:50:49', '2015-06-17 23:50:49'), (8, '<NAME>', '<EMAIL>', '<EMAIL>', '$2y$10$0fCUzmXc7mq73CJemOTZyeyK0tdYLeKoF3rhbuNi0eVUpcroDhfEK', 14, 'morph virtual metrics', 'xavier90.jpg', 'http://www.pinheiro.info/et-quo-nisi-reiciendis-doloremque-ratione-inventore-qui', 0, 4, NULL, '2015-06-17 23:50:50', '2015-06-17 23:50:50'), (9, '<NAME>', 'let<EMAIL>', NULL, '$2y$10$oVwgExf.cVpri0xuy2V1KOg1U6FVEJhL1RwwwwtER2n/dcwPPNjYG', 16, 'revolutionize one-to-one networks', 'leticia77.jpg', 'http://www.ramos.com/inventore-eligendi-dolor-exercitationem-rerum-ratione', 0, 2, NULL, '2015-06-17 23:50:51', '2015-06-17 23:50:51'), (10, '<NAME>', '<EMAIL>', NULL, '$2y$10$Y/8nL55Gud62aK39xorXje1l1m6/v3Dg3tcG1vJyoydb.p.gccCVG', 11, 'strategize world-class initiatives', 'zvicente.jpg', 'http://www.marques.com/culpa-neque-beatae-ut-et.html', 0, 4, NULL, '2015-06-17 23:50:52', '2015-06-17 23:50:52'), (11, '<NAME> <NAME>', '<EMAIL>', '<EMAIL>', '$2y$10$ECw8dECNR5gBC1DIFiWKcOL8wcEh5pZQjWrwhSlnSYBOUr6KYmT5C', 14, 'extend distributed e-markets', 'jessica.oliveira.jpg', 'https://www.azevedo.net/repellendus-repudiandae-deserunt-error-omnis-molestiae-provident-hic', 0, 2, NULL, '2015-06-17 23:50:53', '2015-06-17 23:50:53'), (12, '<NAME>', '<EMAIL>', '<EMAIL>', '$2y$10$L4fIGiBNkw85l9Wm3DE/G.ioyYD8Z2SKQK4YAtkcbA3yFRg1P5JHS', 13, 'aggregate customized synergies', 'filipe.santos.jpg', 'http://faria.biz/aspernatur-qui-et-est-sed-sed-odio-rerum', 0, 1, NULL, '2015-06-17 23:50:54', '2015-06-17 23:50:54'), (13, '<NAME>', '<EMAIL>', NULL, '$2y$10$S2k4Npms0wshPQ7kPMJVmOaMHrkVxCMCpPb0NVy6hN4Nxh/eK6pMi', 13, 'scale cutting-edge solutions', 'lia14.jpg', 'http://www.nunes.com/autem-ut-consectetur-itaque-repudiandae-quae-in-non.html', 0, 1, NULL, '2015-06-17 23:50:55', '2015-06-17 23:50:55'), (14, '<NAME>', '<EMAIL>', '<EMAIL>', '$2y$10$1Z4uxzzVKE/5O3ISeDBSTuRIDMUSZUMlmH1lYp4LVx7nRcP1..Nx2', 6, 'recontextualize intuitive partnerships', 'nsantos.jpg', 'http://www.machado.com/', 0, 4, NULL, '2015-06-17 23:50:56', '2015-06-17 23:50:56'), (15, '<NAME>', '<EMAIL>', '<EMAIL>', '$2y$10$LBxIJ.bSz9/o8/5NcIMwtuS9QioAeyZ/YtpcPQrhDwUGRbIa0yygy', 16, 'seize value-added action-items', 'batista.cesar.jpg', 'https://www.freitas.biz/veritatis-et-quia-ad-nam-itaque', 0, 4, NULL, '2015-06-17 23:50:56', '2015-06-17 23:50:56'), (16, '<NAME>', '<EMAIL>', '<EMAIL>', '$2y$10$aWinrpiOJsmcvsQBwr8HX.GUpfQYc7FDlPATUOEHHK42Nao4Ds8Zu', 13, 'iterate proactive models', 'martim.magalhaes.jpg', 'http://pinho.com/consequuntur-quis-voluptatibus-laboriosam-quae', 0, 1, NULL, '2015-06-17 23:50:57', '2015-06-17 23:50:57'), (17, '<NAME>', '<EMAIL>', NULL, '$2y$10$KmTsN.Ln3XdBK1f3QH..1eI3niq5w1Gg6XfTM0BhAkAtvcoP.xpSu', 12, 'grow dynamic portals', 'joel.lopes.jpg', 'http://www.pires.com/', 0, 4, NULL, '2015-06-17 23:50:58', '2015-06-17 23:50:58'), (18, '<NAME>', '<EMAIL>', '<EMAIL>', '$2y$10$p7cCWCH5wvK.PjUgcCbLjuQh82jnngq5EWohR4jxeWZfS6lqLDoY6', 8, 'drive sticky interfaces', 'alexandra67.jpg', 'http://reis.biz/tenetur-earum-similique-et-ut-doloribus', 0, 2, NULL, '2015-06-17 23:50:59', '2015-06-17 23:50:59'), (19, '<NAME>', '<EMAIL>', NULL, '$2y$10$x1c0Jsl6Til6PbXvEyYU..5myFVIzACUvcX.mvqmfVfSM/Ayfzno2', 11, 'exploit viral technologies', 'guerreiro.vasco.jpg', 'http://www.matias.com/architecto-sint-vel-quam-doloribus-autem', 0, 2, NULL, '2015-06-17 23:51:00', '2015-06-17 23:51:00'), (20, '<NAME>', '<EMAIL>', NULL, '$2y$10$mqBtbhw5NyedyvA5AHMNluANzCUTVEuFxnOpvyG.GFT7hR5ULMCiW', 7, 'revolutionize robust supply-chains', 'cesar60.jpg', 'http://sa.net/non-soluta-ut-iste-in-maiores-rerum', 0, 1, NULL, '2015-06-17 23:51:00', '2015-06-17 23:51:00'); -- 2015-06-22 13:46:07

INSERT INTO department (department_name) VALUES ('Human Resources'), ('Sales'), ('Marketing'), ('Information Tech'), ('Legal'); INSERT INTO role (title, salary, department_id) VALUES('Account Executive', 100000, 1), ('Sr. Account Executive', 152000, 1), ('Sales Director', 223000, 1), ('HR Coordinator', 65000, 2), ('HR Generalist', 25000, 2), ('HR Director', 112000, 2), ('Jr. Developer', 91000, 3), ('Sr. Developer', 123400, 3), ('Programming Director', 227600, 3), ('IT Project Manager', 912000, 4), ('IT Project Director', 111000, 4), ('Chief Executive Officer', 342000, 5), ('Chief Operating Officer', 222300, 5), ('Chief Financial Officer', 252000, 5); INSERT INTO employee (first_name, last_name, role_id, manager_id) VALUES ('Felipe', 'Lisardo', 12, NULL), ('Wally', 'Neximan', 13, 1), ('Lunga', 'linga', 14, 1), ('Falty', 'Impbles', 3, 2), ('Lurking', 'Monsters', 9, 2), ('Eliste', 'Inglebler', 11, 2), ('Lifesabitch', 'Thenyoudie', 6, 2), ('Inflatable', 'Dreams', 1, 4), ('Featch', 'Darsy', 1, 4), ('Alfredo', 'Diez', 2, 4), ('Lingering', 'Code', 4, 7), ('Shame', 'Onyou', 5, 7), ('Butcher', 'Table', 5, 7), ('Insta', 'Graham', 7, 5), ('Flipping', 'Cool', 8, 5), ('Reginal', 'Lewinsky', 10, 6), ('Loopy', 'Absolute', 10, 6);

<reponame>aurelien22/equiKenotte<gh_stars>0 INSERT INTO mydb.dentistes(nom, prenom, adresse, codePostal, ville, telephone, email, siret, login, mdp) VALUES ('serret', 'leslie', '39 rue ange de guernisac', '29600', 'morlaix', '0681626347', '<EMAIL>', '83208269700026', 'lserret', 'password'); INSERT INTO mydb.dentistes(nom, prenom, adresse, codePostal, ville, telephone, email, siret, login, mdp) VALUES ('lecollinet', 'patrick', '2 rue jean mermoz', '35400', 'saint-malo', '0681626041', '<EMAIL>', '38238203400041', 'plecollinet', 'password'); select * from mydb.dentistes; INSERT INTO mydb.clients(nom, prenom, adresse, codePostal, ville, dentistes_idDentiste) VALUES ('pellan', 'frederique', '3 la ville men', '22240', 'frehel', 1); INSERT INTO mydb.clients(nom, prenom, adresse, codePostal, ville, dentistes_idDentiste) VALUES ('<NAME>', 'nadine', '2 lepine', '22240', 'frehel', 1); INSERT INTO mydb.clients(nom, prenom, adresse, codePostal, ville, dentistes_idDentiste) VALUES ('dincuff', 'aurelien', '5 rue de claire vue', '22240', 'frehel', 2); INSERT INTO mydb.clients(nom, prenom, adresse, codePostal, ville, dentistes_idDentiste) VALUES ('bouyou', 'jennifer', '5 rue de claire vue', '22240', 'frehel', 1); INSERT INTO mydb.clients(nom, prenom, adresse, codePostal, ville, dentistes_idDentiste) VALUES ('dincuff', 'aliya', '5 rue de claire vue', '22240', 'frehel', 2); select * from mydb.clients; INSERT INTO mydb.chevaux(nom, numeroSire, anneeNaissance, idClient) VALUES ('<NAME>', '13389321P', 2013, 1); INSERT INTO mydb.chevaux(nom, numeroSire, anneeNaissance, idClient) VALUES ('<NAME>', '15195278S', 2015, 2); INSERT INTO mydb.chevaux(nom, numeroSire, anneeNaissance, idClient) VALUES ('<NAME>', '19309845M', 2019, 3); INSERT INTO mydb.chevaux(nom, numeroSire, anneeNaissance, idClient) VALUES ('<NAME>', '18107917F', 2018, 3); INSERT INTO mydb.chevaux(nom, numeroSire, anneeNaissance, idClient) VALUES ('<NAME>', '19337248B', 2019, 4); INSERT INTO mydb.chevaux(nom, numeroSire, anneeNaissance, idClient) VALUES ('<NAME>', '18198908C', 2018, 4); INSERT INTO mydb.chevaux(nom, numeroSire, anneeNaissance, idClient) VALUES ('fanfan', '52386057H', 2005, 5); select * from mydb.chevaux; select * from mydb.chevaux where idClient = 4; select * from mydb.clients cl inner join mydb.chevaux ch ON ch.idClient = cl.idClient where cl.nom like 'dincuff' AND cl.prenom LIKE 'aurelien'; INSERT INTO mydb.tauxTva(taux) VALUES (5.5); INSERT INTO mydb.tauxTva(taux) VALUES (10); INSERT INTO mydb.tauxTva(taux) VALUES (20); select * from mydb.tauxTva; alter table mydb.tauxTva modify taux DECIMAL(3,1); INSERT INTO mydb.prestations(designation, prixHt, idTauxTva ) VALUES ('Consultation et nivellement', '60', 3); INSERT INTO mydb.prestations(designation, prixHt, idTauxTva ) VALUES ('Extraction des dents de loup', '30', 3); INSERT INTO mydb.prestations(designation, prixHt, idTauxTva ) VALUES ('Tranquilisation', '10', 3); INSERT INTO mydb.prestations(designation, prixHt, idTauxTva ) VALUES ('Déplacement kilométrique', '0.5', 3); select * from mydb.prestations;

<filename>database/sql/20210924.sql create table users( id bigint auto_increment primary key, name varchar(255), email varchar(255) unique, password varchar(255) ); create table comments( id bigint auto_increment primary key, comment varchar(255), user_id bigint, foreign key ( user_id ) references users(id) on delete cascade ); create table book_shelves( id bigint auto_increment primary key, title varchar(255), user_id bigint, foreign key ( user_id ) references users(id) on delete cascade ); create table novels( id bigint auto_increment primary key, title varchar(255), user_id bigint, foreign key ( user_id ) references users(id) on delete cascade ); create table chapters( id bigint auto_increment primary key, title varchar(255), novel_id bigint, foreign key ( novel_id ) references novels(id) on delete cascade ); create table episodes( id bigint auto_increment primary key, title varchar(255), chapter_id bigint, foreign key ( chapter_id ) references chapters(id) on delete cascade, novel text ); create table book_shelf_novel_links ( id bigint auto_increment primary key, book_shelf_id bigint, foreign key ( book_shelf_id ) references book_shelves( id ) on delete cascade, novel_id bigint, foreign key ( novel_id ) references novels( id ) on delete cascade ); create table bookmarks( id bigint auto_increment primary key, last_read_episode_id bigint, foreign key ( last_read_episode_id ) references episodes(id) on delete cascade, user_id bigint, foreign key ( user_id ) references users(id) on delete cascade ); create table reviews ( id bigint auto_increment primary key, user_id bigint, foreign key ( user_id ) references users( id ) on delete cascade, novel_id bigint, foreign key ( novel_id ) references novels( id ) on delete cascade, rating int ); create table subscribes ( id bigint auto_increment primary key, subscriber_id bigint, foreign key ( subscriber_id ) references users( id ) on delete cascade, subscribee_id bigint, foreign key ( subscribee_id ) references users( id ) on delete cascade );

<reponame>douglasrg1/Store create procedure spReturnProduct @Id uniqueidentifier as select [Title], [Description], [Image], [Price], [QuantityOnHand] from [Product] where [Id] = @id

-- Create a new function called 'FN_TrimWord' in schema 'dbo' -- Drop the function if it already exists IF EXISTS ( SELECT * FROM INFORMATION_SCHEMA.ROUTINES WHERE SPECIFIC_SCHEMA = N'dbo' AND SPECIFIC_NAME = N'FN_TrimWord' ) DROP FUNCTION dbo.[FN_TrimWord] GO -- Create the function in the specified schema CREATE FUNCTION dbo.[FN_TrimWord](@word NVARCHAR(4000)) -- determine the return type RETURNS NVARCHAR(4000) AS -- trims a word and returns it BEGIN SET @word = RTRIM(LTRIM(@word)) RETURN @word END GO -- example to execute the function we just created SELECT dbo.[FN_TrimWord](' This is a junky text. ') SELECT (' This is a junky text. ') GO

<filename>presensi.sql -- phpMyAdmin SQL Dump -- version 5.0.2 -- https://www.phpmyadmin.net/ -- -- Host: 127.0.0.1 -- Waktu pembuatan: 12 Sep 2020 pada 23.15 -- Versi server: 10.4.11-MariaDB -- Versi PHP: 7.4.5 SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO"; START TRANSACTION; SET time_zone = "+00:00"; /*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */; /*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */; /*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */; /*!40101 SET NAMES utf8mb4 */; -- -- Database: `presensi` -- -- -------------------------------------------------------- -- -- Struktur dari tabel `admin` -- CREATE TABLE `admin` ( `id_admin` int(11) NOT NULL, `nama` text NOT NULL, `email` varchar(50) NOT NULL, `password` varchar(50) NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4; -- -- Dumping data untuk tabel `admin` -- INSERT INTO `admin` (`id_admin`, `nama`, `email`, `password`) VALUES (1, '<NAME>', '<EMAIL>', '<PASSWORD>'); -- -------------------------------------------------------- -- -- Struktur dari tabel `presensi` -- CREATE TABLE `presensi` ( `id_presensi` int(11) NOT NULL, `nama` text NOT NULL, `nis` bigint(20) NOT NULL, `kelas` varchar(2) NOT NULL, `tanggal` date NOT NULL, `keterangan` varchar(10) NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4; -- -- Indexes for dumped tables -- -- -- Indeks untuk tabel `admin` -- ALTER TABLE `admin` ADD PRIMARY KEY (`id_admin`); -- -- Indeks untuk tabel `presensi` -- ALTER TABLE `presensi` ADD PRIMARY KEY (`id_presensi`); -- -- AUTO_INCREMENT untuk tabel yang dibuang -- -- -- AUTO_INCREMENT untuk tabel `admin` -- ALTER TABLE `admin` MODIFY `id_admin` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2; -- -- AUTO_INCREMENT untuk tabel `presensi` -- ALTER TABLE `presensi` MODIFY `id_presensi` int(11) NOT NULL AUTO_INCREMENT; COMMIT; /*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */; /*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */; /*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;

DROP DATABASE IF EXISTS kiosks; CREATE DATABASE kiosks; \c kiosks CREATE TABLE kiosks ( id SERIAL PRIMARY KEY, kiosk_id VARCHAR(20), mall VARCHAR(40), city VARCHAR(40), state VARCHAR(15), zip INT, batteries_on_loan INT, batteries_to_replace INT, battery_count INT, online BOOLEAN )

<filename>ic_pic.sql set hive.strict.checks.large.query=false; set hive.mapred.mode=nonstrict; CREATE TABLE dm_ic.tmp_ic_goods_with_teamtype_20200806_003 AS SELECT igd.pictures AS picture, igd.kdt_id AS kdt_id team_dim.team_type AS team_type, get_json_object(regexp_replace(igd.pictures,'^\\[|\\]$','') , '$.url') AS url, igv.created_time AS created_time, igv.update_time AS update_time, igv.alias AS alias FROM ods.ic_goods_description_all as igd LEFT JOIN ods.ic_goods_v2 as igv ON igd.kdt_id = igv.kdt_id AND igd.item_id = igv.id LEFT JOIN dw.dim_team as team_dim ON igd.kdt_id = team_dim.kdt_id WHERE -- get_json_object(igd.pictures, '$.url') not like 'http%' get_json_object(regexp_replace(igd.pictures,'^\\[|\\]$','') , '$.url') not like 'http%' AND igv.is_display = 1 ORDER BY created_time desc ; SELECT team_type, count(*) as total_num FROM dm_ic.ic_goods_with_teamtype_20200806_XXX GROUP BY team_type ;

CREATE TABLE `activity_red_packets` ( `id` int(10) UNSIGNED NOT NULL AUTO_INCREMENT , `title` varchar(100) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL DEFAULT '' COMMENT '红包活动标题' , `trigger` tinyint(1) NOT NULL DEFAULT 0 COMMENT '红包触发类型,0为大厅（红包雨），1为下注时（普通红包）' , `type` tinyint(1) UNSIGNED NOT NULL DEFAULT 0 COMMENT '红包类型，0为红包雨，1为普通红包，默认为红包雨' , `user_max` tinyint(3) UNSIGNED NOT NULL DEFAULT 1 COMMENT '单个会员最大能在该活动抢到的红包数' , `total_amount` decimal(10,2) UNSIGNED NOT NULL DEFAULT 0.00 COMMENT '红包的金额（只能为整数金额）' , `get_amount` decimal(10,2) UNSIGNED NOT NULL DEFAULT 0.00 COMMENT '已经领取的金额' , `total_number` int(10) UNSIGNED NOT NULL DEFAULT 0 COMMENT '总的红包个数' , `get_number` int(10) UNSIGNED NOT NULL DEFAULT 0 COMMENT '已经领取的红包个数' , `total_user` int(10) UNSIGNED NOT NULL DEFAULT 0 COMMENT '领取过该红包的会员数' , `start_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00' COMMENT '红包活动开始时间' , `end_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00' COMMENT '红包活动结束时间' , `status` tinyint(1) UNSIGNED NOT NULL DEFAULT 1 COMMENT '红包状态，0为已结束，1为正常，默认为1' , `create_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00' COMMENT '创建时间' , `last_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00' COMMENT '最后修改时间' , `requirements_type` tinyint(1) NOT NULL DEFAULT 0 COMMENT '抢红包条件 1累计下注总额类型 2 当天下注总额' , `user_largest` decimal(10,2) NOT NULL DEFAULT 0.00 COMMENT '大额用户的额度' , `requirements_amount` decimal(10,2) NOT NULL DEFAULT 0.00 COMMENT '抢红包条件的额度 单位/元' , PRIMARY KEY (`id`), INDEX `date_time` (`start_date`, `end_date`) USING BTREE ) ENGINE=InnoDB DEFAULT CHARACTER SET=utf8 COLLATE=utf8_general_ci ROW_FORMAT=Dynamic ; CREATE TABLE `bak__alarm_push_log` ( `id` int(10) NOT NULL , `rule_tag` varchar(20) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL DEFAULT '' COMMENT '具体触发的监控规则标识符（与监控规则表tag字段对应）' , `pass` tinyint(1) UNSIGNED NOT NULL DEFAULT 0 COMMENT '所属平台，0为总平台，1为厅主系统' , `user_name` varchar(30) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL DEFAULT '' COMMENT '用户登录名称（监控对象）' , `hall_id` int(10) UNSIGNED NOT NULL DEFAULT 0 COMMENT '被监控用户所属厅主ID' , `hall_name` varchar(30) CHARACTER SET latin1 COLLATE latin1_swedish_ci NOT NULL DEFAULT '' COMMENT '被监控用户所属厅主登录名' , `agent_id` int(10) UNSIGNED NOT NULL DEFAULT 0 COMMENT '被监控用户所属代理商ID' , `agent_name` varchar(30) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL DEFAULT '' COMMENT '被监控用户所属代理商登录名' , `remark` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL DEFAULT '' COMMENT '报警备注' , `create_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00' COMMENT '报警时间（创建时间）' ) ENGINE=InnoDB DEFAULT CHARACTER SET=latin1 COLLATE=latin1_swedish_ci ROW_FORMAT=Dynamic ; CREATE TABLE `bak__api_login_log` ( `id` int(11) NULL DEFAULT NULL , `agent` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL COMMENT '代理名称' , `postData` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL COMMENT '请求的参数' , `apiName` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL COMMENT '请求接口名称' , `ip_info` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL COMMENT '代理请求的IP ' , `log_type` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL COMMENT '登录类型 login 登录 api 接口请求' , `code` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL COMMENT '返回状态码 0 正常' , `text` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL COMMENT '返回结果字段 Success' , `result` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL COMMENT 'result 请求结果数据' , `start_time` datetime NULL DEFAULT NULL ON UPDATE CURRENT_TIMESTAMP COMMENT '开始时间' , `end_time` datetime NULL DEFAULT NULL ON UPDATE CURRENT_TIMESTAMP COMMENT '结束时间' ) ENGINE=InnoDB DEFAULT CHARACTER SET=utf8 COLLATE=utf8_general_ci ROW_FORMAT=Dynamic ; CREATE TABLE `bak__api_statistics_log` ( `id` int(11) NULL DEFAULT NULL , `apiName` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL COMMENT '联调接口名称' , `agent` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL COMMENT '联调厅主' , `status` tinyint(255) NULL DEFAULT NULL COMMENT '是否联调 默认 0 1 联调' , `succeds` int(255) NULL DEFAULT NULL COMMENT '成功次数 默认 0' , `sum` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL COMMENT '联调总次数 默认 0' ) ENGINE=InnoDB DEFAULT CHARACTER SET=utf8 COLLATE=utf8_general_ci ROW_FORMAT=Dynamic ; ALTER TABLE `bak__exception_cash_log` MODIFY COLUMN `bet_time` datetime NOT NULL DEFAULT '0000-00-00 00:00:00' COMMENT '下注时间' AFTER `user_money`; ALTER TABLE `bak__exception_cash_log` MODIFY COLUMN `add_time` datetime NOT NULL DEFAULT '0000-00-00 00:00:00' COMMENT '添加时间' AFTER `action_passivity`; CREATE TABLE `bak__packets_log` ( `id` int(10) UNSIGNED NOT NULL AUTO_INCREMENT , `packets_id` int(10) UNSIGNED NOT NULL DEFAULT 0 COMMENT '红包活动ID' , `user_id` int(10) NOT NULL DEFAULT 0 COMMENT '会员id' , `user_name` varchar(50) CHARACTER SET latin1 COLLATE latin1_swedish_ci NOT NULL DEFAULT '' COMMENT '会员登录名' , `hall_name` varchar(50) CHARACTER SET latin1 COLLATE latin1_swedish_ci NOT NULL DEFAULT '' COMMENT '会员所属厅主登录名' , `hall_id` int(10) NOT NULL DEFAULT 0 COMMENT '会员所属厅主ID' , `agent_name` varchar(50) CHARACTER SET latin1 COLLATE latin1_swedish_ci NOT NULL DEFAULT '' COMMENT '会员所属代理商登录名' , `agent_id` int(10) NOT NULL DEFAULT 0 COMMENT '会员所属代理商ID' , `packets_amount` decimal(10,2) NOT NULL DEFAULT 0.00 COMMENT '抢到的红包金额' , `get_number` tinyint(1) NOT NULL DEFAULT 1 COMMENT '红包个数，恒定值为1，为了数据统计方便而用' , `create_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00' COMMENT '创建时间（即抢到红包的时间）' , PRIMARY KEY (`id`) ) ENGINE=InnoDB DEFAULT CHARACTER SET=utf8 COLLATE=utf8_general_ci ROW_FORMAT=Dynamic ; CREATE TABLE `bak__system_log` ( `id` int(11) NULL DEFAULT NULL , `action_name` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL COMMENT '操作的项目' , `user_id` int(11) NULL DEFAULT NULL COMMENT '操作者ID' , `action_user` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL COMMENT '操作者' , `action_desc` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL COMMENT '操作具体内容' , `action_passivity` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL COMMENT '操作对象' , `action_date` datetime NULL DEFAULT NULL ON UPDATE CURRENT_TIMESTAMP COMMENT '操作日期' , `ip_info` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL COMMENT 'IP 操作者IP' ) ENGINE=InnoDB DEFAULT CHARACTER SET=utf8 COLLATE=utf8_general_ci ROW_FORMAT=Dynamic ; CREATE TABLE `bak__trigger_log` ( `id` int(10) UNSIGNED NOT NULL AUTO_INCREMENT , `user_id` int(10) NOT NULL DEFAULT 0 COMMENT '用户id' , `user_name` varchar(50) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL DEFAULT '' COMMENT '用户登录名称' , `hall_name` varchar(20) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL DEFAULT '' COMMENT '用户所属厅主登录名' , `hall_id` int(10) UNSIGNED NOT NULL DEFAULT 0 COMMENT '用户所属厅主ID' , `agent_name` varchar(20) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL DEFAULT '' COMMENT '代理商名称' , `agent_id` int(10) NOT NULL DEFAULT 0 COMMENT '代理商id' , `rule_tag` varchar(20) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL DEFAULT '' COMMENT '具体触发的监控规则标识符（与监控规则表tag字段对应）' , `user_real_value` varchar(50) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL DEFAULT '' COMMENT '用户真实的监控数据值' , `rule_value` varchar(50) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL DEFAULT '' COMMENT '具体监控项的阀值' , `number` int(10) UNSIGNED NOT NULL DEFAULT 0 COMMENT '触发规则的次数' , `pass` tinyint(1) UNSIGNED NOT NULL DEFAULT 0 COMMENT '监控记录类型：0为总平台，1为厅主' , `last_trigger_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00' COMMENT '最后触发事件' , `remark` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL DEFAULT '' COMMENT '报警备注' , `begin_balance` decimal(10,2) NOT NULL DEFAULT 0.00 COMMENT '用户初始余额（高盈利监控）' , `monitor_balance` decimal(10,2) NOT NULL DEFAULT 0.00 COMMENT '监控报警时用户余额（高盈利监控）' , `create_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00' COMMENT '记录创建时间' , `ip_str` char(20) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL DEFAULT '0.0.0.0' COMMENT '玩家IP地址' , `is_send_email` tinyint(1) NOT NULL DEFAULT 0 COMMENT '是否已发送邮件，1为已发送' , PRIMARY KEY (`id`) ) ENGINE=InnoDB DEFAULT CHARACTER SET=utf8 COLLATE=utf8_general_ci ROW_FORMAT=Dynamic ; ALTER TABLE `bak__user_chart_info` ADD COLUMN `agent_code` varchar(32) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL DEFAULT '' COMMENT '玩家账号代理商前缀' AFTER `user_name`; CREATE TABLE `dealer_info` ( `id` int(10) UNSIGNED NOT NULL AUTO_INCREMENT , `dealer` varchar(20) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL DEFAULT '' COMMENT '荷官ID(荷官编码)' , `dealer_name` varchar(30) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL DEFAULT '' COMMENT '荷官名称' , `dealer_img` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT '' COMMENT '荷官图片' , `last_update` datetime NOT NULL DEFAULT '0000-00-00 00:00:00' COMMENT '最后更新时间' , PRIMARY KEY (`id`) ) ENGINE=InnoDB DEFAULT CHARACTER SET=utf8 COLLATE=utf8_general_ci ROW_FORMAT=Dynamic ; ALTER TABLE `game_platform_activity` MODIFY COLUMN `update_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00' COMMENT '修改时间' AFTER `add_date`; ALTER TABLE `game_platform_banner` MODIFY COLUMN `label` tinyint(1) UNSIGNED NOT NULL DEFAULT 0 COMMENT '所属平台,0为视讯PC，1为视讯H5，2为视讯APP' AFTER `play_type`; ALTER TABLE `game_platform_banner` MODIFY COLUMN `update_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00' COMMENT '修改时间' AFTER `add_date`; ALTER TABLE `game_platform_cost` MODIFY COLUMN `update_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00' COMMENT '修改时间' AFTER `add_user`; ALTER TABLE `game_platform_delivery` MODIFY COLUMN `add_time` datetime NOT NULL DEFAULT '0000-00-00 00:00:00' COMMENT '添加时间' AFTER `add_user`; ALTER TABLE `game_platform_delivery` MODIFY COLUMN `update_time` datetime NOT NULL DEFAULT '0000-00-00 00:00:00' COMMENT '修改时间' AFTER `add_time`; ALTER TABLE `game_platform_logo` MODIFY COLUMN `label` tinyint(1) NOT NULL DEFAULT 0 COMMENT '所属平台,0为视讯PC，1为视讯H5，2为视讯APP' AFTER `title`; ALTER TABLE `game_platform_logo` MODIFY COLUMN `update_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00' COMMENT '修改时间' AFTER `add_date`; ALTER TABLE `game_platform_scale` MODIFY COLUMN `add_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00' COMMENT '添加时间' AFTER `add_user`; ALTER TABLE `game_template_images` MODIFY COLUMN `add_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00' COMMENT '添加时间' AFTER `img`; CREATE TABLE `hall_message` ( `id` int(10) UNSIGNED NOT NULL AUTO_INCREMENT , `message` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL DEFAULT '' COMMENT '厅主公告内容' , `start_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00' COMMENT '公告开始时间' , `end_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00' COMMENT '公告结束时间' , `create_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00' COMMENT '创建时间' , PRIMARY KEY (`id`), INDEX `start_date` (`start_date`, `end_date`) USING BTREE ) ENGINE=InnoDB DEFAULT CHARACTER SET=utf8 COLLATE=utf8_general_ci ROW_FORMAT=Dynamic ; ALTER TABLE `lb_agent_user` ADD COLUMN `connect_mode` tinyint(1) NOT NULL DEFAULT 0 COMMENT '厅主对接方式，0为额度转换，1为共享钱包，默认为0' AFTER `notify_url`; ALTER TABLE `lb_agent_user` ADD COLUMN `show_delivery` tinyint(1) NOT NULL DEFAULT 1 COMMENT '针对厅主，是否显示厅主交收统计 0：不显示，1：显示' AFTER `connect_mode`; ALTER TABLE `lb_user` ADD COLUMN `grand_total_money` decimal(20,2) NOT NULL DEFAULT 0.00 COMMENT '充值扣款累计余额' AFTER `money`; CREATE TABLE `statis_both_add_gold` ( `id` int(11) UNSIGNED NOT NULL AUTO_INCREMENT , `user_id` int(11) UNSIGNED NOT NULL DEFAULT 0 , `user_name` varchar(50) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL COMMENT '用户名' , `both_add_times` int(11) UNSIGNED NOT NULL DEFAULT 0 COMMENT '总对下次数' , `no_both_add_times` int(11) UNSIGNED NOT NULL DEFAULT 0 COMMENT '非对下次数' , `con_both_add_times` int(11) UNSIGNED NOT NULL DEFAULT 0 COMMENT '连续对下次数' , `con_both_add_times_cur` int(11) NOT NULL DEFAULT 0 COMMENT '当前连续对下次数，临时值' , `add_date` date NOT NULL DEFAULT '0000-00-00' COMMENT '当天日期' , `ip_str` char(20) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL COMMENT '玩家IP地址（目前正式环境无法获取）' , `hall_id` int(11) UNSIGNED NOT NULL DEFAULT 0 COMMENT '厅主ID' , `hall_name` varchar(50) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL DEFAULT '\"\"' COMMENT '厅主名称' , `agent_id` int(11) UNSIGNED NOT NULL DEFAULT 0 COMMENT '代理商ID' , `agent_name` varchar(50) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL DEFAULT '\"\"' COMMENT '代理商名称' , `update_time` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP COMMENT '最后更新时间' , PRIMARY KEY (`id`), UNIQUE INDEX `index_date` (`user_id`, `add_date`) USING BTREE ) ENGINE=InnoDB DEFAULT CHARACTER SET=utf8 COLLATE=utf8_general_ci ROW_FORMAT=Dynamic ; ALTER TABLE `statis_cash_player` ADD COLUMN `totalwinnums` int(11) NULL DEFAULT 0 COMMENT '当天总共胜多少局' AFTER `win_count_cur`; ALTER TABLE `statis_cash_player` ADD COLUMN `totallosenums` int(11) NULL DEFAULT 0 COMMENT '当天总共输多少局' AFTER `totalwinnums`; CREATE TABLE `sys_alarm_account` ( `id` int(11) UNSIGNED NOT NULL AUTO_INCREMENT , `hall_id` int(11) NOT NULL DEFAULT 0 COMMENT '所属厅主id，默认为0，0时代表为总平台' , `mobile` varchar(15) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL DEFAULT '' COMMENT '手机号码' , `email` varchar(30) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL DEFAULT '' COMMENT '报警邮箱' , `last_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00' COMMENT '最后修改时间' , PRIMARY KEY (`id`) ) ENGINE=InnoDB DEFAULT CHARACTER SET=utf8 COLLATE=utf8_general_ci ROW_FORMAT=Dynamic ; ALTER TABLE `system_log` MODIFY COLUMN `action_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00' COMMENT '操作时间' AFTER `action_user`; ALTER TABLE `system_maintain` MODIFY COLUMN `start_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00' COMMENT '系统维护开始时间' AFTER `hall_id`; ALTER TABLE `system_message` MODIFY COLUMN `type` tinyint(1) UNSIGNED NOT NULL DEFAULT 1 COMMENT '公告发布的平台，0为所有平台，1为视讯PC，2为视讯H5，3为视讯APP。默认为0' AFTER `update_date`; ALTER TABLE `agent_system_menus` MODIFY COLUMN `update_date` datetime NULL DEFAULT NULL AFTER `menu_code`; INSERT INTO `sys_monitor` VALUES ('1', '0', '刷水', 'M001', '0'); INSERT INTO `sys_monitor` VALUES ('2', '0', '大额投注', 'M002', '0'); INSERT INTO `sys_monitor` VALUES ('3', '0', '高盈利', 'M003', '1'); INSERT INTO `sys_monitor` VALUES ('4', '0', '连胜次数', 'M004', '0'); INSERT INTO `sys_monitor` VALUES ('5', '0', '胜率', 'M005', '0'); INSERT INTO `sys_monitor_rule` VALUES ('1', '0', 'M002', 'bet', '6', '2017-11-02 22:07:34'); INSERT INTO `sys_monitor_rule` VALUES ('2', '0', 'M002', 'gap', '1', '2017-11-02 22:07:28'); INSERT INTO `sys_monitor_rule` VALUES ('3', '0', 'M003', 'profit', '101', '2017-11-01 05:59:55'); INSERT INTO `sys_monitor_rule` VALUES ('4', '0', 'M003', 'gap', '50', '2017-10-18 04:11:10'); INSERT INTO `sys_monitor_rule` VALUES ('5', '0', 'M004', 'win_streak', '1000', '2017-10-26 21:56:04'); INSERT INTO `sys_monitor_rule` VALUES ('6', '0', 'M004', 'gap', '5', '2017-10-18 04:11:08'); INSERT INTO `sys_monitor_rule` VALUES ('7', '0', 'M005', 'victory_ratio', '200', '2017-10-26 21:56:07'); INSERT INTO `sys_monitor_rule` VALUES ('8', '0', 'M005', 'gap', '5', '2017-10-18 04:11:11'); ALTER TABLE `game_platform_delivery_info` ADD COLUMN `red_packets` decimal(10,2) UNSIGNED NULL DEFAULT 0.00 COMMENT '红包金额' AFTER `local_end_date`; CREATE TABLE `game_host` ( `id` int(10) unsigned NOT NULL AUTO_INCREMENT COMMENT '游戏入口域名管理Id', `host_type` varchar(255) NOT NULL DEFAULT '0' COMMENT '游戏域名类型 1 pc游戏域名 2 h5游戏域名 ', `host_url` varchar(255) NOT NULL DEFAULT '' COMMENT '游戏域名', `status` tinyint(4) DEFAULT '0' COMMENT '是否启动 0 不启用 1 启用', `add_time` datetime DEFAULT '0000-00-00 00:00:00' COMMENT '创建时间', `update_time` datetime DEFAULT '0000-00-00 00:00:00' COMMENT '修改时间', PRIMARY KEY (`id`) ) ENGINE=InnoDB AUTO_INCREMENT=14 DEFAULT CHARSET=utf8 COMMENT='游戏入口域名管理表'; ALTER TABLE `lb_agent_user` ADD COLUMN `connect_mode` tinyint(1) NOT NULL DEFAULT 0 COMMENT '厅主对接方式，0为额度转换，1为共享钱包，默认为0' AFTER `notify_url`; CREATE TABLE `statis_shuashui` ( `id` int(11) unsigned NOT NULL AUTO_INCREMENT, `ip_str` char(20) DEFAULT NULL COMMENT '玩家IP地址（目前正式环境无法获取）', `user_name` varchar(50) DEFAULT NULL COMMENT '用户名', `both_add_times` int(11) unsigned NOT NULL DEFAULT '0' COMMENT '总对下次数', `no_both_add_times` int(11) unsigned NOT NULL DEFAULT '0' COMMENT '非对下次数', `con_both_add_times` int(11) unsigned NOT NULL DEFAULT '0' COMMENT '连续对下次数', `con_both_add_times_cur` int(11) NOT NULL DEFAULT '0' COMMENT '当前连续对下次数，临时值', `add_date` date NOT NULL DEFAULT '0000-00-00' COMMENT '当天日期', `update_time` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP COMMENT '最后更新时间', PRIMARY KEY (`id`), UNIQUE KEY `index_ip_date` (`ip_str`,`add_date`) ) ENGINE=InnoDB AUTO_INCREMENT=0 DEFAULT CHARSET=utf8 COMMENT='每天IP对下记录表（保存1周数据）';

USE AdventureWorks2008R2; GO SELECT p.Name AS ProductName, NonDiscountSales = (OrderQty * UnitPrice), Discounts = ((OrderQty * UnitPrice) * UnitPriceDiscount) FROM Production.Product AS p INNER JOIN Sales.SalesOrderDetail AS sod ON p.ProductID = sod.ProductID ORDER BY ProductName DESC; GO

<filename>data/open-source/extracted_sql/OCA_connector.sql SELECT id FROM res_users WHERE login=%s update queue_job set state=pending where state in (started, enqueued) UPDATE queue_job SET state=%s WHERE uuid=%s UPDATE queue_job SET state=%s WHERE uuid=%s SELECT 1 FROM ir_module_module

<filename>type/type.sql GRANT CREATE,ALTER,SELECT,INSERT,UPDATE,DELETE ON example.* TO example@localhost IDENTIFIED BY 'example'; DROP TABLE IF EXISTS nodes; CREATE TABLE nodes ( id int(10) unsigned NOT NULL default '0', prototype varchar(255) default NULL, name varchar(255) default NULL, visible tinyint(3) unsigned default NULL, position tinyint(3) unsigned default NULL, parent_id int(10) unsigned default NULL, creator_id int(11) default '0', creation_date datetime default NULL, modifier_id int(11) default '0', modification_date datetime default NULL, related_ids varchar(255) default NULL, text text, PRIMARY KEY (id), KEY name (name,text(64)), FULLTEXT KEY search (name,text) ) ENGINE=MyISAM DEFAULT CHARSET=utf8; INSERT INTO nodes VALUES (0,'Root','Welcome',1,0,NULL,0,'2007-11-06 15:08:38',0,'2007-11-08 02:51:34',NULL,'Welcome to this simple demonstration.'),(2,'Page','Three',1,2,0,NULL,'2007-11-07 23:26:26',0,'2007-11-08 02:52:27',NULL,'Same here really...'),(3,'Page','One',1,0,0,NULL,'2007-11-07 23:26:08',0,'2007-11-08 02:51:58',NULL,'Guys, I\'m mighty!'),(9,'Page','Two',1,1,0,0,'2007-11-07 23:26:18',0,'2007-11-08 02:52:06',NULL,'Not much here...'); DROP TABLE IF EXISTS resources; CREATE TABLE resources ( id int(10) unsigned NOT NULL default '0', node_id int(10) unsigned default NULL, post_id int(10) unsigned default NULL, prototype varchar(255) default NULL, name varchar(255) default NULL, visible tinyint(3) unsigned default NULL, position tinyint(3) unsigned default NULL, creator_id int(11) default '0', creation_date datetime default NULL, modifier_id int(11) default '0', modification_date datetime default NULL, extension varchar(16) default NULL, counter int(10) unsigned default NULL, version int(10) unsigned default NULL, width smallint(5) unsigned default NULL, height smallint(5) unsigned default NULL, type varchar(255) default NULL, PRIMARY KEY (id), KEY name (name) ) ENGINE=MyISAM DEFAULT CHARSET=utf8; INSERT INTO resources VALUES (1,3,NULL,'Picture','Billy.jpg',1,0,0,'2007-11-08 00:14:40',0,'2007-11-08 00:15:30','jpg',0,NULL,539,480,'image'); DROP TABLE IF EXISTS users; CREATE TABLE users ( id int(10) unsigned NOT NULL default '0', name varchar(255) default NULL, full_name varchar(64) default NULL, password varchar(255) default NULL, role int(10) unsigned default NULL, email varchar(255) default NULL, registration_date datetime default NULL, last_login datetime default NULL, text text, website varchar(255) default NULL, PRIMARY KEY (id), KEY name (name) ) ENGINE=MyISAM DEFAULT CHARSET=utf8; INSERT INTO users VALUES (0,'admin','Administrator','<PASSWORD>',15,'<EMAIL>','2005-01-21 11:01:55','2007-11-08 00:28:45','Sys Admins Do It Better','http://www.scratchdisk.com');

MATCH (a:ANNOTATION)-[r:Body]-(b)-[r1:Body]-(a) WHERE r <> r1 WITH DISTINCT a, b MATCH (a)-[rb:Body]-(b) WITH a, b, COLLECT(rb) AS bodies CALL apoc.refactor.mergeRelationships(bodies, {}) YIELD rel RETURN rel;

<filename>tests/data/postgresql/01_extensions.sql -- Enable PostGIS (includes raster) --CREATE EXTENSION IF NOT EXISTS postgis; -- Enable pgcrypto CREATE EXTENSION IF NOT EXISTS pgcrypto;

-- file:join.sql ln:22 expect:true INSERT INTO J1_TBL VALUES (5, 0, 'five')

-- Titles DROP TABLE IF EXISTS titles; CREATE TABLE titles ( title_id VARCHAR PRIMARY KEY, title VARCHAR ); SELECT * FROM titles; -- Employees DROP TABLE IF EXISTS employees; CREATE TABLE employees ( emp_no INTEGER PRIMARY KEY, emp_title_id VARCHAR(5), FOREIGN KEY (emp_title_id) REFERENCES titles(title_id), birth_date VARCHAR(10), first_name VARCHAR, last_name VARCHAR, gender VARCHAR(1), hire_date DATE ); SELECT * FROM employees; -- Departments DROP TABLE IF EXISTS departments; CREATE TABLE departments ( dept_no VARCHAR(4) PRIMARY KEY, dept_name VARCHAR ); SELECT * FROM departments; -- Department Managers DROP TABLE IF EXISTS dept_manager; CREATE TABLE dept_manager ( dept_no VARCHAR(4), emp_no INTEGER PRIMARY KEY, FOREIGN KEY (emp_no) REFERENCES employees(emp_no) ); SELECT * FROM dept_manager; -- Salaries DROP TABLE IF EXISTS salaries; CREATE TABLE salaries ( emp_no INTEGER PRIMARY KEY, FOREIGN KEY (emp_no) REFERENCES employees(emp_no), salary INTEGER ); SELECT * FROM salaries; -- Department Employees DROP TABLE IF EXISTS dept_emp; CREATE TABLE dept_emp ( emp_no INTEGER, FOREIGN KEY (emp_no) REFERENCES employees(emp_no), dept_no VARCHAR(4), FOREIGN KEY (dept_no) REFERENCES departments(dept_no) ); SELECT * FROM dept_emp;

-- 2018-02-23T13:59:30.145 -- I forgot to set the DICTIONARY_ID_COMMENTS System Configurator /* DDL */ SELECT public.db_alter_table('M_Product_PlanningSchema','ALTER TABLE public.M_Product_PlanningSchema ADD COLUMN OnMaterialReceiptWithDestWarehouse CHAR(1) DEFAULT ''M'' NOT NULL') ;

<reponame>smith750/kc DELIMITER / CREATE TABLE AWARD_REPORT_NOTIFICATION_SENT ( AWARD_REPORT_TERM_ID DECIMAL(22) NULL, AWARD_NUMBER VARCHAR(12) NOT NULL, DUE_DATE DATE NOT NULL, SENT_DATE DATE NOT NULL, ACTION_CODE VARCHAR(3) NOT NULL, UPDATE_TIMESTAMP DATE NOT NULL, UPDATE_USER VARCHAR(60) NOT NULL, VER_NBR DECIMAL(8,0) DEFAULT 1 NOT NULL, OBJ_ID VARCHAR(36) NOT NULL ) ENGINE InnoDB CHARACTER SET utf8 COLLATE utf8_bin / DELIMITER ;

ALTER TABLE db_version CHANGE COLUMN required_8775_02_mangos_creature required_8775_03_mangos_gameobject bit; -- cause bgs now have different spawnmodes all gameobjects on those maps must go -- to all spwanmodes.. maybe this isn't valid for all gameobjects - but i won't -- destroy again all bgs :p UPDATE gameobject SET spawnMask = (0x1 | 0x2 | 0x4 | 0x8) WHERE map IN (30, 489, 529, 566);

-- Задание 1 USE `employees`; CREATE OR REPLACE VIEW `average_salary_by_department` AS SELECT dept_emp.dept_no AS dept_no, departments.dept_name AS dept_name, ROUND(AVG(salaries.salary), 2) AS average_salary FROM dept_emp AS dept_emp LEFT JOIN departments AS departments ON dept_emp.dept_no = departments.dept_no LEFT JOIN salaries AS salaries ON dept_emp.emp_no = salaries.emp_no WHERE dept_emp.to_date = '9999-01-01' AND dept_emp.dept_no IN ('d001', 'd004') GROUP BY dept_no HAVING average_salary > 70000; -- Задание 2 USE `employees`; DROP FUNCTION IF EXISTS `find_employee_by_department_number`; DELIMITER $$ USE `employees`$$ CREATE DEFINER = CURRENT_USER FUNCTION `find_employee_by_department_number`(dept_no CHAR(4)) RETURNS INT BEGIN SET @result = ( SELECT dept_manager.emp_no AS emp_no FROM dept_manager AS dept_manager WHERE dept_manager.dept_no = dept_no AND dept_manager.to_date = '9999-01-01' LIMIT 1); RETURN @result; END$$ DELIMITER ; -- Задание 3 USE `employees`; DROP TRIGGER IF EXISTS `employees`.`add_bonus_new_employee`; DELIMITER $$ USE `employees`$$ CREATE DEFINER = CURRENT_USER TRIGGER `add_bonus_new_employee` AFTER INSERT ON `employees` FOR EACH ROW BEGIN INSERT INTO salaries SET emp_no = NEW.emp_no, salary = 1000, from_date = CURRENT_DATE(), to_date = CURRENT_DATE(); END$$ DELIMITER ;

<filename>database/src/main/flow_patterns/insert_additional_data.sql /* * Copyright 2021 ABSA Group Limited * * Licensed under the Apache License, Version 2.0 (the "License"); * you may not use this file except in compliance with the License. * You may obtain a copy of the License at * http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by applicable law or agreed to in writing, software * distributed under the License is distributed on an "AS IS" BASIS, * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. * See the License for the specific language governing permissions and * limitations under the License. */ CREATE OR REPLACE FUNCTION flow_patterns.set_additional_data( IN i_flow_name TEXT, IN i_ad_name TEXT, IN i_ad_default_value TEXT, IN i_by_user TEXT, OUT status INTEGER, OUT status_text TEXT, OUT id_fp_additional_data BIGINT, OUT key_fp_flow BIGINT ) RETURNS record AS $$ ------------------------------------------------------------------------------- -- -- Function: flow_patterns.set_additional_data(4) -- Adds an additional data pattern for the given flow. -- -- Parameters: -- i_flow_name - flow name the entry belongs to -- i_ad_name - name of the additional data entry -- i_ad_default_value - default value of the additional data entry -- i_by_user - user initiating the change -- -- Returns: -- status - Status code -- status_text - Status text -- id_fp_additional_data - id of the additional data pattern entry -- key_fp_flow - id of the flow the additional data pattern were added into -- -- Status codes: -- 11 - Additional data entry created -- 41 - Flow not found -- ------------------------------------------------------------------------------- DECLARE _id_fp_additional_data BIGINT; BEGIN SELECT GF.status, GF.status_text, GF.id_fp_flow FROM flow_patterns.get_flow(i_flow_name) GF INTO status, status_text, key_fp_flow; IF status = 10 THEN INSERT INTO flow_patterns.additional_data(key_fp_flow, ad_name, ad_default_value, created_by, updated_by) VALUES (key_fp_flow, i_ad_name, i_ad_default_value, i_by_user, i_by_user) RETURNING flow_patterns.additional_data.id_fp_additional_data INTO id_fp_additional_data; status := 11; status_text := 'Additional data entry created'; ELSE -- flow not found, status_text can stay status := 41; END IF; RETURN; END; $$ LANGUAGE plpgsql VOLATILE SECURITY DEFINER; GRANT EXECUTE ON FUNCTION flow_patterns.set_additional_data(TEXT, TEXT, TEXT, TEXT) TO atum_configurator;

<filename>util/src/main/resources/cleanAccount-postgresql.sql<gh_stars>1000+ CREATE OR REPLACE PROCEDURE cleanAccount(p_account_id varchar(36)) LANGUAGE plpgsql AS $$ DECLARE v_account_record_id bigint; v_tenant_record_id bigint; BEGIN select record_id, tenant_record_id from accounts WHERE id = p_account_id into v_account_record_id, v_tenant_record_id; call trimAccount(p_account_id); DELETE FROM account_history WHERE target_record_id = v_account_record_id and tenant_record_id = v_tenant_record_id; DELETE FROM accounts WHERE record_id = v_account_record_id and tenant_record_id = v_tenant_record_id; DELETE FROM audit_log WHERE account_record_id = v_account_record_id and tenant_record_id = v_tenant_record_id; DELETE FROM payment_method_history WHERE account_record_id = v_account_record_id and tenant_record_id = v_tenant_record_id; DELETE FROM payment_methods WHERE account_record_id = v_account_record_id and tenant_record_id = v_tenant_record_id; END $$;

-- VARBINARY CREATE TYPE sys.BBF_VARBINARY; CREATE OR REPLACE FUNCTION sys.varbinaryin(cstring, oid, integer) RETURNS sys.BBF_VARBINARY AS 'babelfishpg_common', 'varbinaryin' LANGUAGE C IMMUTABLE STRICT PARALLEL SAFE; CREATE OR REPLACE FUNCTION sys.varbinaryout(sys.BBF_VARBINARY) RETURNS cstring AS 'babelfishpg_common', 'varbinaryout' LANGUAGE C IMMUTABLE STRICT PARALLEL SAFE; CREATE OR REPLACE FUNCTION sys.varbinaryrecv(internal, oid, integer) RETURNS sys.BBF_VARBINARY AS 'babelfishpg_common', 'varbinaryrecv' LANGUAGE C IMMUTABLE STRICT PARALLEL SAFE; CREATE OR REPLACE FUNCTION sys.varbinarysend(sys.BBF_VARBINARY) RETURNS bytea AS 'babelfishpg_common', 'varbinarysend' LANGUAGE C IMMUTABLE STRICT PARALLEL SAFE; CREATE OR REPLACE FUNCTION sys.varbinarytypmodin(cstring[]) RETURNS integer AS 'babelfishpg_common', 'varbinarytypmodin' LANGUAGE C IMMUTABLE STRICT PARALLEL SAFE; CREATE OR REPLACE FUNCTION sys.varbinarytypmodout(integer) RETURNS cstring AS 'babelfishpg_common', 'varbinarytypmodout' LANGUAGE C IMMUTABLE STRICT PARALLEL SAFE; CREATE TYPE sys.BBF_VARBINARY ( INPUT = sys.varbinaryin, OUTPUT = sys.varbinaryout, RECEIVE = sys.varbinaryrecv, SEND = sys.varbinarysend, TYPMOD_IN = sys.varbinarytypmodin, TYPMOD_OUT = sys.varbinarytypmodout, INTERNALLENGTH = VARIABLE, ALIGNMENT = 'int4', STORAGE = 'extended', CATEGORY = 'U', PREFERRED = false, COLLATABLE = false ); CREATE OR REPLACE FUNCTION sys.bbfvarbinary(sys.BBF_VARBINARY, integer, boolean) RETURNS sys.BBF_VARBINARY AS 'babelfishpg_common', 'varbinary' LANGUAGE C IMMUTABLE STRICT PARALLEL SAFE; -- typmod cast for sys.BBF_VARBINARY CREATE CAST (sys.BBF_VARBINARY AS sys.BBF_VARBINARY) WITH FUNCTION sys.bbfvarbinary(sys.BBF_VARBINARY, integer, BOOLEAN) AS ASSIGNMENT; CREATE OR REPLACE FUNCTION sys.byteavarbinary(pg_catalog.BYTEA, integer, boolean) RETURNS sys.BBF_VARBINARY AS 'babelfishpg_common', 'byteavarbinary' LANGUAGE C IMMUTABLE STRICT PARALLEL SAFE; CREATE CAST (pg_catalog.BYTEA AS sys.BBF_VARBINARY) WITH FUNCTION sys.byteavarbinary(pg_catalog.BYTEA, integer, boolean) AS ASSIGNMENT; CREATE OR REPLACE FUNCTION sys.varbinarybytea(sys.BBF_VARBINARY, integer, boolean) RETURNS pg_catalog.BYTEA AS 'babelfishpg_common', 'byteavarbinary' LANGUAGE C IMMUTABLE STRICT PARALLEL SAFE; CREATE CAST (sys.BBF_VARBINARY AS pg_catalog.BYTEA) WITH FUNCTION sys.varbinarybytea(sys.BBF_VARBINARY, integer, boolean) AS ASSIGNMENT; CREATE OR REPLACE FUNCTION sys.varcharvarbinary(sys.VARCHAR, integer, boolean) RETURNS sys.BBF_VARBINARY AS 'babelfishpg_common', 'varcharvarbinary' LANGUAGE C IMMUTABLE STRICT PARALLEL SAFE; CREATE CAST (sys.VARCHAR AS sys.BBF_VARBINARY) WITH FUNCTION sys.varcharvarbinary (sys.VARCHAR, integer, boolean) AS ASSIGNMENT; CREATE OR REPLACE FUNCTION sys.varcharvarbinary(pg_catalog.VARCHAR, integer, boolean) RETURNS sys.BBF_VARBINARY AS 'babelfishpg_common', 'varcharvarbinary' LANGUAGE C IMMUTABLE STRICT PARALLEL SAFE; CREATE CAST (pg_catalog.VARCHAR AS sys.BBF_VARBINARY) WITH FUNCTION sys.varcharvarbinary (pg_catalog.VARCHAR, integer, boolean) AS ASSIGNMENT; CREATE OR REPLACE FUNCTION sys.bpcharvarbinary(pg_catalog.BPCHAR, integer, boolean) RETURNS sys.BBF_VARBINARY AS 'babelfishpg_common', 'bpcharvarbinary' LANGUAGE C IMMUTABLE STRICT PARALLEL SAFE; CREATE CAST (pg_catalog.BPCHAR AS sys.BBF_VARBINARY) WITH FUNCTION sys.bpcharvarbinary (pg_catalog.BPCHAR, integer, boolean) AS ASSIGNMENT; CREATE OR REPLACE FUNCTION sys.bpcharvarbinary(sys.BPCHAR, integer, boolean) RETURNS sys.BBF_VARBINARY AS 'babelfishpg_common', 'bpcharvarbinary' LANGUAGE C IMMUTABLE STRICT PARALLEL SAFE; CREATE CAST (sys.BPCHAR AS sys.BBF_VARBINARY) WITH FUNCTION sys.bpcharvarbinary (sys.BPCHAR, integer, boolean) AS ASSIGNMENT; CREATE OR REPLACE FUNCTION sys.varbinarysysvarchar(sys.BBF_VARBINARY, integer, boolean) RETURNS sys.VARCHAR AS 'babelfishpg_common', 'varbinaryvarchar' LANGUAGE C IMMUTABLE STRICT PARALLEL SAFE; CREATE CAST (sys.BBF_VARBINARY AS sys.VARCHAR) WITH FUNCTION sys.varbinarysysvarchar (sys.BBF_VARBINARY, integer, boolean) AS ASSIGNMENT; CREATE OR REPLACE FUNCTION sys.varbinaryvarchar(sys.BBF_VARBINARY, integer, boolean) RETURNS pg_catalog.VARCHAR AS 'babelfishpg_common', 'varbinaryvarchar' LANGUAGE C IMMUTABLE STRICT PARALLEL SAFE; CREATE CAST (sys.BBF_VARBINARY AS pg_catalog.VARCHAR) WITH FUNCTION sys.varbinaryvarchar (sys.BBF_VARBINARY, integer, boolean) AS ASSIGNMENT; CREATE OR REPLACE FUNCTION sys.int2varbinary(INT2, integer, boolean) RETURNS sys.BBF_VARBINARY AS 'babelfishpg_common', 'int2varbinary' LANGUAGE C IMMUTABLE STRICT PARALLEL SAFE; CREATE CAST (INT2 AS sys.BBF_VARBINARY) WITH FUNCTION sys.int2varbinary (INT2, integer, boolean) AS ASSIGNMENT; CREATE OR REPLACE FUNCTION sys.int4varbinary(INT4, integer, boolean) RETURNS sys.BBF_VARBINARY AS 'babelfishpg_common', 'int4varbinary' LANGUAGE C IMMUTABLE STRICT PARALLEL SAFE; CREATE CAST (INT4 AS sys.BBF_VARBINARY) WITH FUNCTION sys.int4varbinary (INT4, integer, boolean) AS ASSIGNMENT; CREATE OR REPLACE FUNCTION sys.int8varbinary(INT8, integer, boolean) RETURNS sys.BBF_VARBINARY AS 'babelfishpg_common', 'int8varbinary' LANGUAGE C IMMUTABLE STRICT PARALLEL SAFE; CREATE CAST (INT8 AS sys.BBF_VARBINARY) WITH FUNCTION sys.int8varbinary (INT8, integer, boolean) AS ASSIGNMENT; CREATE OR REPLACE FUNCTION sys.float4varbinary(REAL, integer, boolean) RETURNS sys.BBF_VARBINARY AS 'babelfishpg_common', 'float4varbinary' LANGUAGE C IMMUTABLE STRICT PARALLEL SAFE; CREATE CAST (REAL AS sys.BBF_VARBINARY) WITH FUNCTION sys.float4varbinary (REAL, integer, boolean) AS ASSIGNMENT; CREATE OR REPLACE FUNCTION sys.float8varbinary(DOUBLE PRECISION, integer, boolean) RETURNS sys.BBF_VARBINARY AS 'babelfishpg_common', 'float8varbinary' LANGUAGE C IMMUTABLE STRICT PARALLEL SAFE; CREATE CAST (DOUBLE PRECISION AS sys.BBF_VARBINARY) WITH FUNCTION sys.float8varbinary (DOUBLE PRECISION, integer, boolean) AS ASSIGNMENT; CREATE OR REPLACE FUNCTION sys.varbinaryint2(sys.BBF_VARBINARY) RETURNS INT2 AS 'babelfishpg_common', 'varbinaryint2' LANGUAGE C IMMUTABLE STRICT PARALLEL SAFE; CREATE CAST (sys.BBF_VARBINARY as INT2) WITH FUNCTION sys.varbinaryint2 (sys.BBF_VARBINARY) AS ASSIGNMENT; CREATE OR REPLACE FUNCTION sys.varbinaryint4(sys.BBF_VARBINARY) RETURNS INT4 AS 'babelfishpg_common', 'varbinaryint4' LANGUAGE C IMMUTABLE STRICT PARALLEL SAFE; CREATE CAST (sys.BBF_VARBINARY as INT4) WITH FUNCTION sys.varbinaryint4 (sys.BBF_VARBINARY) AS ASSIGNMENT; CREATE OR REPLACE FUNCTION sys.varbinaryint8(sys.BBF_VARBINARY) RETURNS INT8 AS 'babelfishpg_common', 'varbinaryint8' LANGUAGE C IMMUTABLE STRICT PARALLEL SAFE; CREATE CAST (sys.BBF_VARBINARY as INT8) WITH FUNCTION sys.varbinaryint8 (sys.BBF_VARBINARY) AS ASSIGNMENT; CREATE OR REPLACE FUNCTION sys.varbinaryfloat4(sys.BBF_VARBINARY) RETURNS REAL AS 'babelfishpg_common', 'varbinaryfloat4' LANGUAGE C IMMUTABLE STRICT PARALLEL SAFE; CREATE OR REPLACE FUNCTION sys.varbinaryfloat8(sys.BBF_VARBINARY) RETURNS DOUBLE PRECISION AS 'babelfishpg_common', 'varbinaryfloat8' LANGUAGE C IMMUTABLE STRICT PARALLEL SAFE; SET enable_domain_typmod = TRUE; CREATE DOMAIN sys.VARBINARY AS sys.BBF_VARBINARY; RESET enable_domain_typmod; CREATE OR REPLACE FUNCTION sys.varbinary(sys.VARBINARY, integer, boolean) RETURNS sys.VARBINARY AS 'babelfishpg_common', 'varbinary' LANGUAGE C IMMUTABLE STRICT PARALLEL SAFE; SET client_min_messages = 'ERROR'; CREATE CAST (sys.VARBINARY AS sys.VARBINARY) WITH FUNCTION sys.varbinary (sys.VARBINARY, integer, BOOLEAN) AS ASSIGNMENT; SET client_min_messages = 'WARNING'; -- Add support for varbinary and binary with operators -- Support equals CREATE FUNCTION sys.varbinary_eq(leftarg sys.bbf_varbinary, rightarg sys.bbf_varbinary) RETURNS boolean AS 'babelfishpg_common', 'varbinary_eq' LANGUAGE C IMMUTABLE STRICT PARALLEL SAFE; CREATE OPERATOR sys.= ( LEFTARG = sys.bbf_varbinary, RIGHTARG = sys.bbf_varbinary, FUNCTION = sys.varbinary_eq, COMMUTATOR = = ); -- Support not equals CREATE FUNCTION sys.varbinary_neq(leftarg sys.bbf_varbinary, rightarg sys.bbf_varbinary) RETURNS boolean AS 'babelfishpg_common', 'varbinary_neq' LANGUAGE C IMMUTABLE STRICT PARALLEL SAFE; CREATE OPERATOR sys.<> ( LEFTARG = sys.bbf_varbinary, RIGHTARG = sys.bbf_varbinary, FUNCTION = sys.varbinary_neq, COMMUTATOR = <> ); -- Support greater than CREATE FUNCTION sys.varbinary_gt(leftarg sys.bbf_varbinary, rightarg sys.bbf_varbinary) RETURNS boolean AS 'babelfishpg_common', 'varbinary_gt' LANGUAGE C IMMUTABLE STRICT PARALLEL SAFE; CREATE OPERATOR sys.> ( LEFTARG = sys.bbf_varbinary, RIGHTARG = sys.bbf_varbinary, FUNCTION = sys.varbinary_gt, COMMUTATOR = < ); -- Support greater than equals CREATE FUNCTION sys.varbinary_geq(leftarg sys.bbf_varbinary, rightarg sys.bbf_varbinary) RETURNS boolean AS 'babelfishpg_common', 'varbinary_geq' LANGUAGE C IMMUTABLE STRICT PARALLEL SAFE; CREATE OPERATOR sys.>= ( LEFTARG = sys.bbf_varbinary, RIGHTARG = sys.bbf_varbinary, FUNCTION = sys.varbinary_geq, COMMUTATOR = <= ); -- Support less than CREATE FUNCTION sys.varbinary_lt(leftarg sys.bbf_varbinary, rightarg sys.bbf_varbinary) RETURNS boolean AS 'babelfishpg_common', 'varbinary_lt' LANGUAGE C IMMUTABLE STRICT PARALLEL SAFE; CREATE OPERATOR sys.< ( LEFTARG = sys.bbf_varbinary, RIGHTARG = sys.bbf_varbinary, FUNCTION = sys.varbinary_lt, COMMUTATOR = > ); -- Support less than equals CREATE FUNCTION sys.varbinary_leq(leftarg sys.bbf_varbinary, rightarg sys.bbf_varbinary) RETURNS boolean AS 'babelfishpg_common', 'varbinary_leq' LANGUAGE C IMMUTABLE STRICT PARALLEL SAFE; CREATE OPERATOR sys.<= ( LEFTARG = sys.bbf_varbinary, RIGHTARG = sys.bbf_varbinary, FUNCTION = sys.varbinary_leq, COMMUTATOR = >= ); CREATE FUNCTION sys.bbf_varbinary_cmp(sys.bbf_varbinary, sys.bbf_varbinary) RETURNS int AS 'babelfishpg_common', 'varbinary_cmp' LANGUAGE C IMMUTABLE STRICT PARALLEL SAFE; CREATE OPERATOR CLASS sys.bbf_varbinary_ops DEFAULT FOR TYPE sys.bbf_varbinary USING btree AS OPERATOR 1 < (sys.bbf_varbinary, sys.bbf_varbinary), OPERATOR 2 <= (sys.bbf_varbinary, sys.bbf_varbinary), OPERATOR 3 = (sys.bbf_varbinary, sys.bbf_varbinary), OPERATOR 4 >= (sys.bbf_varbinary, sys.bbf_varbinary), OPERATOR 5 > (sys.bbf_varbinary, sys.bbf_varbinary), FUNCTION 1 sys.bbf_varbinary_cmp(sys.bbf_varbinary, sys.bbf_varbinary);

-- phpMyAdmin SQL Dump -- version 4.4.14 -- http://www.phpmyadmin.net -- -- Servidor: localhost -- Tiempo de generación: 10-03-2016 a las 05:23:10 -- Versión del servidor: 5.6.26 -- Versión de PHP: 5.6.12 SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO"; SET time_zone = "+00:00"; /*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */; /*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */; /*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */; /*!40101 SET NAMES utf8mb4 */; -- -- Base de datos: `kingdata` -- -- -------------------------------------------------------- -- -- Estructura de tabla para la tabla `auth_assignment` -- CREATE TABLE IF NOT EXISTS `auth_assignment` ( `item_name` varchar(64) COLLATE utf8_unicode_ci NOT NULL, `user_id` varchar(64) COLLATE utf8_unicode_ci NOT NULL, `created_at` int(11) DEFAULT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Volcado de datos para la tabla `auth_assignment` -- INSERT INTO `auth_assignment` (`item_name`, `user_id`, `created_at`) VALUES ('admin', '1', NULL), ('admin', '8', 1457583574); -- -------------------------------------------------------- -- -- Estructura de tabla para la tabla `auth_item` -- CREATE TABLE IF NOT EXISTS `auth_item` ( `name` varchar(64) COLLATE utf8_unicode_ci NOT NULL, `type` int(11) NOT NULL, `description` text COLLATE utf8_unicode_ci, `rule_name` varchar(64) COLLATE utf8_unicode_ci DEFAULT NULL, `data` text COLLATE utf8_unicode_ci, `created_at` int(11) DEFAULT NULL, `updated_at` int(11) DEFAULT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Volcado de datos para la tabla `auth_item` -- INSERT INTO `auth_item` (`name`, `type`, `description`, `rule_name`, `data`, `created_at`, `updated_at`) VALUES ('admin', 1, 'Administrador del Sistema', NULL, NULL, NULL, NULL), ('vendedor', 1, 'Vendedor', NULL, NULL, NULL, NULL); -- -------------------------------------------------------- -- -- Estructura de tabla para la tabla `auth_item_child` -- CREATE TABLE IF NOT EXISTS `auth_item_child` ( `parent` varchar(64) COLLATE utf8_unicode_ci NOT NULL, `child` varchar(64) COLLATE utf8_unicode_ci NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -------------------------------------------------------- -- -- Estructura de tabla para la tabla `auth_rule` -- CREATE TABLE IF NOT EXISTS `auth_rule` ( `name` varchar(64) COLLATE utf8_unicode_ci NOT NULL, `data` text COLLATE utf8_unicode_ci, `created_at` int(11) DEFAULT NULL, `updated_at` int(11) DEFAULT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -------------------------------------------------------- -- -- Estructura de tabla para la tabla `Clientes` -- CREATE TABLE IF NOT EXISTS `Clientes` ( `ClienteID` int(11) NOT NULL, `ClienteNombre` varchar(100) COLLATE utf8_unicode_ci NOT NULL, `ClienteCedula` varchar(45) COLLATE utf8_unicode_ci NOT NULL, `ClienteDireccion` varchar(200) COLLATE utf8_unicode_ci DEFAULT NULL, `ClienteEmail` varchar(100) COLLATE utf8_unicode_ci DEFAULT NULL, `ClienteTelefono` varchar(20) COLLATE utf8_unicode_ci DEFAULT NULL, `ClienteContacto` varchar(100) COLLATE utf8_unicode_ci DEFAULT NULL, `Observaciones` varchar(200) COLLATE utf8_unicode_ci DEFAULT NULL, `RutaID` int(11) NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -------------------------------------------------------- -- -- Estructura de tabla para la tabla `FormasPagos` -- CREATE TABLE IF NOT EXISTS `FormasPagos` ( `FormaPagoID` int(11) NOT NULL, `FormaPagoNombre` varchar(100) COLLATE utf8_unicode_ci NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -------------------------------------------------------- -- -- Estructura de tabla para la tabla `migration` -- CREATE TABLE IF NOT EXISTS `migration` ( `version` varchar(180) COLLATE utf8_unicode_ci NOT NULL, `apply_time` int(11) DEFAULT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Volcado de datos para la tabla `migration` -- INSERT INTO `migration` (`version`, `apply_time`) VALUES ('m000000_000000_base', 1457483926), ('m140506_102106_rbac_init', 1457483931); -- -------------------------------------------------------- -- -- Estructura de tabla para la tabla `Ordenes` -- CREATE TABLE IF NOT EXISTS `Ordenes` ( `OrdenID` int(11) NOT NULL, `OrdenFecha` date NOT NULL, `OrdenEstado` varchar(45) COLLATE utf8_unicode_ci DEFAULT NULL, `Observaciones` varchar(200) COLLATE utf8_unicode_ci DEFAULT NULL, `Ordencol` varchar(45) COLLATE utf8_unicode_ci DEFAULT NULL, `ClienteID` int(11) NOT NULL, `FormaPagoID` int(11) NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -------------------------------------------------------- -- -- Estructura de tabla para la tabla `Ordenes_Productos` -- CREATE TABLE IF NOT EXISTS `Ordenes_Productos` ( `OrdenID` int(11) NOT NULL, `ProductoID` int(11) NOT NULL, `CantidadProducto` int(11) DEFAULT NULL, `TotalPrecio` decimal(8,2) DEFAULT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -------------------------------------------------------- -- -- Estructura de tabla para la tabla `Productos` -- CREATE TABLE IF NOT EXISTS `Productos` ( `ProductoID` int(11) NOT NULL, `ProductoNombre` varchar(100) COLLATE utf8_unicode_ci NOT NULL, `ProductoDescripcion` varchar(45) COLLATE utf8_unicode_ci DEFAULT NULL, `ProductoModelo` varchar(45) COLLATE utf8_unicode_ci DEFAULT NULL, `ProductoColor` varchar(45) COLLATE utf8_unicode_ci DEFAULT NULL, `ProductoSKU` varchar(45) COLLATE utf8_unicode_ci DEFAULT NULL, `ProductoIm1` varchar(250) COLLATE utf8_unicode_ci DEFAULT NULL, `ProductoIm2` varchar(250) COLLATE utf8_unicode_ci DEFAULT NULL, `ProductoIm3` varchar(250) COLLATE utf8_unicode_ci DEFAULT NULL, `ProductoDisponible` int(11) DEFAULT NULL, `ProductoMaximo` int(11) DEFAULT NULL, `Productocol` int(11) DEFAULT NULL, `ProductoPrecio` decimal(8,2) DEFAULT NULL, `ProductoIva` decimal(8,2) DEFAULT NULL, `TipoProductoID` int(11) NOT NULL, `ProveedorID` int(11) NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -------------------------------------------------------- -- -- Estructura de tabla para la tabla `Proveedores` -- CREATE TABLE IF NOT EXISTS `Proveedores` ( `ProveedorID` int(11) NOT NULL, `ProveedorNombre` varchar(100) COLLATE utf8_unicode_ci NOT NULL, `ProveedorEmail` varchar(100) COLLATE utf8_unicode_ci DEFAULT NULL, `ProveedorTelefono` varchar(100) COLLATE utf8_unicode_ci DEFAULT NULL, `ProveedorDireccion` varchar(200) COLLATE utf8_unicode_ci DEFAULT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -------------------------------------------------------- -- -- Estructura de tabla para la tabla `Roles` -- CREATE TABLE IF NOT EXISTS `Roles` ( `RolID` int(11) NOT NULL, `RolNombre` varchar(50) COLLATE utf8_unicode_ci NOT NULL ) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Volcado de datos para la tabla `Roles` -- INSERT INTO `Roles` (`RolID`, `RolNombre`) VALUES (1, 'Administrador'); -- -------------------------------------------------------- -- -- Estructura de tabla para la tabla `Rutas` -- CREATE TABLE IF NOT EXISTS `Rutas` ( `RutaID` int(11) NOT NULL, `RutaNombre` varchar(45) COLLATE utf8_unicode_ci NOT NULL, `RutaFecha` date NOT NULL, `UsuarioID` int(11) NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -------------------------------------------------------- -- -- Estructura de tabla para la tabla `TiposProductos` -- CREATE TABLE IF NOT EXISTS `TiposProductos` ( `TipoProductoID` int(11) NOT NULL, `TipoProductoNombre` varchar(100) COLLATE utf8_unicode_ci NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -------------------------------------------------------- -- -- Estructura de tabla para la tabla `Usuarios` -- CREATE TABLE IF NOT EXISTS `Usuarios` ( `UsuarioID` int(11) NOT NULL, `UsuarioNombre` varchar(100) COLLATE utf8_unicode_ci NOT NULL, `UsuarioApellido` varchar(100) COLLATE utf8_unicode_ci NOT NULL, `UsuarioEmail` varchar(100) COLLATE utf8_unicode_ci NOT NULL, `UsuarioAlias` varchar(50) COLLATE utf8_unicode_ci NOT NULL, `UsuarioTelefono` varchar(20) COLLATE utf8_unicode_ci DEFAULT NULL, `UsuarioClave` varchar(200) COLLATE utf8_unicode_ci NOT NULL, `UsuarioDireccion` varchar(200) COLLATE utf8_unicode_ci DEFAULT NULL, `Usuariocol` varchar(45) COLLATE utf8_unicode_ci DEFAULT NULL, `RolID` int(11) NOT NULL ) ENGINE=InnoDB AUTO_INCREMENT=9 DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; -- -- Volcado de datos para la tabla `Usuarios` -- INSERT INTO `Usuarios` (`UsuarioID`, `UsuarioNombre`, `UsuarioApellido`, `UsuarioEmail`, `UsuarioAlias`, `UsuarioTelefono`, `UsuarioClave`, `UsuarioDireccion`, `Usuariocol`, `RolID`) VALUES (1, 'Administrador', 'Administrador', '<EMAIL>', 'admin ', NULL, '$2y$13$I7RG8AmD5q2MC6V.H.ECkOxmOai4YBdK0mFipIHR0fH2jQosj3K6y', NULL, NULL, 1), (8, 'Felipe', 'Felipe', '<EMAIL>', 'Felipe35modus', '', '$2y$13$8Ak6cWBH4wRrrMKeSlSqberLt1tAuInDWnheuAoHsMRt4Sp4F7sXO', 'San Cristóbal', '', 1); -- -- Índices para tablas volcadas -- -- -- Indices de la tabla `auth_assignment` -- ALTER TABLE `auth_assignment` ADD PRIMARY KEY (`item_name`,`user_id`); -- -- Indices de la tabla `auth_item` -- ALTER TABLE `auth_item` ADD PRIMARY KEY (`name`), ADD KEY `rule_name` (`rule_name`), ADD KEY `idx-auth_item-type` (`type`); -- -- Indices de la tabla `auth_item_child` -- ALTER TABLE `auth_item_child` ADD PRIMARY KEY (`parent`,`child`), ADD KEY `child` (`child`); -- -- Indices de la tabla `auth_rule` -- ALTER TABLE `auth_rule` ADD PRIMARY KEY (`name`); -- -- Indices de la tabla `Clientes` -- ALTER TABLE `Clientes` ADD PRIMARY KEY (`ClienteID`), ADD KEY `fk_Clientes_Rutas_idx` (`RutaID`); -- -- Indices de la tabla `FormasPagos` -- ALTER TABLE `FormasPagos` ADD PRIMARY KEY (`FormaPagoID`); -- -- Indices de la tabla `migration` -- ALTER TABLE `migration` ADD PRIMARY KEY (`version`); -- -- Indices de la tabla `Ordenes` -- ALTER TABLE `Ordenes` ADD PRIMARY KEY (`OrdenID`), ADD KEY `fk_Ordenes_Clientes1_idx` (`ClienteID`), ADD KEY `fk_Ordenes_FormasPagos1_idx` (`FormaPagoID`); -- -- Indices de la tabla `Ordenes_Productos` -- ALTER TABLE `Ordenes_Productos` ADD PRIMARY KEY (`OrdenID`,`ProductoID`), ADD KEY `fk_Orden_has_Productos_Productos1_idx` (`ProductoID`), ADD KEY `fk_Orden_has_Productos_Ordenes1_idx` (`OrdenID`); -- -- Indices de la tabla `Productos` -- ALTER TABLE `Productos` ADD PRIMARY KEY (`ProductoID`), ADD KEY `fk_Productos_TiposProductos1_idx` (`TipoProductoID`), ADD KEY `fk_Productos_Proveedors1_idx` (`ProveedorID`); -- -- Indices de la tabla `Proveedores` -- ALTER TABLE `Proveedores` ADD PRIMARY KEY (`ProveedorID`); -- -- Indices de la tabla `Roles` -- ALTER TABLE `Roles` ADD PRIMARY KEY (`RolID`); -- -- Indices de la tabla `Rutas` -- ALTER TABLE `Rutas` ADD PRIMARY KEY (`RutaID`), ADD KEY `fk_Rutas_Usuarios1_idx` (`UsuarioID`); -- -- Indices de la tabla `TiposProductos` -- ALTER TABLE `TiposProductos` ADD PRIMARY KEY (`TipoProductoID`); -- -- Indices de la tabla `Usuarios` -- ALTER TABLE `Usuarios` ADD PRIMARY KEY (`UsuarioID`), ADD KEY `fk_Usuarios_Roles1_idx` (`RolID`); -- -- AUTO_INCREMENT de las tablas volcadas -- -- -- AUTO_INCREMENT de la tabla `Clientes` -- ALTER TABLE `Clientes` MODIFY `ClienteID` int(11) NOT NULL AUTO_INCREMENT; -- -- AUTO_INCREMENT de la tabla `FormasPagos` -- ALTER TABLE `FormasPagos` MODIFY `FormaPagoID` int(11) NOT NULL AUTO_INCREMENT; -- -- AUTO_INCREMENT de la tabla `Ordenes` -- ALTER TABLE `Ordenes` MODIFY `OrdenID` int(11) NOT NULL AUTO_INCREMENT; -- -- AUTO_INCREMENT de la tabla `Productos` -- ALTER TABLE `Productos` MODIFY `ProductoID` int(11) NOT NULL AUTO_INCREMENT; -- -- AUTO_INCREMENT de la tabla `Proveedores` -- ALTER TABLE `Proveedores` MODIFY `ProveedorID` int(11) NOT NULL AUTO_INCREMENT; -- -- AUTO_INCREMENT de la tabla `Roles` -- ALTER TABLE `Roles` MODIFY `RolID` int(11) NOT NULL AUTO_INCREMENT,AUTO_INCREMENT=2; -- -- AUTO_INCREMENT de la tabla `Rutas` -- ALTER TABLE `Rutas` MODIFY `RutaID` int(11) NOT NULL AUTO_INCREMENT; -- -- AUTO_INCREMENT de la tabla `TiposProductos` -- ALTER TABLE `TiposProductos` MODIFY `TipoProductoID` int(11) NOT NULL AUTO_INCREMENT; -- -- AUTO_INCREMENT de la tabla `Usuarios` -- ALTER TABLE `Usuarios` MODIFY `UsuarioID` int(11) NOT NULL AUTO_INCREMENT,AUTO_INCREMENT=9; -- -- Restricciones para tablas volcadas -- -- -- Filtros para la tabla `auth_assignment` -- ALTER TABLE `auth_assignment` ADD CONSTRAINT `auth_assignment_ibfk_1` FOREIGN KEY (`item_name`) REFERENCES `auth_item` (`name`) ON DELETE CASCADE ON UPDATE CASCADE; -- -- Filtros para la tabla `auth_item` -- ALTER TABLE `auth_item` ADD CONSTRAINT `auth_item_ibfk_1` FOREIGN KEY (`rule_name`) REFERENCES `auth_rule` (`name`) ON DELETE SET NULL ON UPDATE CASCADE; -- -- Filtros para la tabla `auth_item_child` -- ALTER TABLE `auth_item_child` ADD CONSTRAINT `auth_item_child_ibfk_1` FOREIGN KEY (`parent`) REFERENCES `auth_item` (`name`) ON DELETE CASCADE ON UPDATE CASCADE, ADD CONSTRAINT `auth_item_child_ibfk_2` FOREIGN KEY (`child`) REFERENCES `auth_item` (`name`) ON DELETE CASCADE ON UPDATE CASCADE; -- -- Filtros para la tabla `Clientes` -- ALTER TABLE `Clientes` ADD CONSTRAINT `fk_Cliente_Ruta` FOREIGN KEY (`RutaID`) REFERENCES `Rutas` (`RutaID`) ON DELETE NO ACTION ON UPDATE NO ACTION; -- -- Filtros para la tabla `Ordenes` -- ALTER TABLE `Ordenes` ADD CONSTRAINT `fk_Ordenes_Clientes1` FOREIGN KEY (`ClienteID`) REFERENCES `Clientes` (`ClienteID`) ON DELETE NO ACTION ON UPDATE NO ACTION, ADD CONSTRAINT `fk_Ordenes_FormasPagos1` FOREIGN KEY (`FormaPagoID`) REFERENCES `FormasPagos` (`FormaPagoID`) ON DELETE NO ACTION ON UPDATE NO ACTION; -- -- Filtros para la tabla `Ordenes_Productos` -- ALTER TABLE `Ordenes_Productos` ADD CONSTRAINT `fk_Orden_has_Productos_Ordenes1` FOREIGN KEY (`OrdenID`) REFERENCES `Ordenes` (`OrdenID`) ON DELETE NO ACTION ON UPDATE NO ACTION, ADD CONSTRAINT `fk_Orden_has_Productos_Productos1` FOREIGN KEY (`ProductoID`) REFERENCES `Productos` (`ProductoID`) ON DELETE NO ACTION ON UPDATE NO ACTION; -- -- Filtros para la tabla `Productos` -- ALTER TABLE `Productos` ADD CONSTRAINT `fk_Productos_Proveedores1` FOREIGN KEY (`ProveedorID`) REFERENCES `Proveedores` (`ProveedorID`) ON DELETE NO ACTION ON UPDATE NO ACTION, ADD CONSTRAINT `fk_Productos_TiposProductos1` FOREIGN KEY (`TipoProductoID`) REFERENCES `TiposProductos` (`TipoProductoID`) ON DELETE NO ACTION ON UPDATE NO ACTION; -- -- Filtros para la tabla `Rutas` -- ALTER TABLE `Rutas` ADD CONSTRAINT `fk_Rutas_Usuarios1` FOREIGN KEY (`UsuarioID`) REFERENCES `Usuarios` (`UsuarioID`) ON DELETE NO ACTION ON UPDATE NO ACTION; -- -- Filtros para la tabla `Usuarios` -- ALTER TABLE `Usuarios` ADD CONSTRAINT `fk_Usuarios_Roles1` FOREIGN KEY (`RolID`) REFERENCES `Roles` (`RolID`) ON DELETE NO ACTION ON UPDATE NO ACTION; /*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */; /*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */; /*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;

-- -------------------------------------------------------- -- Host: 127.0.0.1 -- Versión del servidor: 10.1.31-MariaDB - mariadb.org binary distribution -- SO del servidor: Win32 -- HeidiSQL Versión: 9.5.0.5196 -- -------------------------------------------------------- /*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */; /*!40101 SET NAMES utf8 */; /*!50503 SET NAMES utf8mb4 */; /*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */; /*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */; -- Volcando estructura de base de datos para libreria_arkix DROP DATABASE IF EXISTS `libreria_arkix`; CREATE DATABASE IF NOT EXISTS `libreria_arkix` /*!40100 DEFAULT CHARACTER SET utf8 COLLATE utf8_spanish_ci */; USE `libreria_arkix`; -- Volcando estructura para tabla libreria_arkix.autores DROP TABLE IF EXISTS `autores`; CREATE TABLE IF NOT EXISTS `autores` ( `id_autor` int(11) NOT NULL AUTO_INCREMENT, `nombre` varchar(100) COLLATE utf8_spanish_ci DEFAULT NULL, `apellidos` varchar(100) COLLATE utf8_spanish_ci NOT NULL, `anio_nacimiento` date DEFAULT NULL, `anio_fallecido` date DEFAULT NULL, PRIMARY KEY (`id_autor`) ) ENGINE=InnoDB AUTO_INCREMENT=1 DEFAULT CHARSET=utf8 COLLATE=utf8_spanish_ci; -- La exportación de datos fue deseleccionada. -- Volcando estructura para tabla libreria_arkix.clientes DROP TABLE IF EXISTS `clientes`; CREATE TABLE IF NOT EXISTS `clientes` ( `id_cliente` int(11) NOT NULL AUTO_INCREMENT, `nombre` varchar(50) COLLATE utf8_spanish_ci NOT NULL, `apellidos` varchar(50) COLLATE utf8_spanish_ci NOT NULL, `telefono` int(11) NOT NULL, `direccion_envio` varchar(100) COLLATE utf8_spanish_ci NOT NULL, PRIMARY KEY (`id_cliente`) ) ENGINE=InnoDB AUTO_INCREMENT=1 DEFAULT CHARSET=utf8 COLLATE=utf8_spanish_ci; -- La exportación de datos fue deseleccionada. -- Volcando estructura para tabla libreria_arkix.libros DROP TABLE IF EXISTS `libros`; CREATE TABLE IF NOT EXISTS `libros` ( `id_libro` int(11) NOT NULL AUTO_INCREMENT, `titulo` varchar(50) COLLATE utf8_spanish_ci NOT NULL, `editor` varchar(50) COLLATE utf8_spanish_ci NOT NULL, `fecha_publicacion` date NOT NULL, `edicion` varchar(50) COLLATE utf8_spanish_ci NOT NULL, `costo` double NOT NULL, `precio_sugerido` double NOT NULL, `valoracion` enum('Extraordinario','Excelente','Bueno','Dañado') COLLATE utf8_spanish_ci NOT NULL, `descripcion_valoracion` varchar(200) COLLATE utf8_spanish_ci DEFAULT NULL, `estado` enum('Inventario','Vendido') COLLATE utf8_spanish_ci NOT NULL DEFAULT 'Inventario', PRIMARY KEY (`id_libro`) ) ENGINE=InnoDB AUTO_INCREMENT=1 DEFAULT CHARSET=utf8 COLLATE=utf8_spanish_ci; -- La exportación de datos fue deseleccionada. -- Volcando estructura para tabla libreria_arkix.libro_autor DROP TABLE IF EXISTS `libro_autor`; CREATE TABLE IF NOT EXISTS `libro_autor` ( `id_lib_aut` int(11) NOT NULL AUTO_INCREMENT, `libro_id` int(11) NOT NULL DEFAULT '0', `autor_id` int(11) NOT NULL DEFAULT '0', PRIMARY KEY (`id_lib_aut`), KEY `FK_autor` (`autor_id`), KEY `FK_libro` (`libro_id`), CONSTRAINT `FK_autor` FOREIGN KEY (`autor_id`) REFERENCES `autores` (`id_autor`) ON DELETE NO ACTION ON UPDATE NO ACTION, CONSTRAINT `FK_libro` FOREIGN KEY (`libro_id`) REFERENCES `libros` (`id_libro`) ON DELETE NO ACTION ON UPDATE NO ACTION ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_spanish_ci; -- La exportación de datos fue deseleccionada. -- Volcando estructura para tabla libreria_arkix.ventas DROP TABLE IF EXISTS `ventas`; CREATE TABLE IF NOT EXISTS `ventas` ( `id_venta` int(11) NOT NULL AUTO_INCREMENT, `libro_id` int(11) NOT NULL, `cliente_id` int(11) NOT NULL, `fecha_venta` date NOT NULL, `valor` double NOT NULL, `vendedor` varchar(50) COLLATE utf8_spanish_ci NOT NULL, PRIMARY KEY (`id_venta`), KEY `FK_clienteventa` (`cliente_id`), KEY `FK_libroventa` (`libro_id`), CONSTRAINT `FK_clienteventa` FOREIGN KEY (`cliente_id`) REFERENCES `clientes` (`id_cliente`) ON DELETE NO ACTION ON UPDATE NO ACTION, CONSTRAINT `FK_libroventa` FOREIGN KEY (`libro_id`) REFERENCES `libros` (`id_libro`) ON DELETE NO ACTION ON UPDATE NO ACTION ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_spanish_ci; -- La exportación de datos fue deseleccionada. /*!40101 SET SQL_MODE=IFNULL(@OLD_SQL_MODE, '') */; /*!40014 SET FOREIGN_KEY_CHECKS=IF(@OLD_FOREIGN_KEY_CHECKS IS NULL, 1, @OLD_FOREIGN_KEY_CHECKS) */; /*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */;

/* SQLyog Ultimate v11.11 (64 bit) MySQL - 5.6.26 : Database - bongyeu_vn ********************************************************************* */ /*!40101 SET NAMES utf8 */; /*!40101 SET SQL_MODE=''*/; /*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */; /*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */; /*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */; /*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */; USE `bongyeu_vn`; /*Table structure for table `article` */ DROP TABLE IF EXISTS `article`; CREATE TABLE `article` ( `id` int(11) NOT NULL AUTO_INCREMENT, `category_id` int(11) DEFAULT NULL, `name` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `label` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `slug` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `old_slugs` varchar(2000) COLLATE utf8_unicode_ci DEFAULT NULL, `content` text COLLATE utf8_unicode_ci, `description` varchar(511) COLLATE utf8_unicode_ci DEFAULT NULL, `image` varchar(511) COLLATE utf8_unicode_ci DEFAULT NULL, `image_path` varchar(511) COLLATE utf8_unicode_ci DEFAULT NULL, `page_title` varchar(511) COLLATE utf8_unicode_ci DEFAULT NULL, `meta_title` varchar(511) COLLATE utf8_unicode_ci DEFAULT NULL, `meta_keywords` varchar(511) COLLATE utf8_unicode_ci DEFAULT NULL, `meta_description` varchar(511) COLLATE utf8_unicode_ci DEFAULT NULL, `h1` varchar(511) COLLATE utf8_unicode_ci DEFAULT NULL, `view_count` int(11) DEFAULT '0', `like_count` int(11) DEFAULT '0', `comment_count` int(11) DEFAULT '0', `share_count` int(11) DEFAULT '0', `created_at` int(11) NOT NULL, `updated_at` int(11) DEFAULT NULL, `created_by` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `updated_by` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `auth_alias` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `is_hot` tinyint(1) DEFAULT NULL, `sort_order` int(11) DEFAULT NULL, `status` tinyint(2) DEFAULT NULL, `long_description` text COLLATE utf8_unicode_ci, `published_at` int(11) NOT NULL, `is_active` tinyint(1) DEFAULT NULL, `type` tinyint(2) DEFAULT NULL, PRIMARY KEY (`id`), UNIQUE KEY `slug` (`slug`), KEY `category_id` (`category_id`), CONSTRAINT `article_ibfk_1` FOREIGN KEY (`category_id`) REFERENCES `article_category` (`id`) ON DELETE SET NULL ON UPDATE CASCADE ) ENGINE=InnoDB AUTO_INCREMENT=942 DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; /*Data for the table `article` */ insert into `article`(`id`,`category_id`,`name`,`label`,`slug`,`old_slugs`,`content`,`description`,`image`,`image_path`,`page_title`,`meta_title`,`meta_keywords`,`meta_description`,`h1`,`view_count`,`like_count`,`comment_count`,`share_count`,`created_at`,`updated_at`,`created_by`,`updated_by`,`auth_alias`,`is_hot`,`sort_order`,`status`,`long_description`,`published_at`,`is_active`,`type`) values (903,180,'Veneto chính thức khai trương showroom đầu tiên tại Sài Gòn','','veneto-chinh-thuc-khai-truong-showroom-dau-tien-tai-sai-gon-2248-28243-article','{\"1476802412\":\"veneto-chinh-thuc-khai-truong-showroom-dau-tien-tai-sai-gon\"}','<p><span style=\"font-family:arial,helvetica,sans-serif; font-size:14px\"><span style=\"font-size:26px\"><strong>B</strong></span>ằng sự nỗ lực của m&igrave;nh,&nbsp;<strong>Veneto&nbsp;</strong>lu&ocirc;n cố gắng kh&ocirc;ng ngừng trong việc cải tiến chất lượng sản phẩm v&agrave; n&acirc;ng cao chất lượng dịch vụ. B&ecirc;n cạnh đ&oacute;, ch&uacute;ng t&ocirc;i lu&ocirc;n ch&uacute; trọng việc lắng nghe t&acirc;m tư, nguyện vọng của kh&aacute;ch h&agrave;ng để mở rộng mạng lưới chi nh&aacute;nh - mang sản phẩm tới gần hơn b&agrave;n tay người ti&ecirc;u d&ugrave;ng tr&ecirc;n khắp cả nước.<br />\r\n<br />\r\nThực thi sứ mệnh đ&oacute; v&agrave; cũng để thay lời cảm ơn sự ủng hộ của kh&aacute;ch h&agrave;ng ph&iacute;a Nam trong những năm qua,&nbsp;<strong>Veneto</strong>&nbsp;h&acirc;n hoan khai trương showroom thứ 9 của m&igrave;nh tại 316 L&ecirc; Văn Sỹ - Quận 3 &ndash; TP.HCM.</span><br />\r\n<span style=\"font-family:arial,helvetica,sans-serif; font-size:12px\">&nbsp;</span></p>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: center;\"><span style=\"font-size:14px\"><img alt=\"\" src=\"//veneto.vn/images/201610/v7_0701164458.jpg\" style=\"border:none; height:467px; max-width:100%; width:700px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/v3_0701164720.jpg\" style=\"border:none; height:467px; max-width:100%; width:700px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/v6_0701164538.jpg\" style=\"border:none; height:auto !important; max-width:100%\" /></span></div>\r\n\r\n<p><br />\r\n<span style=\"font-family:arial,helvetica,sans-serif; font-size:14px\">Chắc chắn đ&acirc;y l&agrave; một tin vui d&agrave;nh cho những qu&yacute; kh&aacute;ch h&agrave;ng tại S&agrave;i G&ograve;n đ&atilde; lu&ocirc;n tin tưởng v&agrave; ủng hộ c&aacute;c sản phẩm thời trang nam của Veneto. Từ nay, c&aacute;c đấng m&agrave;y r&acirc;u của S&agrave;i Th&agrave;nh kh&ocirc;ng c&ograve;n phải chờ đợi qu&atilde;ng thời gian d&agrave;i chuyển ph&aacute;t nhanh qua đường bưu điện mới được tận mắt trải nghiệm sản phẩm. C&aacute;c kh&aacute;ch h&agrave;ng đ&atilde; c&oacute; thể tới trực tiếp showroom cảm nhận chất liệu ri&ecirc;ng biệt của Veneto, thưởng thức mẫu m&atilde; của c&aacute;c bộ sưu tập v&agrave; mua sắm trực tiếp.</span><br />\r\n<span style=\"font-family:arial,helvetica,sans-serif; font-size:12px\">&nbsp;</span></p>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: center;\"><span style=\"font-size:14px\"><a href=\"//veneto.vn/images/201610/v5_0701164405.jpg\" style=\"text-decoration: none;\"><img alt=\"\" src=\"//veneto.vn/images/201610/v5_0701164405.jpg\" style=\"height:467px; max-width:100%; width:700px\" /></a></span></div>\r\n\r\n<p><br />\r\n<span style=\"font-family:arial,helvetica,sans-serif; font-size:14px\">Trong kh&ocirc;ng kh&iacute; khai trương showroom n&aacute;o nhiệt, chị&nbsp;<strong>Đinh Ngọc Phượng (</strong>GĐ trẻ của nh&atilde;n hiệu thời trang&nbsp;<strong>Veneto)</strong>&nbsp;đ&atilde; kh&ocirc;ng giấu được sự hạnh ph&uacute;c khi chia sẻ về lần Nam tiến đầu ti&ecirc;n n&agrave;y của m&igrave;nh:&nbsp;<em>&ldquo;T&ocirc;i xin được gửi lời cảm ơn ch&acirc;n th&agrave;nh sự ủng hộ của c&aacute;c kh&aacute;ch h&agrave;ng ph&iacute;a Nam trong suốt qu&atilde;ng thời gian vừa qua. Để đ&aacute;p lại sự mong mỏi của anh chị, nay Veneto đ&atilde; đặt ch&acirc;n tới S&agrave;i G&ograve;n. Với th&agrave;nh c&ocirc;ng bước đầu n&agrave;y, t&ocirc;i kh&ocirc;ng coi trọng số lượng đại l&yacute; m&agrave; Veneto sẽ mở l&agrave; bao nhi&ecirc;u? M&agrave; phải l&agrave; chất lượng của từng showroom sẽ như thế n&agrave;o? C&oacute; thực sự l&agrave;m h&agrave;i l&ograve;ng kh&aacute;ch đến mua sắm hay kh&ocirc;ng? Xuất ph&aacute;t từ hy vọng đ&oacute;, tối v&agrave; từng nh&acirc;n vi&ecirc;n của Veneto sẽ lu&ocirc;n cố gắng v&agrave; ho&agrave;n thiện m&igrave;nh để trở th&agrave;nh một doanh nghiệp kh&ocirc;ng chỉ cung cấp sản phẩm tốt &ndash; m&agrave; c&ograve;n đi đầu về chất lượng phục vụ kh&aacute;ch h&agrave;ng&rdquo;</em></span><br />\r\n<span style=\"font-family:arial,helvetica,sans-serif; font-size:12px\">&nbsp;</span></p>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: center;\"><span style=\"font-size:14px\"><em><img alt=\"\" src=\"//veneto.vn/images/201610/v1_0701164604.jpg\" style=\"border:none; height:467px; max-width:100%; width:700px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/v2_0701164629.jpg\" style=\"border:none; height:467px; max-width:100%; width:700px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/v4_0701164653.jpg\" style=\"border:none; height:467px; max-width:100%; width:700px\" /></em></span></div>\r\n\r\n<p><br />\r\n<span style=\"font-family:arial,helvetica,sans-serif; font-size:14px\">Với một chặng đường d&agrave;i x&acirc;y dựng v&agrave; ph&aacute;t triển, Veneto rất vui mừng v&igrave; lu&ocirc;n c&oacute; sự đồng h&agrave;nh, ủng hộ v&agrave; g&oacute;p &yacute; của c&aacute;c qu&yacute; kh&aacute;ch h&agrave;ng &ndash; ch&iacute;nh nhờ động lực vững v&agrave;ng ấy, ch&uacute;ng t&ocirc;i kh&ocirc;ng nhừng ho&agrave;n thiện sản phẩm cả về chất liệu, mẫu m&atilde; lẫn phong c&aacute;ch phục vụ; song h&agrave;nh với đ&oacute; l&agrave; c&aacute;c chương tr&igrave;nh ưu đ&atilde;i, hậu m&atilde;i sau b&aacute;n h&agrave;ng,&hellip;<br />\r\n<br />\r\nĐể ch&agrave;o mừng sự kiện đặc biệt n&agrave;y,&nbsp;<strong>Veneto</strong>&nbsp;gửi đến c&aacute;c qu&yacute; kh&aacute;ch h&agrave;ng đến mua sắm tại showroom Veneto 316 L&ecirc; Văn Sỹ chương tr&igrave;nh giảm gi&aacute; v&ocirc; c&ugrave;ng hấp dẫ &ldquo;Sale off 15% tất cả sản phẩm&rdquo; &ndash; k&eacute;o d&agrave;i duy nhất trong tuần đầu khai trương (từ ng&agrave;y 03/01 - 10/01/2015).</span></p>\r\n','Bằng sự nỗ lực của mình, Veneto luôn cố gắng không ngừng trong việc cải tiến chất lượng sản phẩm và nâng cao chất lượng dịch vụ. Bên cạnh đó, chúng tôi luôn chú trọng việc lắng nghe tâm tư, nguyện vọng của khách hàng để mở rộng mạng lưới chi nhánh - mang sản phẩm tới gần hơn bàn tay người tiêu dùng trên khắp cả nước','BANNER_LVS_0701202144.jpg','/201610/','Veneto chính thức khai trương showroom đầu tiên tại Sài Gòn','Veneto chính thức khai trương showroom đầu tiên tại Sài Gòn',' veneto, khai trương, Sài Gòn, TP. HCM, Lê Văn Sỹ','Bằng sự nỗ lực của mình, Veneto luôn cố gắng không ngừng trong việc cải tiến chất lượng sản phẩm và nâng cao chất lượng dịch vụ. Bên cạnh đó, chúng tôi luôn chú trọng việc lắng nghe tâm tư, nguyện vọng của khách hàng để mở rộng mạng lưới chi nhánh - mang sản phẩm tới gần hơn bàn tay người tiêu dùng trên khắp cả nước','Veneto chính thức khai trương showroom đầu tiên tại Sài Gòn',0,0,0,0,1476430873,1476802412,'quyettv','quyettv',NULL,0,NULL,NULL,NULL,1476430744,1,NULL),(904,180,'Veneto hân hoan khai trương showroom thứ 10 trên toàn quốc - 19 Phố Huế','','veneto-han-hoan-khai-truong-showroom-thu-tren-toan-quoc-–-pho-hue-2248-28244-article','{\"1476802467\":\"veneto-han-hoan-khai-truong-showroom-thu-10-tren-toan-quoc-19-pho-hue\",\"1476802512\":\"veneto-han-hoan-khai-truong-showroom-thu-tren-toan-quoc-%E2%80%93-pho-hue-2248-28244-article\"}','<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: justify;\"><span style=\"font-size:14px\">Được sự y&ecirc;u mến của h&agrave;ng ng&agrave;n kh&aacute;ch h&agrave;ng,&nbsp;<strong>Veneto&nbsp;</strong>lu&ocirc;n dẫn đầu thị trường thời trang nam với phong c&aacute;ch lịch l&atilde;m, thời thượng. C&aacute;c sản phẩm thời trang của Veneto lu&ocirc;n hướng tới sự trẻ trung v&agrave; đẳng cấp; đặc biệt l&agrave; sản phẩm suit, thời trang c&ocirc;ng sở. Để thực hiện tốt mục ti&ecirc;u phục vụ tốt nhất nhu cầu mặc đẹp của c&aacute;c đấng m&agrave;y r&acirc;u, Veneto lu&ocirc;n nỗ lực hết m&igrave;nh n&acirc;ng cao chất lượng sản phẩm &amp; dịch vụ. B&ecirc;n cạnh đ&oacute;, thương hiệu Veneto kh&ocirc;ng ngừng vươn m&igrave;nh, mở rộng mạng lưới chi nh&aacute;nh tr&ecirc;n khắp cả nước; đưa c&aacute;c sản phẩm thời trang cao cấp tới gần hơn b&agrave;n tay người ti&ecirc;u d&ugrave;ng.</span><br />\r\n<br />\r\n&nbsp;</div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: center;\"><img alt=\"\" src=\"//veneto.vn/images/201610/_MI81101_compressed_2404185051.jpg\" style=\"border:none; height:467px; max-width:100%; width:700px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/_MI81375_2404192348.jpg\" style=\"border:none; height:467px; max-width:100%; width:700px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/_MI81482_2404192513.jpg\" style=\"border:none; height:467px; max-width:100%; width:700px\" /><br />\r\n<em><span style=\"font-size:14px\">Kh&ocirc;ng kh&iacute; rộn r&agrave;ng tại lễ khai trương</span></em><br />\r\n&nbsp;</div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: justify;\"><br />\r\n<span style=\"font-size:14px\">Thực thi sứ mệnh n&agrave;y, sau một thời gian nỗ lực chuẩn bị &amp; ho&agrave;n thiện mặt bằng, chiều qua 23/04/2016, chương tr&igrave;nh ra mắt showroom&nbsp;<strong>Veneto</strong>&nbsp;thứ 10 (19 Phố Huế - H&agrave; Nội) đ&atilde; diễn ra tưng bừng, long trọng với sự tham gia của rất nhiều gương mặt nổi tiếng: diễn vi&ecirc;n &ndash; đại sứ thương hiệu&nbsp;<strong>Phạm Anh Tuấn</strong>; ch&agrave;ng hot boy - diễn vi&ecirc;n trẻ&nbsp;<strong>B&igrave;nh An</strong>; &Aacute; qu&acirc;n&nbsp;Vietnam&#39;s Next Top Model 2014&nbsp;<strong>Ti&ecirc;u Ngọc Linh</strong>;&nbsp;</span><span style=\"font-size:14px\">&Aacute; qu&acirc;n&nbsp;Vietnam&#39;s Next Top Model 2014&nbsp;<strong>Phạm Anh Duy;&nbsp;</strong><strong>Mai Tuấn Anh</strong>&nbsp;- Giải v&agrave;ng Si&ecirc;u mẫu 2015;&nbsp;<strong>Đồng &Aacute;nh Quỳnh</strong>&nbsp;- Top 5 Hoa hậu t&agrave;i năng Việt Nam 2014;&nbsp;<strong>Vũ Tiến Mạnh</strong>&nbsp;- Top 6 Nh&agrave; thiết kế thời trang Việt Nam;&nbsp;Vietnam&#39;s Next Top Model 2014<strong>&nbsp;Kim Ng&acirc;n</strong>; 2 ch&agrave;ng người mẫu trẻ&nbsp;<strong>Ho&agrave;ng Anh T&uacute;</strong>&nbsp;&amp;&nbsp;<strong>Ho&agrave;ng Gia Anh Vũ</strong>&nbsp;-&nbsp;Vietnam&#39;s Next Top Model&nbsp; 2015</span><span style=\"font-size:14px\">&nbsp;&hellip; c&ugrave;ng qu&yacute; bạn h&agrave;ng, qu&yacute; đối t&aacute;c v&agrave; c&aacute;c kh&aacute;ch h&agrave;ng th&acirc;n thiết, đ&atilde; gắn b&oacute; cũng Veneto trong suốt thời gian qua.&nbsp;<br />\r\n<br />\r\n<br />\r\n<em><strong>Một số h&igrave;nh ảnh kh&aacute;c mời tham dự chương tr&igrave;nh:</strong></em></span><br />\r\n<br />\r\n&nbsp;</div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: center;\"><em><strong><img alt=\"\" src=\"//veneto.vn/images/201610/_MI81719_2404191223.jpg\" style=\"border:none; height:467px; max-width:100%; width:700px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/_MI81795_2404191400.jpg\" style=\"border:none; height:467px; max-width:100%; width:700px\" /></strong></em><br />\r\n<br />\r\n<br />\r\n<br />\r\n<em><strong><img alt=\"\" src=\"//veneto.vn/images/201610/_MI81975_2404191448.jpg\" style=\"border:none; height:467px; max-width:100%; width:700px\" /></strong></em><br />\r\n<br />\r\n<em><strong><img alt=\"\" src=\"//veneto.vn/images/201610/_MI81312_2404191420.jpg\" style=\"border:none; height:1049px; max-width:100%; width:700px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/_MI81072_2404191527.jpg\" style=\"border:none; height:467px; max-width:100%; width:700px\" /></strong></em><br />\r\n&nbsp;</div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: justify;\"><br />\r\n<span style=\"font-size:14px\">Tọa lạc tại vị tr&iacute; đẹp c&ugrave;ng với kh&ocirc;ng gian mua sắn sang trọng, rộng r&atilde;i, showroom&nbsp;<strong>Veneto 19 Phố Huế&nbsp;</strong>đ&atilde; nhận được những lời khen ngợi kh&ocirc;ng ngớt v&agrave; những t&igrave;nh cảm y&ecirc;u mến, sự ủng hộ nhiệt t&igrave;nh của kh&aacute;ch mời &amp; c&aacute;c kh&aacute;ch h&agrave;ng tới tham quan v&agrave; mua sắm. Trong thiết kế của showroom thứ 10,&nbsp;<strong>Veneto</strong>&nbsp;mang tới một sự thay đổi đặc biệt trong diện mạo, phong c&aacute;ch decor của showroom kh&iacute; &aacute;p dụng phi&ecirc;n bản thiết kế 3.0 đầy tinh tế v&agrave; đẹp mắt. Bằng những nỗ lực v&agrave; thay đổi tuy nhỏ đ&oacute;, gi&aacute;m đốc v&agrave; đội ngũ nh&acirc;n vi&ecirc;n ch&uacute;ng t&ocirc;i hy vọng: sự phục vụ chuy&ecirc;n nghiệp kết hợp với một m&agrave;u sắc rất ri&ecirc;ng chỉ c&oacute; tại Veneto sẽ mang tới những trải nghiệm ho&agrave;n to&agrave;n mới, l&agrave;m h&agrave;i l&ograve;ng c&aacute;c qu&yacute; kh&aacute;ch h&agrave;ng.</span><br />\r\n<br />\r\n&nbsp;</div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: center;\"><span style=\"font-size:14px\"><img alt=\"\" src=\"//veneto.vn/images/201610/13007104_553406391528782_5454479457029168646_n_2404191730.jpg\" style=\"border:none; height:394px; max-width:100%; width:700px\" /></span></div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: justify;\"><br />\r\n<span style=\"font-size:14px\">Chia sẻ tại buổi lễ ra mắt, chị&nbsp;<strong>Đinh Ngọc Phượng</strong>&nbsp;&ndash; gi&aacute;m đốc C&ocirc;ng ty TNHH Thời trang Veneto t&acirc;m sự:&nbsp;<em>&ldquo;Để c&oacute; được những bước tiến quan trọng như ng&agrave;y h&ocirc;m nay, Veneto đ&atilde; kh&ocirc;ng những nỗ lực, kh&ocirc;ng ngừng cố gắng trong hoạt động nghi&ecirc;n cứu thị trường &ndash; t&igrave;m hiểu nhu cầu kh&aacute;ch h&agrave;ng v&agrave; xu hướng ăn mặc đang thịnh h&agrave;nh. V&agrave; trong sự nỗ lực ấy, ch&uacute;ng t&ocirc;i gửi lời cảm ơn ch&acirc;n th&agrave;nh nhất đến c&aacute;c qu&yacute; đối t&aacute;c gi&uacute;p Veneto ng&agrave;y c&agrave;ng phủ s&oacute;ng, đưa sản phẩm của ch&uacute;ng t&ocirc;i đến gần hơn với kh&aacute;ch h&agrave;ng. Điều đặc biệt hơn, đ&oacute; l&agrave; sự tin tưởng v&agrave; ủng hộ từ ph&iacute;a kh&aacute;ch h&agrave;ng ti&ecirc;u d&ugrave;ng; để kh&ocirc;ng phụ l&ograve;ng mong mỏi của qu&yacute; kh&aacute;ch Veneto sẽ ng&agrave;y c&agrave;ng ho&agrave;n thiện v&agrave; cho ra mắt những sản phẩm cao cấp hơn, đẹp hơn để thỏa m&atilde;n tốt nhất nhu cầu của kh&aacute;ch h&agrave;ng&rdquo;</em></span><br />\r\n&nbsp;</div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: center;\"><em><img alt=\"\" src=\"//veneto.vn/images/201610/_MI81567_2404191814.jpg\" style=\"border:none; height:1050px; max-width:100%; width:700px\" /><br />\r\n<span style=\"font-size:14px\"><NAME> - Gi&aacute;m đốc Veneto ph&aacute;t biểu tải buổi lễ</span></em><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/_MI81618_2504092416.jpg\" style=\"border:none; height:auto !important; max-width:100%; width:700px\" /><br />\r\n<em><span style=\"font-size:14px\"><NAME> - Đại l&yacute; chi nh&aacute;nh ph&aacute;t biểu cảm ơn v&agrave; ch&uacute;c mừng c&ocirc;ng ty</span></em></div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: justify;\">&nbsp;</div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: center;\"><img alt=\"\" src=\"//veneto.vn/images/201610/_MI81601_compressed_2404190022.jpg\" style=\"border:none; height:467px; line-height:20.8px; max-width:100%; width:700px\" /><br />\r\n<span style=\"font-size:14px\"><em>C&aacute;c đối t&aacute;c của Veneto n&acirc;ng ly rượu mừng</em></span></div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: justify;\"><br />\r\n<span style=\"font-size:14px\">Đồng h&agrave;nh c&ugrave;ng hoạt động khai trương Veneto 19 Phố Huế chiều qua,&nbsp;<strong>Veneto&nbsp;</strong>cho ra mắt bộ sưu tập&nbsp;<strong>&ldquo;Elegant Suit&rdquo;</strong>&nbsp;với điểm nhấn l&agrave; những gam m&agrave;u trầm huyền b&iacute;, chắc chắn sẽ m&ecirc; hoặc c&aacute;c đấng m&agrave;y r&acirc;u y&ecirc;u mến vẻ lịch l&atilde;m.</span><br />\r\n&nbsp;</div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: center;\"><img alt=\"\" src=\"//veneto.vn/images/201610/_MI81956_2404191954.jpg\" style=\"border:none; height:1050px; max-width:100%; width:700px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/_MI81985_2404192021.jpg\" style=\"border:none; height:467px; max-width:100%; width:700px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/_MI81996_2404192039.jpg\" style=\"border:none; height:467px; max-width:100%; width:700px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/_MI82000_2404192102.jpg\" style=\"border:none; height:467px; max-width:100%; width:700px\" /></div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: justify;\"><br />\r\n<span style=\"font-size:14px\">B&ecirc;n cạnh đ&oacute;, chương tr&igrave;nh mini-game của Veneto cũng d&agrave;nh tặng những phần qu&agrave; th&uacute; vị cho người tham gia. Những gi&acirc;y ph&uacute;t vui tươi, sảng kho&aacute;i để lại dấu ấn tr&ecirc;n từng khu&ocirc;n mặt kh&aacute;ch h&agrave;ng c&oacute; mặt tại buổi ra mắt.</span><br />\r\n&nbsp;</div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: center;\"><img alt=\"\" src=\"//veneto.vn/images/201610/_MI82121_2404192124.jpg\" style=\"border:none; height:467px; max-width:100%; width:700px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/_MI82064_2404192148.jpg\" style=\"border:none; height:467px; max-width:100%; width:700px\" /></div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: justify;\"><br />\r\n<span style=\"font-size:14px\">Ch&uacute;ng t&ocirc;i kỳ vọng trong tương lai gần, sẽ c&oacute; th&ecirc;m những lễ khai trương showroom tiếp theo của Veneto trải d&agrave;i tr&ecirc;n khắp chiều d&agrave;i Việt Nam để c&aacute;c kh&aacute;ch h&agrave;ng c&oacute; thể trải nghiệm sản phẩm một c&aacute;ch h&agrave;i l&ograve;ng, thuận tiện nhất.</span>\r\n\r\n<div style=\"text-align: right;\"><span style=\"font-size:14px\"><strong>Veneto &ndash; Khởi đầu cho sự th&agrave;nh c&ocirc;ng!</strong></span></div>\r\n</div>\r\n','Chiều qua 23/04/2016, chương trình ra mắt showroom Veneto thứ 10 (19 Phố Huế - Hà Nội) đã diễn ra tưng bừng','javitex_khaitruong_phohue_compressed_2707144813.jpg','/201610/','Veneto hân hoan khai trương showroom thứ 10 trên toàn quốc - 19 Phố Huế','Veneto hân hoan khai trương showroom thứ 10 trên toàn quốc - 19 Phố Huế','khai trương, Veneto 19 Phố Huế, thời trang nam, thời trang công sở, thời trang Veneto','Chiều qua 23/04/2016, chương trình ra mắt showroom Veneto thứ 10 (19 Phố Huế - Hà Nội) đã diễn ra tưng bừng','Veneto hân hoan khai trương showroom thứ 10 trên toàn quốc - 19 Phố Huế',2,0,0,0,1476431171,1476802512,'quyettv','quyettv',NULL,0,NULL,NULL,NULL,1476431044,1,NULL),(905,178,'Theo chân Veneto đến với trẻ em vùng cao','','theo-chan-veneto-den-voi-tre-em-vung-cao-2237-28245-article','{\"1476802544\":\"theo-chan-veneto-den-voi-tre-em-vung-cao\"}','<p style=\"text-align:justify\"><span style=\"font-size:14px\"><span style=\"color:rgb(0, 0, 0)\">Những ng&agrave;y cuối th&aacute;ng Hai, trong tiết trời vừa sang mới xu&acirc;n, với sự gi&uacute;p đỡ nhiệt t&igrave;nh của Hội Chữ thập đỏ tỉnh Bắc Kạn; tập thể c&aacute;n bộ, nh&acirc;n vi&ecirc;n&nbsp;<strong>C&ocirc;ng ty TNHH Thời trang&nbsp;‪Veneto</strong>‬ đ&atilde; vượt nẻo đường xa x&ocirc;i đến với x&atilde; Bản Thi.</span></span><br />\r\n&nbsp;</p>\r\n\r\n<p style=\"text-align:center\"><img alt=\"\" src=\"//veneto.vn/images/201610/veneto_backan_xuanyeuthuong0_0903102812.jpg\" style=\"border:none; height:433px; max-width:100%; width:650px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/veneto_backan_xuanyeuthuong1_0903102821.jpg\" style=\"border:none; height:464px; max-width:100%; width:650px\" /></p>\r\n\r\n<p style=\"text-align:justify\"><br />\r\n<span style=\"font-size:14px\"><span style=\"color:rgb(0, 0, 0)\">Tại bản l&agrave;ng v&ugrave;ng cao như x&atilde; Bản Thi</span></span><span style=\"color:rgb(0, 0, 0); font-size:14px\">, huyện Chợ Đồn, tỉnh Bắc Kạn chỉ</span><span style=\"font-size:14px\"><span style=\"color:rgb(0, 0, 0)\">&nbsp;c&oacute; 2 trường tiểu học v&agrave; mầm non. Trường tiểu học c&oacute; 133 em th&igrave; c&oacute; tới 83 em thuộc diện kh&oacute; khăn; trường mầm non 156 em th&igrave; c&oacute; 20 em diện ngh&egrave;o. Qua trao đổi với c&ocirc; gi&aacute;o Ph&oacute; hiệu trưởng c&ugrave;ng c&aacute;c thầy c&ocirc; gia đ&igrave;nh, c&aacute;c em nhỏ tại v&ugrave;ng cao nơi đ&acirc;y vẫn chưa thực sự coi trọng việc học tập. Một thực tại đ&aacute;ng buồn hơn đ&oacute; l&agrave; kh&ocirc;ng &iacute;t số hộ gia đ&igrave;nh cho con em nghỉ học rất sớm để lao động phụ gi&uacute;p cha mẹ l&agrave;m nương rẫy...</span></span><br />\r\n&nbsp;</p>\r\n\r\n<p style=\"text-align:center\"><img alt=\"\" src=\"//veneto.vn/images/201610/veneto_backan_xuanyeuthuong2_0903102828.jpg\" style=\"border:none; height:463px; max-width:100%; width:650px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/veneto_backan_xuanyeuthuong7_0903102959.jpg\" style=\"border:none; height:586px; max-width:100%; width:650px\" /><br />\r\n<span style=\"font-size:14px\"><span style=\"font-family:arial,helvetica,sans-serif\"><em>C&aacute;c em nhỏ tại x&atilde; Bản Thi</em></span></span><br />\r\n&nbsp;</p>\r\n\r\n<p style=\"text-align:center\"><img alt=\"\" src=\"//veneto.vn/images/201610/veneto_backan_xuanyeuthuong99_0903103234.jpg\" style=\"border:none; height:480px; max-width:100%; width:650px\" /><br />\r\n<span style=\"font-size:14px\"><em>Người mẹ kh&ocirc;ng giấu nổi niềm x&uacute;c động khi đo&agrave;n tới thăm gia đ&igrave;nh</em></span></p>\r\n\r\n<p style=\"text-align:justify\"><br />\r\n<span style=\"font-size:14px\"><span style=\"color:rgb(0, 0, 0)\">Phần lớn c&aacute;c em nhỏ tại x&atilde; Bản Thi đều c&oacute; ho&agrave;n cảnh kh&aacute; kh&oacute; khăn. Những m&oacute;n đồ nhỏ như: cặp s&aacute;ch, b&uacute;t, vở, tất, quần &aacute;o,... m&agrave; đo&agrave;n trao tặng thật sự đ&aacute;ng qu&yacute; với c&aacute;c em.&nbsp;</span></span><br />\r\n&nbsp;</p>\r\n\r\n<p style=\"text-align:center\"><img alt=\"\" src=\"//veneto.vn/images/201610/veneto_backan_xuanyeuthuong3_0903103154-2.jpg\" style=\"border:none; height:433px; max-width:100%; width:650px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/veneto_backan_xuanyeuthuong6_0903103213.jpg\" style=\"border:none; height:433px; max-width:100%; width:650px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/veneto_backan_xuanyeuthuong8_0903103220.jpg\" style=\"border:none; height:433px; max-width:100%; width:650px\" /></p>\r\n\r\n<p style=\"text-align:justify\">&nbsp;</p>\r\n\r\n<p style=\"text-align:center\"><img alt=\"\" src=\"//veneto.vn/images/201610/veneto_backan_xuanyeuthuong9_0903103228.jpg\" style=\"border:none; height:975px; max-width:100%; width:650px\" /></p>\r\n\r\n<p style=\"text-align:justify\"><br />\r\n<br />\r\n<span style=\"font-size:14px\"><span style=\"color:rgb(0, 0, 0)\">&quot;Nh&igrave;n những nụ cười vui mừng, rạng rỡ tr&ecirc;n khu&ocirc;n mặt c&aacute;c em; ngắm nh&igrave;n c&aacute;ch c&aacute;c em khoe nhau những m&oacute;n đồ mới - ch&uacute;ng t&ocirc;i như sống lại một thời thơ ấu; lắng nghe thầy c&ocirc; t&acirc;m sự về ho&agrave;n cảnh nhiều em phải nghỉ học đi nương l&agrave;m rẫy theo &yacute; của gia đ&igrave;nh khiến cả đo&agrave;n ch&uacute;ng t&ocirc;i v&ocirc; c&ugrave;ng cảm động. Vậy mới thấu hiểu những gian kh&oacute;, vất vả của c&aacute;c em v&ugrave;ng cao&quot; - một bạn nh&acirc;n vi&ecirc;n trong đo&agrave;n thiện nguyện chia sẻ.</span></span><br />\r\n&nbsp;</p>\r\n\r\n<p style=\"text-align:center\"><img alt=\"\" src=\"//veneto.vn/images/201610/veneto_backan_xuanyeuthuong4_0903103201.jpg\" style=\"border:none; color:rgb(0, 0, 0); font-size:14px; height:451px; line-height:16.08px; max-width:100%; text-align:justify; width:650px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/veneto_backan_xuanyeuthuong5_0903103101.jpg\" style=\"border:none; height:433px; max-width:100%; width:650px\" /></p>\r\n\r\n<p style=\"text-align:justify\"><br />\r\n<span style=\"font-size:14px\"><span style=\"color:rgb(0, 0, 0)\">Veneto mong rằng những m&oacute;n qu&agrave; nhỏ trong chương tr&igrave;nh</span></span><span style=\"color:rgb(0, 0, 0); font-size:14px\">&nbsp;&quot;Xu&acirc;n y&ecirc;u thương&quot; sẽ</span><span style=\"font-size:14px\"><span style=\"color:rgb(0, 0, 0)\">&nbsp;phần n&agrave;o kh&iacute;ch lệ được tinh thần học tập của c&aacute;c em, trao hi vọng cho cha mẹ &amp; ch&iacute;nh c&aacute;c em để c&oacute; thể tiếp tục cho c&aacute;c em đến trường.&nbsp;Hy vọng đ&oacute; sẽ l&agrave; nguồn động vi&ecirc;n tinh thần để c&aacute;c em chăm ngoan, tiếp tục đến trường. Cầu ch&uacute;c cho c&aacute;c em học tập tốt để trở th&agrave;nh người c&oacute; &iacute;ch cho x&atilde; hội tương lai!!&nbsp;</span></span></p>\r\n\r\n<p style=\"text-align:right\"><span style=\"font-size:14px\"><span style=\"color:rgb(0, 0, 0)\"><strong>Veneto</strong></span></span></p>\r\n','Những ngày cuối tháng Hai, tập thể cán bộ, nhân viên Công ty TNHH Thời trang ‪Veneto‬ đã vượt nẻo đường xa xôi đến với xã Bản Thi.','veneto_backan_xuanyeuthuong3_0903103154.jpg','/201610/','Theo chân Veneto đến với trẻ em vùng cao','Theo chân Veneto đến với trẻ em vùng cao','Bắc Kạn, xuân yêu thương, trẻ em, xã Bản Thi, veneto','Những ngày cuối tháng Hai, tập thể cán bộ, nhân viên Công ty TNHH Thời trang ‪Veneto‬ đã vượt nẻo đường xa xôi đến với xã Bản Thi.','Theo chân Veneto đến với trẻ em vùng cao',0,0,0,0,1476431299,1476802544,'quyettv','quyettv',NULL,0,NULL,NULL,NULL,1476431183,1,NULL),(906,180,'Veneto tưng bừng khai trương chi nhánh Hải Phòng','','veneto-tung-bung-khai-truong-chi-nhanh-hai-phong-2248-28246-article','{\"1476802572\":\"veneto-tung-bung-khai-truong-chi-nhanh-hai-phong\"}','<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: justify;\"><span style=\"font-size:16px\"><span style=\"font-family:arial,helvetica,sans-serif\">Hướng tới phong c&aacute;ch thời trang lịch l&atilde;m, thời thượng v&agrave; đẳng cấp,&nbsp;</span></span><strong>Veneto</strong><span style=\"font-size:16px\"><span style=\"font-family:arial,helvetica,sans-serif\"><strong>&nbsp;</strong>được biết đến như lựa chọn h&agrave;ng đầu d&agrave;nh cho nam giới c&ocirc;ng sở. Với mục ti&ecirc;u phục vụ tốt nhất nhu cầu mặc đẹp của nam giới,&nbsp;<strong>Veneto</strong>&nbsp;kh&ocirc;ng ngừng mở rộng mạng lưới hoạt động của m&igrave;nh tr&ecirc;n phạm vi trong v&agrave; ngo&agrave;i nước; cũng như t&igrave;m hiểu, thăm d&ograve; nhu cầu, thị hiếu thời trang của tất cả c&aacute;c đối tượng kh&aacute;ch h&agrave;ng.<br />\r\n<br />\r\nVới hy vọng mang c&aacute;c sản phẩm thời trang với phong c&aacute;ch v&agrave; trẻ trung đến gần hơn qu&yacute; kh&aacute;ch h&agrave;ng; đồng thời với phương hướng mở rộng thị trường, t&igrave;m kiếm đối t&aacute;c tiềm năng tận t&acirc;m với thương hiệu để c&ugrave;ng ph&aacute;t triển.&nbsp;<strong>Veneto</strong>&nbsp;tưng bừng khai trương Showroom mới tại miền đất Cảng Hải Ph&ograve;ng&nbsp;<em>(Địa chỉ: 52 M&ecirc; Linh- L&ecirc; Ch&acirc;n - Hải Ph&ograve;ng)</em>&nbsp;&ndash; đ&aacute;nh dấu cột mốc chi nh&aacute;nh thứ 5 tr&ecirc;n cả nước.</span></span><br />\r\n&nbsp;</div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: center;\"><img alt=\"\" src=\"//veneto.vn/images/201610/DSC_0358_1410165601.JPG\" style=\"border:none; height:641.578px; max-width:100%; width:1039px\" /><br />\r\n<em><span style=\"font-size:16px\">Gi&aacute;m đốc v&agrave; kh&aacute;ch mời cắt băng khai trương Showroom</span></em></div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: justify;\"><br />\r\n&nbsp;</div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: center;\"><img alt=\"\" src=\"//veneto.vn/images/201610/DSC_0149_1410170742.JPG\" style=\"border:none; height:718.203px; max-width:100%; width:1039px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/DSC_0226_1410170757.JPG\" style=\"border:none; height:690.922px; max-width:100%; width:1039px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/DSC_0171_1410170809.JPG\" style=\"border:none; height:777.938px; line-height:20.8px; max-width:100%; width:1039px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/DSC_0174_1410170821.JPG\" style=\"border:none; height:1435.11px; max-width:100%; width:1039px\" /><br />\r\n<em><span style=\"font-size:16px\">Một số kh&aacute;ch mời tham dự chương tr&igrave;nh khai trương</span></em></div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: justify;\"><br />\r\n<span style=\"font-size:16px\"><span style=\"font-family:arial,helvetica,sans-serif\">Sau 10 ng&agrave;y gấp r&uacute;t ho&agrave;n thiện, ng&agrave;y 10/8/2015 Showroom&nbsp;<strong>Veneto Hải Ph&ograve;ng</strong>&nbsp;đ&atilde; ch&iacute;nh thức đi v&agrave;o hoạt động. Với sự ủng hộ đ&ocirc;ng đảo của c&aacute;c vị kh&aacute;ch mời v&agrave; qu&yacute; kh&aacute;ch h&agrave;ng tới tham dự, chương tr&igrave;nh khai trương đ&atilde; diễn ra tưng bừng, n&aacute;o nhiệt.&nbsp;<strong>Veneto Hải Ph&ograve;ng</strong>&nbsp;d&agrave;nh được những lời khen ngợi v&agrave; những t&igrave;nh cảm y&ecirc;u mến của c&aacute;c kh&aacute;ch h&agrave;ng tới tham quan v&agrave; mua sắm. Với th&agrave;nh c&ocirc;ng n&agrave;y,&nbsp;<strong>Veneto&nbsp;</strong>đ&atilde; thực sự toả s&aacute;ng! Ch&uacute;ng t&ocirc;i hy vọng&nbsp;<strong>Veneto Hải Ph&ograve;ng</strong>&nbsp;c&oacute; thể đ&aacute;p ứng một c&aacute;ch tốt nhất nhu cầu mua sắm c&aacute;c sản phẩm thời trang như: veston thời trang, vest cưới, sơ mi c&ocirc;ng sở, quần &acirc;u, đồng phục c&ocirc;ng sở&hellip; của qu&yacute; kh&aacute;ch h&agrave;ng tại Hải Ph&ograve;ng v&agrave; c&aacute;c khu vực l&acirc;n cận.</span></span><br />\r\n&nbsp;</div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: center;\"><img alt=\"\" src=\"//veneto.vn/images/201610/DSC_0184_1410165845.JPG\" style=\"border:none; height:690.922px; max-width:100%; width:1039px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/DSC_0190_1410170859.JPG\" style=\"border:none; height:691.844px; max-width:100%; width:1039px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/DSC_0211_1410170913.JPG\" style=\"border:none; height:690.922px; max-width:100%; width:1039px\" /></div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: justify;\"><br />\r\n<span style=\"font-size:16px\"><span style=\"font-family:arial,helvetica,sans-serif\">Đồng h&agrave;nh c&ugrave;ng sự kiện ra mắt Showroom&nbsp;<strong>Veneto Hải Ph&ograve;ng</strong>, ch&uacute;ng t&ocirc;i d&agrave;nh tặng rất nhiều chương tr&igrave;nh ưu đ&atilde;i khai trương hấp dẫn cho kh&aacute;ch h&agrave;ng đến mua sắm. Đặc biệt l&agrave; chương tr&igrave;nh:</span></span></div>\r\n\r\n<ul>\r\n <li><span style=\"font-size:16px\"><span style=\"font-family:arial,helvetica,sans-serif\">Tặng sơmi bất kỳ khi mua 1 bộ vest</span></span></li>\r\n <li><span style=\"font-size:16px\"><span style=\"font-family:arial,helvetica,sans-serif\">Giảm 20 % cho ho&aacute; đơn tr&ecirc;n 999k</span></span></li>\r\n <li><span style=\"font-size:16px\"><span style=\"font-family:arial,helvetica,sans-serif\">Giảm gi&aacute; 10% tất cả c&aacute;c sản phẩm</span></span></li>\r\n</ul>\r\n\r\n<p><span style=\"font-family:arial,helvetica,sans-serif; font-size:12px\">&nbsp;</span></p>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: center;\"><span style=\"font-size:16px\"><span style=\"font-family:arial,helvetica,sans-serif\"><img alt=\"\" src=\"//veneto.vn/images/201610/DSC_0220_1410170927.JPG\" style=\"border:none; height:698.719px; max-width:100%; width:1039px\" /><br />\r\n<em>Đội ngũ nh&acirc;n vi&ecirc;n trẻ trung tại Veneto Hải Ph&ograve;ng</em></span></span><br />\r\n&nbsp;</div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: justify;\"><span style=\"font-size:16px\"><span style=\"font-family:arial,helvetica,sans-serif\">&nbsp;Ch&uacute;ng t&ocirc;i kỳ vọng trong tương lai gần, thương hiệu&nbsp;<strong>Veneto</strong>&nbsp;sẽ c&oacute; mặt ở khắp c&aacute;c tỉnh th&agrave;nh để c&aacute;c kh&aacute;ch h&agrave;ng c&oacute; thể trải nghiệm sản phẩm một c&aacute;ch h&agrave;i l&ograve;ng, thuận tiện nhất</span></span><br />\r\n&nbsp;</div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: right;\"><span style=\"font-size:16px\"><span style=\"font-family:arial,helvetica,sans-serif\"><strong>Veneto &ndash; Khởi đầu cho sự th&agrave;nh c&ocirc;ng!</strong></span></span></div>\r\n','Veneto tưng bừng khai trương Showroom mới tại miền đất Cả<NAME> (Địa chỉ: 52 Mê Linh- Lê Chân - Hải Phòng) – đánh dấu cột mốc chi nhánh thứ 5 trên cả nước.','khai_truong_veneto_HP_2210101446_1006233026.jpg','/201610/','Veneto tưng bừng khai trương chi nhánh Hải Phòng','Veneto tưng bừng khai trương chi nhánh Hải Phòng','','Veneto tưng bừng khai trương Showroom mới tại miền đất Cảng Hải Phòng (Địa chỉ: 52 Mê Linh- Lê Chân - Hải Phòng) – đánh dấu cột mốc chi nhánh thứ 5 trên cả nước.','Veneto tưng bừng khai trương chi nhánh Hải Phòng',0,0,0,0,1476431466,1476802572,'quyettv','quyettv',NULL,0,NULL,NULL,NULL,1476431333,1,NULL),(907,181,'Veneto ưu đãi cực shock: mua vest tặng sơmi','','veneto-uu-dai-cuc-shock-mua-vest-tang-somi-2249-28248-article','{\"1476431671\":\"veneto-uu-dai-cuc-shock-mua-vest-tang-somi\"}','<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: center;\"><img alt=\"\" src=\"//veneto.vn/images/201610/mua-vest-tang-somi-veneto_2403150611-2.jpg\" style=\"border:none; height:284px; max-width:100%; width:700px\" /></div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: justify;\">\r\n<p><br />\r\nĐể mang tới vẻ lịch l&atilde;m, kh&aacute;c biệt cho c&aacute;c ch&agrave;ng trong ng&agrave;y cưới; để anh em c&ocirc;ng sở c&oacute; th&ecirc;m những sự lựa chọn mới mỗi ng&agrave;y.</p>\r\n\r\n<p><a class=\"_58cn\" href=\"https://www.facebook.com/hashtag/veneto?source=feed_text&amp;story_id=543115659224522\" style=\"text-decoration: none; color: rgb(59, 89, 152); cursor: pointer;\"><span style=\"color:rgb(98, 122, 173)\">‪#&lrm;</span>Veneto‬</a>&nbsp;quyết định gửi tới c&aacute;c kh&aacute;ch h&agrave;ng chương tr&igrave;nh ưu đ&atilde;i đ&atilde; từng &ldquo;l&agrave;m mưa l&agrave;m gi&oacute;&rdquo; tại c&aacute;c showroom trong năm vừa qua. Cụ thể như sau:</p>\r\n\r\n<div class=\"text_exposed_show\" style=\"display: inline; color: rgb(20, 24, 35); font-family: helvetica, arial, sans-serif; font-size: 14px; line-height: 19.32px;\">\r\n<p><br />\r\nKhi mua&nbsp;<strong>01 BỘ VEST BẤT KỲ</strong>&nbsp;tại c&aacute;c showroom của Veneto, qu&yacute; kh&aacute;ch sẽ được tặng&nbsp;<strong>01 SƠMI CAO CẤP</strong></p>\r\n\r\n<p>H&agrave;ng ng&agrave;n kh&aacute;ch h&agrave;ng đ&atilde; h&agrave;i l&ograve;ng v&agrave; tin tưởng v&agrave;o sản phẩm Veston của Veneto, h&atilde;y nhanh ch&acirc;n tới Veneto mua sắm v&agrave; tận hưởng ưu đ&atilde;i cực hấp dẫn n&agrave;y&nbsp;</p>\r\n\r\n<p><br />\r\n-----<br />\r\n&nbsp;LƯU &Yacute;:<br />\r\n■ Thời gian ưu đ&atilde;i: 23/3 &ndash; 30/03/2016<br />\r\n■ Chương tr&igrave;nh &aacute;p dụng cho to&agrave;n bộ hệ thống showroom tr&ecirc;n to&agrave;n quốc<br />\r\n■ Chương tr&igrave;nh kh&ocirc;ng &aacute;p dụng chung với thẻ VIP v&agrave; c&aacute;c dịch vụ khuyến m&atilde;i kh&aacute;c.</p>\r\n\r\n<p><br />\r\n-----<br />\r\n&nbsp;ALBUM VESTON ĐẲNG CẤP CỦA VENETO xem tại:<br />\r\n■ Autumn 2015 Collection:&nbsp;<a href=\"https://www.facebook.com/l.php?u=https%3A%2F%2Fgoo.gl%2FlONjLI&amp;h=pAQEZlrGdAQHXDjzflyvI1ATgPjvodz9IL0SeFnmrlFHcKQ&amp;enc=AZPIeyfhv-khjJZs_d0EYkTeXMbzxcmS9bdC4WDCZprUmhLgv688JgBurSrmMPSBJ6qledNPo1bbT6pOueFg7oauIiYxWjxiFmC32YISFDf6mnz0h_hqvO9eKaBtu4DXLUVZAYD7kaCJOcHTD06itEJ4XrEOPg1K077yJ5GopA_OZxQKlIUJhAHnKHIlW8-8LrQ_5xZDI6-BpCz6EYuk4hv8&amp;s=1\" rel=\"nofollow\" style=\"text-decoration: none; color: rgb(59, 89, 152); cursor: pointer;\" target=\"_blank\">https://goo.gl/lONjLI</a><br />\r\n■ Winter 2015 Collection:&nbsp;<a href=\"https://goo.gl/Mt7BUe\" rel=\"nofollow\" style=\"text-decoration: none; color: rgb(59, 89, 152); cursor: pointer;\" target=\"_blank\">https://goo.gl/Mt7BUe</a><br />\r\n■ Veneto Wedding Fashion Show 2015:&nbsp;<a href=\"https://www.facebook.com/l.php?u=https%3A%2F%2Fgoo.gl%2FGGhokc&amp;h=kAQGJBNT-AQFh2bsmrWWWeVQARWpp7lyB2nFbGYR4NctQlA&amp;enc=AZN18Zb5pdyUsKvF9kVRR4RTUu_5ulnSiYoTp5q7NIo_v8j4ibT5-tWSobb_6LncHooMSGNfqZUbPRTjE6jj8uxaeG2A6AufvpIFpJCzucfPxRauMFrJXxpxOCGZdpodlQu5PIUyrBuvgn-QHinDM5FR2_tUrL5RqvSBNbO1JRdJ5GlYLMSM5Phn4bBYuJe7eu80jkSm4LbfXLmNdxZsojwX&amp;s=1\" rel=\"nofollow\" style=\"text-decoration: none; color: rgb(59, 89, 152); cursor: pointer;\" target=\"_blank\">https://goo.gl/GGhokc</a></p>\r\n</div>\r\n</div>\r\n','Veneto‬ quyết định gửi tới các khách hàng chương trình ưu đãi đã từng “làm mưa làm gió” tại các showroom trong năm vừa qua.','mua-vest-tang-somi-veneto_2403150611.jpg','/201610/','Veneto ưu đãi cực shock: mua vest tặng sơmi','Veneto ưu đãi cực shock: mua vest tặng sơmi','ưu đãi, khuyến mãi, promotion, veneto, thời trang nam, công sở, vest cưới','Veneto‬ quyết định gửi tới các khách hàng chương trình ưu đãi đã từng “làm mưa làm gió” tại các showroom trong năm vừa qua.','Veneto ưu đãi cực shock: mua vest tặng sơmi',0,0,0,0,1476431596,1476431671,'quyettv','quyettv',NULL,0,NULL,NULL,NULL,1476431471,1,NULL),(908,181,'Veneto dành tặng ưu đãi \"cực khủng\" cho khách hàng dịp cuối năm','','-2249-28249-article','{\"1476802632\":\"veneto-danh-tang-uu-dai-cuc-khung-cho-khach-hang-dip-cuoi-nam\"}','<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; clear: both; text-align: justify;\"><span style=\"font-size:14px\"><span style=\"font-size:26px\"><strong>M</strong></span>ột năm nữa lại sắp đi qua. Nh&acirc;n dịp Gi&aacute;ng sinh v&agrave; năm mới đang tới thật gần,&nbsp;<strong>Veneto</strong>&nbsp;đ&atilde; update th&ecirc;m thật nhiều sản phẩm mới tại c&aacute;c hệ thống showroom; c&ugrave;ng với h&agrave;ng trăm items cực hấp dẫn để phục vụ nhu cầu mua sắm của kh&aacute;ch h&agrave;ng nh&acirc;n dịp cuối năm 2015.&nbsp;</span><span style=\"font-size:14px\">Để nh&acirc;n đ&ocirc;i sự hấp dẫn của kh&ocirc;ng kh&iacute; mua sắm dịp cuối năm,&nbsp;<strong>Veneto&nbsp;</strong>triển khai chương tr&igrave;nh ưu đ&atilde;i hấp dẫn nhất 2015 để kh&aacute;ch h&agrave;ng thỏa sức mua sắm; v&agrave; cũng để thay lời cảm ơn tới qu&yacute; kh&aacute;ch h&agrave;ng th&acirc;n th&acirc;n thiết đ&atilde; ủng hộ&nbsp;<strong>Veneto</strong>&nbsp;trong suốt một năm vừa qua.</span></div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: justify;\"><span style=\"font-size:14px\">&nbsp;<br />\r\nKhi mua 01 bộ vest bất kỳ từ ng&agrave;y&nbsp;<strong>15/12 - 30/12/2015</strong>&nbsp;tại c&aacute;c hệ thống showroom của Veneto tr&ecirc;n to&agrave;n quốc, qu&yacute; kh&aacute;ch sẽ được tặng ngay c&aacute;c sản phẩm cao cấp:</span></div>\r\n\r\n<ul>\r\n <li><span style=\"font-size:14px\">01 &aacute;o sơmi cao cấp</span></li>\r\n <li><span style=\"font-size:14px\">01 caravat thời thượng</span></li>\r\n <li><span style=\"font-size:14px\">01 d&acirc;y lưng thời trang</span></li>\r\n <li><span style=\"font-size:14px\">01 thẻ VIP giảm gi&aacute; 10% tại c&aacute;c hệ thống showroom của Veneto tại H&agrave; Nội</span></li>\r\n</ul>\r\n\r\n<p><span style=\"font-family:arial,helvetica,sans-serif; font-size:14px\">B&ecirc;n cạnh đ&oacute;, Veneto gửi tới qu&yacute; kh&aacute;ch h&agrave;ng ưu đ&atilde;i v&ocirc; c&ugrave;ng hấp dẫn từ c&aacute;c thương hiệu li&ecirc;n kết:</span></p>\r\n\r\n<ul>\r\n <li><span style=\"font-size:14px\">01 Voucher trị gi&aacute; 1.000.000đ từ thương hiệu v&aacute;y cưới Linh B&ugrave;i Bridal</span></li>\r\n <li><span style=\"font-size:14px\">01 Voucher trị gi&aacute; 1.000.000đ từ Thời trang Dạ hội Queen Style</span></li>\r\n <li><span style=\"font-size:14px\">01 thẻ vip 10% sử dụng tại c&aacute;c hệ thống tại H&agrave; Nội của Veneto</span></li>\r\n</ul>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: center;\"><br />\r\n<span style=\"font-size:14px\"><img alt=\"\" src=\"//veneto.vn/images/201610/VENETO_POST_1712144132-2.jpg\" style=\"border:none; height:358px; max-width:100%; width:700px\" /></span></div>\r\n\r\n<p><span style=\"font-family:arial,helvetica,sans-serif; font-size:14px\">&nbsp;</span></p>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: justify;\"><span style=\"font-size:14px\">Sử dụng những chất liệu tốt nhất, ch&uacute; trọng tới sự thoải m&aacute;i của ph&aacute;i mạnh khi mặc; kết hợp với đ&ocirc;i tay t&agrave;i hoa của những thợ may l&agrave;nh nghề; c&aacute;c sản phẩm veston của Veneto lu&ocirc;n nhận được sự ưa chuộng v&agrave; đ&aacute;nh gi&aacute; cao từ người ti&ecirc;u d&ugrave;ng. Veneto cam kết mang tới cho kh&aacute;ch h&agrave;ng một vẻ ngo&agrave;i lịch l&atilde;m, sang trọng, tinh tế v&agrave; kh&ocirc;ng k&eacute;m phần trẻ trung, thời thượng</span></div>\r\n','Một năm nữa lại sắp đi qua. Nhân dịp Giáng sinh và năm mới đang tới thật gần, Veneto đã update thêm thật nhiều sản phẩm mới tại các hệ thống showroom; cùng với hàng trăm items cực hấp dẫn để phục vụ nhu cầu mua sắm của khách hàng nhân dịp cuối năm 2015.','VENETO_POST_1712144132.jpg','/201610/','Veneto dành tặng ưu đãi \"cực khủng\" cho khách hàng dịp cuối năm','Veneto dành tặng ưu đãi \"cực khủng\" cho khách hàng dịp cuối năm',' khuyến mại, ưu đãi, veneto, quà tặng, 2015','Một năm nữa lại sắp đi qua. Nhân dịp Giáng sinh và năm mới đang tới thật gần, Veneto đã update thêm thật nhiều sản phẩm mới tại các hệ thống showroom; cùng với hàng trăm items cực hấp dẫn để phục vụ nhu cầu mua sắm của khách hàng nhân dịp cuối năm 2015.','Veneto dành tặng ưu đãi \"cực khủng\" cho khách hàng dịp cuối năm',0,0,0,0,1476431899,1476802632,'quyettv','quyettv',NULL,0,NULL,NULL,NULL,1476431699,1,NULL),(909,182,'VENETO FASHION SHOW - HONEY MOON & WEDDING PERFECT 2015','','veneto-fashion-show-honey-moon-wedding-perfect-2252-28275-article','{\"1476432037\":\"veneto-fashion-show-honey-moon-wedding-perfect-2015\"}','<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: justify;\"><span style=\"font-size:16px\"><strong>VENETO</strong>&nbsp;được biết đến như một trong c&aacute;c thương hiệu thời trang Nam cao cấp h&agrave;ng đầu H&agrave; Nội.&nbsp;Với phong c&aacute;ch lịch l&atilde;m, thời thượng v&agrave; đẳng cấp ,&nbsp;<strong>VENETO</strong>&nbsp;ra mắt Bộ sưu t&acirc;p vest cưới thời trang s&agrave;nh điệu .​<br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/veneto_fashion_show_2_0310124230.jpg\" style=\"border:none; height:733.781px; max-width:100%; width:1039px\" /><br />\r\n<br />\r\n<span style=\"color:rgb(20, 24, 35); font-family:helvetica,arial,sans-serif\"><strong>VENETO</strong>&nbsp;ấp ủ kế hoạch từ đầu năm, đ&atilde; tham gia l&agrave; phải chương tr&igrave;nh lớn v&agrave; ho&agrave;nh tr&aacute;ng nhất miền bắc tại kh&aacute;ch sạn 5 sao Melia H&agrave; Nội.&nbsp;Mọi thứ chuẩn bị đ&atilde; xong chỉ c&ograve;n chờ đến ng&agrave;y tr&igrave;nh diễn Bộ sưu tập mới tại Triển l&atilde;m cưới lớn nhất miền Bắc với gian h&agrave;ng đặc biệt.&nbsp;</span><span style=\"color:rgb(20, 24, 35); font-family:helvetica,arial,sans-serif\">Cơ hội cho c&ocirc; d&acirc;u ch&uacute; rể tại miền Bắc đến tham dự v&agrave; hưởng nhiều ưu đ&atilde;i với c&aacute;c thương hiệu cưới lớn nhất, uy t&iacute;n nhất!&nbsp;<br />\r\n<br />\r\nĐặc biệt,&nbsp;<strong>VENETO</strong>&nbsp;c&ograve;n t&agrave;i trợ tặng qu&agrave; cho c&ocirc; d&acirc;u, ch&uacute; rể ở chương tr&igrave;nh&nbsp;<strong>CẶP Đ&Ocirc;I HO&Agrave;N HẢO</strong>&nbsp;l&agrave; 10 bộ vest trị gi&aacute; l&ecirc;n tới: 30.000.000đ&nbsp;</span></span><br />\r\n&nbsp;</div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: center;\"><iframe align=\"middle\" frameborder=\"1\" height=\"500\" name=\"VENETO FASHION SHOW - HONEY MOON &amp; WEDDING PERFECT 2015.\" scrolling=\"yes\" src=\"http://www.youtube.com/embed/MsFlvciQiEc\" style=\"max-width: 100%;\" width=\"700\"></iframe></div>\r\n','VENETO được biết đến như một trong các thương hiệu thời trang Nam cao cấp hàng đầu Hà Nội. Với phong cách lịch lãm, thời thương và đẳng cấp , VENETO ra mắt BST vest cưới thời trang sành điệu','veneto_fashion_show_0310122440.jpg','/201610/','VENETO FASHION SHOW - HONEY MOON & WEDDING PERFECT 2015','VENETO FASHION SHOW - HONEY MOON & WEDDING PERFECT 2015','VENETO, FASHION SHOW','VENETO được biết đến như một trong các thương hiệu thời trang Nam cao cấp hàng đầu Hà Nội. Với phong cách lịch lãm, thời thương và đẳng cấp , VENETO ra mắt BST vest cưới thời trang sành điệu','VENETO FASHION SHOW - HONEY MOON & WEDDING PERFECT 2015',0,0,0,0,1476432019,1476432113,'quyettv','quyettv',NULL,0,NULL,NULL,NULL,1476431904,1,NULL),(910,178,'5 lý do bạn nên mua vest tại Veneto','','-ly-do-ban-nen-mua-vest-tai-veneto-2237-28276-article','{\"1476802685\":\"5-ly-do-ban-nen-mua-vest-tai-veneto\"}','<p><img alt=\"\" src=\"//veneto.vn/images/201610/BANNER_VENETO_0911170449.jpg\" style=\"border:none; font-family:arial,helvetica,sans-serif; font-size:12px; height:284px; line-height:20.8px; max-width:100%; text-align:center; width:700px\" /><br style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: center;\" />\r\n<br style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: center;\" />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/POST_1___1_0911171248.jpg\" style=\"border:none; font-family:arial,helvetica,sans-serif; font-size:12px; height:458px; line-height:20.8px; max-width:100%; text-align:center; width:700px\" /><br style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: center;\" />\r\n<br style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: center;\" />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/POST_2___2_0911171302.jpg\" style=\"border:none; font-family:arial,helvetica,sans-serif; font-size:12px; height:458px; line-height:20.8px; max-width:100%; text-align:center; width:700px\" /><br style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: center;\" />\r\n<br style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: center;\" />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/POST_3___3_0911171313.jpg\" style=\"border:none; font-family:arial,helvetica,sans-serif; font-size:12px; height:458px; line-height:20.8px; max-width:100%; text-align:center; width:700px\" /></p>\r\n','','VENETO_POST_1712144132-3.jpg','/201610/','5 lý do bạn nên mua vest tại Veneto','5 lý do bạn nên mua vest tại Veneto','vest, veneto, lý do, ưu đãi','','5 lý do bạn nên mua vest tại Veneto',0,0,0,0,1476432318,1476802685,'quyettv','quyettv',NULL,0,NULL,NULL,NULL,1476432115,1,NULL),(911,180,'Veneto - Giá trị không nằm ở những gì nhận lại','','veneto-–-gia-tri-khong-nam-o-nhung-gi-nhan-lai-2248-28434-article','{\"1476802732\":\"veneto-gia-tri-khong-nam-o-nhung-gi-nhan-lai\"}','<p>&nbsp;</p>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: center;\"><img alt=\"\" src=\"//veneto.vn/images/201610/Untitled-1_0805130720_1506124220.jpg\" style=\"border:none; height:373px; max-width:100%; width:919px\" /></div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: justify;\"><br />\r\n<span style=\"font-size:14px\">L&agrave; một thương hiệu thời trang kh&aacute; &ldquo;non trẻ&rdquo; tr&ecirc;n thị trường thời trang d&agrave;nh cho ph&aacute;i mạnh, tuy vậy, chỉ với 3 năm ngắn ngủi&nbsp;<strong>Veneto</strong>&nbsp;đ&atilde; c&oacute; những bước đi ấn tượng khi khi li&ecirc;n tục nhận được những lời khen ngợi, những phản hồi t&iacute;ch cực từ c&aacute;c qu&yacute; kh&aacute;ch h&agrave;ng nam giới về chất lượng sản phẩm v&agrave; quy tr&igrave;nh hậu m&atilde;i sau b&aacute;n h&agrave;ng; c&ugrave;ng với đ&oacute; l&agrave; những chương tr&igrave;nh t&ocirc;n vinh doanh nghiệp, giải thưởng danh gi&aacute; khẳng định chất lượng sản phẩm &ndash; dịch vụ&hellip;.</span><br />\r\n&nbsp;</div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: justify;\"><span style=\"font-size:14px\">Nh&igrave;n lại chặng đường 3 năm hoạt động,&nbsp;<strong>Veneto</strong>&nbsp;lu&ocirc;n đặt &ldquo;chất lượng sản phẩm&rdquo; v&agrave; &ldquo;sự h&agrave;i l&ograve;ng của kh&aacute;ch h&agrave;ng&rdquo; l&agrave;m trọng t&acirc;m để vươn m&igrave;nh v&agrave; ph&aacute;t triển. T&iacute;nh đến thời điểm hiện nay, Veneto hiện đang sở hữu hệ thống gồm 10 showroom trải d&agrave;i từ Bắc v&agrave;o Nam, tất cả đều đồng bộ h&oacute;a về kh&ocirc;ng gian, định hướng phong c&aacute;ch thời trang cũng như chất lượng phục vụ. Với những sự đầu tư đ&oacute;, Veneto kỳ vọng sẽ lu&ocirc;n l&agrave; địa chỉ mua sắm tin cậy, l&agrave; h&igrave;nh ảnh đầu ti&ecirc;n trong t&acirc;m tr&iacute; kh&aacute;ch h&agrave;ng khi nghĩ về thời trang nam.</span><br />\r\n<br />\r\n&nbsp;</div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: center;\"><img alt=\"\" src=\"//veneto.vn/images/201610/_MI82000_2404192102-2.jpg\" style=\"border:none; height:467px; line-height:20.8px; max-width:100%; width:700px\" /></div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: justify;\"><br />\r\n<span style=\"font-size:14px\">C&ugrave;ng với đ&oacute; l&agrave; những bộ sưu tập thời trang c&ocirc;ng phu mang sắc m&agrave;u lịch l&atilde;m, đẳng cấp được chuẩn bị kỹ lưỡng bởi b&agrave;n tay của đội ngũ sản xuất &ndash; thiết kế l&acirc;u năm kinh nghiệm &ndash; tạo n&ecirc;n t&ecirc;n tuổi v&agrave; thương hiệu&nbsp;<strong>Veneto</strong>&nbsp;như ng&agrave;y nay. Song h&agrave;nh với đ&oacute; l&agrave; những show diễn thời trang ho&agrave;nh tr&aacute;ng được đầu tư, d&agrave;n dựng một c&aacute;ch c&ocirc;ng phu, chuy&ecirc;n nghiệp&hellip; Với tất cả những hoạt động đ&oacute;, ch&uacute;ng t&ocirc;i thực hiện với một t&acirc;m nguyện duy nhất: Mang đến cho c&aacute;c qu&yacute; kh&aacute;ch h&agrave;ng những trải nghiệm ch&acirc;n thực nhất, ho&agrave;n hảo nhất về chất liệu, những kiểu d&aacute;ng &ndash; mẫu m&atilde; mới nhất của sản phẩm &ndash; m&agrave; kh&ocirc;ng phải những g&igrave; h&agrave;o nho&aacute;ng chỉ thấy tr&ecirc;n quảng c&aacute;o.</span><br />\r\n&nbsp;</div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: center;\"><img alt=\"\" src=\"//veneto.vn/images/201610/K_N_9847_1506124704.jpg\" style=\"border:none; height:467px; max-width:100%; width:700px\" /></div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: justify;\">&nbsp;</div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: center;\"><img alt=\"\" src=\"//veneto.vn/images/201610/11919548_467765710092851_1840072311963666259_n_1506120149.jpg\" style=\"border:none; height:388px; max-width:100%; width:700px\" /></div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: justify;\">&nbsp;</div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: center;\"><img alt=\"\" src=\"//veneto.vn/images/201610/11863387_466769376859151_6931202683106693559_n_1506120213.jpg\" style=\"border:none; height:960px; max-width:100%; width:640px\" /></div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: justify;\"><br />\r\n<span style=\"font-size:14px\">Trong suốt những năm vừa qua, ngo&agrave;i việc ch&uacute; trọng ổn đinh hệ thống showroom &ndash; đẩy mạnh hoạt động kinh doanh &amp; ph&aacute;t triển xa hơn tới c&aacute;c thị trường mới,&nbsp;<strong>Veneto</strong>&nbsp;thực sự ch&uacute; trọng tới những gi&aacute; trị, lợi &iacute;ch m&agrave; một doang nghiệp mới như ch&uacute;ng t&ocirc;i đ&oacute;ng g&oacute;p cho x&atilde; hội.&nbsp;<strong>&ldquo;Gi&aacute; trị kh&ocirc;ng nằm ở những g&igrave; nhận lại&rdquo;</strong>&nbsp;&ndash; đ&oacute; l&agrave; một trong những triết l&yacute; kinh doanh được đội ngũ s&aacute;ng lập v&agrave; điều h&agrave;nh của&nbsp;<strong>Veneto</strong>&nbsp;đặt l&ecirc;n h&agrave;ng đầu. Ch&uacute;ng t&ocirc;i đề cao &ndash; ưu ti&ecirc;n h&agrave;ng đầu cho những đ&oacute;ng g&oacute;p gi&uacute;p &iacute;ch cho x&atilde; hội v&agrave; cộng đồng được tạo ra từ ch&iacute;nh hiệu quả kinh doanh của c&ocirc;ng ty &ndash; đ&oacute; ch&iacute;nh l&agrave; nguồn s&aacute;ng, l&agrave; động lực th&uacute;c đẩy đội ngũ nh&acirc;n vi&ecirc;n của&nbsp;<strong>Veneto</strong>&nbsp;kh&ocirc;ng ngừng cố gắng v&agrave; s&aacute;ng tạo.<br />\r\n<br />\r\nThực thi những gi&aacute; trị tr&ecirc;n v&agrave; coi đ&oacute; như nền tảng của mọi hoạt động,&nbsp;<strong>Veneto</strong>&nbsp;đ&atilde; t&iacute;ch cực tham gia hỗ trợ cho c&aacute;c chương tr&igrave;nh ngoại kh&oacute;a của c&aacute;c bạn sinh vi&ecirc;n;&nbsp;<strong>Veneto</strong>&nbsp;đ&atilde; đồng h&agrave;nh &ndash; hỗ trợ tối đa cho c&aacute;c hoạt động của c&aacute;c bạn học sinh, sinh vi&ecirc;n tại c&aacute;c trường: ĐH Ngoại thương, ĐH Kinh doanh &ndash; C&ocirc;ng nghệ, ĐH Thương mại,&hellip; Ch&uacute;ng t&ocirc;i hy vọng những đ&oacute;ng g&oacute;p nhỏ n&agrave;y sẽ phần n&agrave;o sẽ gi&uacute;p cho những ước mơ, ho&agrave;i b&atilde;o của c&aacute;c bạn sinh vi&ecirc;n trẻ t&agrave;i năng &amp; đầy nhiệt huyết sẽ c&oacute; cơ hội bay cao, vươn xa hơn nữa...</span><br />\r\n&nbsp;</div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: center;\"><img alt=\"\" src=\"//veneto.vn/images/201610/13407056_631868140303727_6610739110171612419_n_1506115614.jpg\" style=\"border:none; height:903px; max-width:100%; width:600px\" /></div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: justify;\">&nbsp;</div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: center;\"><img alt=\"\" src=\"//veneto.vn/images/201610/13417498_1227938517230740_2952979418119670298_n_1506115644.jpg\" style=\"border:none; height:960px; max-width:100%; width:960px\" /></div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: justify;\"><br />\r\n<span style=\"font-size:14px\">Đội ngũ CBNV v&agrave; c&aacute;c gi&aacute;m đốc chi nh&aacute;nh của&nbsp;<strong>Veneto&nbsp;</strong>cũng đ&atilde; c&oacute; những chuyến thiện nguyện tới c&aacute;c bản l&agrave;ng v&ugrave;ng cao: lắng nghe v&agrave; sẻ chia những c&acirc;u chuyện của người d&acirc;n miền n&uacute;i &amp; d&agrave;nh tặng những phần qu&agrave;, những khoản kinh ph&iacute; hỗ trợ cho c&aacute;c gia đ&igrave;nh ngh&egrave;o, c&aacute;c em nhỏ c&oacute; ho&agrave;n cảnh kh&oacute; khăn,&hellip; được tr&iacute;ch ra từ ch&iacute;nh doanh số b&aacute;n h&agrave;ng của to&agrave;n bộ hệ thống đại l&yacute;. Ch&uacute;ng t&ocirc;i thực hiện điều đ&oacute; với t&acirc;m nguyện:&nbsp;<strong>&ldquo;Gi&aacute; trị kh&ocirc;ng nằm ở những g&igrave; nhận lại&rdquo;</strong>.</span><br />\r\n&nbsp;</div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: center;\"><img alt=\"\" src=\"//veneto.vn/images/201610/veneto_backan_xuanyeuthuong99_0903103234-2.jpg\" style=\"border:none; height:709px; max-width:100%; width:960px\" /></div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: justify;\">&nbsp;</div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: center;\"><img alt=\"\" src=\"//veneto.vn/images/201610/veneto_backan_xuanyeuthuong5_0903103101-2.jpg\" style=\"border:none; height:640px; max-width:100%; width:960px\" /></div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: justify;\"><br />\r\n<span style=\"font-size:14px\">Với những bước tiến tiếp theo của Veneto trong tương lai, ch&uacute;ng t&ocirc;i hy vọng sẽ c&oacute; cơ hội đến gần hơn với những mảnh đời bất hạnh, cống hiến nhiều hơn cho cộng đồng v&agrave; to&agrave;n thể x&atilde; hội.</span></div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: center;\"><img alt=\"\" src=\"//veneto.vn/images/201610/Untitled-1_0805130720_1506124220.jpg\" style=\"border:none; height:373px; max-width:100%; width:919px\" /></div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: justify;\"><br />\r\n<span style=\"font-size:14px\">L&agrave; một thương hiệu thời trang kh&aacute; &ldquo;non trẻ&rdquo; tr&ecirc;n thị trường thời trang d&agrave;nh cho ph&aacute;i mạnh, tuy vậy, chỉ với 3 năm ngắn ngủi&nbsp;<strong>Veneto</strong>&nbsp;đ&atilde; c&oacute; những bước đi ấn tượng khi khi li&ecirc;n tục nhận được những lời khen ngợi, những phản hồi t&iacute;ch cực từ c&aacute;c qu&yacute; kh&aacute;ch h&agrave;ng nam giới về chất lượng sản phẩm v&agrave; quy tr&igrave;nh hậu m&atilde;i sau b&aacute;n h&agrave;ng; c&ugrave;ng với đ&oacute; l&agrave; những chương tr&igrave;nh t&ocirc;n vinh doanh nghiệp, giải thưởng danh gi&aacute; khẳng định chất lượng sản phẩm &ndash; dịch vụ&hellip;.</span><br />\r\n&nbsp;</div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: justify;\"><span style=\"font-size:14px\">Nh&igrave;n lại chặng đường 3 năm hoạt động,&nbsp;<strong>Veneto</strong>&nbsp;lu&ocirc;n đặt &ldquo;chất lượng sản phẩm&rdquo; v&agrave; &ldquo;sự h&agrave;i l&ograve;ng của kh&aacute;ch h&agrave;ng&rdquo; l&agrave;m trọng t&acirc;m để vươn m&igrave;nh v&agrave; ph&aacute;t triển. T&iacute;nh đến thời điểm hiện nay, Veneto hiện đang sở hữu hệ thống gồm 10 showroom trải d&agrave;i từ Bắc v&agrave;o Nam, tất cả đều đồng bộ h&oacute;a về kh&ocirc;ng gian, định hướng phong c&aacute;ch thời trang cũng như chất lượng phục vụ. Với những sự đầu tư đ&oacute;, Veneto kỳ vọng sẽ lu&ocirc;n l&agrave; địa chỉ mua sắm tin cậy, l&agrave; h&igrave;nh ảnh đầu ti&ecirc;n trong t&acirc;m tr&iacute; kh&aacute;ch h&agrave;ng khi nghĩ về thời trang nam.</span><br />\r\n<br />\r\n&nbsp;</div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: center;\"><img alt=\"\" src=\"//veneto.vn/images/201610/_MI82000_2404192102-2.jpg\" style=\"border:none; height:467px; line-height:20.8px; max-width:100%; width:700px\" /></div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: justify;\"><br />\r\n<span style=\"font-size:14px\">C&ugrave;ng với đ&oacute; l&agrave; những bộ sưu tập thời trang c&ocirc;ng phu mang sắc m&agrave;u lịch l&atilde;m, đẳng cấp được chuẩn bị kỹ lưỡng bởi b&agrave;n tay của đội ngũ sản xuất &ndash; thiết kế l&acirc;u năm kinh nghiệm &ndash; tạo n&ecirc;n t&ecirc;n tuổi v&agrave; thương hiệu&nbsp;<strong>Veneto</strong>&nbsp;như ng&agrave;y nay. Song h&agrave;nh với đ&oacute; l&agrave; những show diễn thời trang ho&agrave;nh tr&aacute;ng được đầu tư, d&agrave;n dựng một c&aacute;ch c&ocirc;ng phu, chuy&ecirc;n nghiệp&hellip; Với tất cả những hoạt động đ&oacute;, ch&uacute;ng t&ocirc;i thực hiện với một t&acirc;m nguyện duy nhất: Mang đến cho c&aacute;c qu&yacute; kh&aacute;ch h&agrave;ng những trải nghiệm ch&acirc;n thực nhất, ho&agrave;n hảo nhất về chất liệu, những kiểu d&aacute;ng &ndash; mẫu m&atilde; mới nhất của sản phẩm &ndash; m&agrave; kh&ocirc;ng phải những g&igrave; h&agrave;o nho&aacute;ng chỉ thấy tr&ecirc;n quảng c&aacute;o.</span><br />\r\n&nbsp;</div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: center;\"><img alt=\"\" src=\"//veneto.vn/images/201610/K_N_9847_1506124704.jpg\" style=\"border:none; height:467px; max-width:100%; width:700px\" /></div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: justify;\">&nbsp;</div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: center;\"><img alt=\"\" src=\"//veneto.vn/images/201610/11919548_467765710092851_1840072311963666259_n_1506120149.jpg\" style=\"border:none; height:388px; max-width:100%; width:700px\" /></div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: justify;\">&nbsp;</div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: center;\"><img alt=\"\" src=\"//veneto.vn/images/201610/11863387_466769376859151_6931202683106693559_n_1506120213.jpg\" style=\"border:none; height:960px; max-width:100%; width:640px\" /></div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: justify;\"><br />\r\n<span style=\"font-size:14px\">Trong suốt những năm vừa qua, ngo&agrave;i việc ch&uacute; trọng ổn đinh hệ thống showroom &ndash; đẩy mạnh hoạt động kinh doanh &amp; ph&aacute;t triển xa hơn tới c&aacute;c thị trường mới,&nbsp;<strong>Veneto</strong>&nbsp;thực sự ch&uacute; trọng tới những gi&aacute; trị, lợi &iacute;ch m&agrave; một doang nghiệp mới như ch&uacute;ng t&ocirc;i đ&oacute;ng g&oacute;p cho x&atilde; hội.&nbsp;<strong>&ldquo;Gi&aacute; trị kh&ocirc;ng nằm ở những g&igrave; nhận lại&rdquo;</strong>&nbsp;&ndash; đ&oacute; l&agrave; một trong những triết l&yacute; kinh doanh được đội ngũ s&aacute;ng lập v&agrave; điều h&agrave;nh của&nbsp;<strong>Veneto</strong>&nbsp;đặt l&ecirc;n h&agrave;ng đầu. Ch&uacute;ng t&ocirc;i đề cao &ndash; ưu ti&ecirc;n h&agrave;ng đầu cho những đ&oacute;ng g&oacute;p gi&uacute;p &iacute;ch cho x&atilde; hội v&agrave; cộng đồng được tạo ra từ ch&iacute;nh hiệu quả kinh doanh của c&ocirc;ng ty &ndash; đ&oacute; ch&iacute;nh l&agrave; nguồn s&aacute;ng, l&agrave; động lực th&uacute;c đẩy đội ngũ nh&acirc;n vi&ecirc;n của&nbsp;<strong>Veneto</strong>&nbsp;kh&ocirc;ng ngừng cố gắng v&agrave; s&aacute;ng tạo.<br />\r\n<br />\r\nThực thi những gi&aacute; trị tr&ecirc;n v&agrave; coi đ&oacute; như nền tảng của mọi hoạt động,&nbsp;<strong>Veneto</strong>&nbsp;đ&atilde; t&iacute;ch cực tham gia hỗ trợ cho c&aacute;c chương tr&igrave;nh ngoại kh&oacute;a của c&aacute;c bạn sinh vi&ecirc;n;&nbsp;<strong>Veneto</strong>&nbsp;đ&atilde; đồng h&agrave;nh &ndash; hỗ trợ tối đa cho c&aacute;c hoạt động của c&aacute;c bạn học sinh, sinh vi&ecirc;n tại c&aacute;c trường: ĐH Ngoại thương, ĐH Kinh doanh &ndash; C&ocirc;ng nghệ, ĐH Thương mại,&hellip; Ch&uacute;ng t&ocirc;i hy vọng những đ&oacute;ng g&oacute;p nhỏ n&agrave;y sẽ phần n&agrave;o sẽ gi&uacute;p cho những ước mơ, ho&agrave;i b&atilde;o của c&aacute;c bạn sinh vi&ecirc;n trẻ t&agrave;i năng &amp; đầy nhiệt huyết sẽ c&oacute; cơ hội bay cao, vươn xa hơn nữa...</span><br />\r\n&nbsp;</div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: center;\"><img alt=\"\" src=\"//veneto.vn/images/201610/13407056_631868140303727_6610739110171612419_n_1506115614.jpg\" style=\"border:none; height:903px; max-width:100%; width:600px\" /></div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: justify;\">&nbsp;</div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: center;\"><img alt=\"\" src=\"//veneto.vn/images/201610/13417498_1227938517230740_2952979418119670298_n_1506115644.jpg\" style=\"border:none; height:960px; max-width:100%; width:960px\" /></div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: justify;\"><br />\r\n<span style=\"font-size:14px\">Đội ngũ CBNV v&agrave; c&aacute;c gi&aacute;m đốc chi nh&aacute;nh của&nbsp;<strong>Veneto&nbsp;</strong>cũng đ&atilde; c&oacute; những chuyến thiện nguyện tới c&aacute;c bản l&agrave;ng v&ugrave;ng cao: lắng nghe v&agrave; sẻ chia những c&acirc;u chuyện của người d&acirc;n miền n&uacute;i &amp; d&agrave;nh tặng những phần qu&agrave;, những khoản kinh ph&iacute; hỗ trợ cho c&aacute;c gia đ&igrave;nh ngh&egrave;o, c&aacute;c em nhỏ c&oacute; ho&agrave;n cảnh kh&oacute; khăn,&hellip; được tr&iacute;ch ra từ ch&iacute;nh doanh số b&aacute;n h&agrave;ng của to&agrave;n bộ hệ thống đại l&yacute;. Ch&uacute;ng t&ocirc;i thực hiện điều đ&oacute; với t&acirc;m nguyện:&nbsp;<strong>&ldquo;Gi&aacute; trị kh&ocirc;ng nằm ở những g&igrave; nhận lại&rdquo;</strong>.</span><br />\r\n&nbsp;</div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: center;\"><img alt=\"\" src=\"//veneto.vn/images/201610/veneto_backan_xuanyeuthuong99_0903103234-2.jpg\" style=\"border:none; height:709px; max-width:100%; width:960px\" /></div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: justify;\">&nbsp;</div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: center;\"><img alt=\"\" src=\"//veneto.vn/images/201610/veneto_backan_xuanyeuthuong5_0903103101-2.jpg\" style=\"border:none; height:640px; max-width:100%; width:960px\" /></div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height: 20.8px; text-align: justify;\"><br />\r\n<span style=\"font-size:14px\">Với những bước tiến tiếp theo của Veneto trong tương lai, ch&uacute;ng t&ocirc;i hy vọng sẽ c&oacute; cơ hội đến gần hơn với những mảnh đời bất hạnh, cống hiến nhiều hơn cho cộng đồng v&agrave; to&agrave;n thể x&atilde; hội.</span></div>\r\n','Với những bước tiến tiếp theo của Veneto trong tương lai, chúng tôi hy vọng sẽ có cơ hội đến gần hơn với những mảnh đời bất hạnh, cống hiến nhiều hơn cho cộng đồng và toàn thể xã hội.','Slide_01_2106145818.jpg','/201610/','Veneto - Giá trị không nằm ở những gì nhận lại','Veneto - Giá trị không nằm ở những gì nhận lại','veneto, thời trang nam veneto, lịch lãm, sang trọng, thời trang công sở','Với những bước tiến tiếp theo của Veneto trong tương lai, chúng tôi hy vọng sẽ có cơ hội đến gần hơn với những mảnh đời bất hạnh, cống hiến nhiều hơn cho cộng đồng và toàn thể xã hội.','Veneto - Giá trị không nằm ở những gì nhận lại',0,0,0,0,1476432454,1476802732,'quyettv','quyettv',NULL,0,NULL,NULL,NULL,1476432347,1,NULL),(912,180,'Veneto cháy hết mình trong chuyến du lịch Hạ Long','','veneto-chay-het-minh-trong-chuyen-du-lich-ha-long-2248-29071-article','{\"1476802755\":\"veneto-chay-het-minh-trong-chuyen-du-lich-ha-long\"}','<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; text-align: justify;\"><span style=\"font-size:14px\"><span style=\"color:rgb(0, 0, 0)\">Tạm g&aacute;c lại hoạt động kinh doanh - b&aacute;n h&agrave;ng tất bật của c&aacute;c showroom, trong 02 ng&agrave;y 7 &amp; 8/09/2016 vừa qua, Veneto đ&atilde; tổ chức th&agrave;nh c&ocirc;ng chương tr&igrave;nh nghỉ m&aacute;t cho to&agrave;n thể CBNV tại th&agrave;nh phố biển Hạ Long.</span></span><br />\r\n&nbsp;</div>\r\n\r\n<p style=\"text-align:justify\"><span style=\"font-size:14px\"><span style=\"color:rgb(0, 0, 0)\">Với mục đ&iacute;ch mang đến những gi&acirc;y ph&uacute;t nghỉ ngơi, thư gi&atilde;n sau những ng&agrave;y l&agrave;m việc căng thẳng, đồng thời để thay lời cảm ơn cho những nỗ lực phấn đấu của CBNV Veneto d&agrave;nh cho c&ocirc;ng ty trong suốt một năm qua, Veneto đ&atilde; quyết định tổ chức chuyến du lịch kh&aacute;m ph&aacute; th&agrave;nh phố biển Hạ Long cho to&agrave;n thể nh&acirc;n vi&ecirc;n. Tham gia chuyến du lịch c&ograve;n c&oacute; sự g&oacute;p mặt của đại diện c&aacute;c qu&yacute; đại l&yacute; - những người đ&atilde; kề vai s&aacute;t c&aacute;nh, đ&oacute;ng g&oacute;p kh&ocirc;ng &iacute;t v&agrave;o mọi hoạt động kinh doanh của c&ocirc;ng ty.</span></span></p>\r\n\r\n<p>&nbsp;</p>\r\n\r\n<p style=\"text-align:center\"><span style=\"font-size:14px\"><span style=\"color:rgb(0, 0, 0)\"><img alt=\"\" src=\"//veneto.vn/images/201610/_MG_0673veneto_dulich_2016_1309163747-2.jpg\" style=\"border:none; height:469px; max-width:100%; width:700px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/_MG_0868veneto_dulich_2016_1309163822.jpg\" style=\"border:none; height:469px; max-width:100%; width:700px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/_MG_0763veneto_dulich_2016_1309170030.jpg\" style=\"border:none; height:469px; max-width:100%; width:700px\" /></span></span><br />\r\n&nbsp;</p>\r\n\r\n<p style=\"text-align:justify\"><span style=\"font-size:14px\"><span style=\"color:rgb(0, 0, 0)\">Tổ chức du lịch h&egrave; l&agrave; một hoạt động&nbsp;thường ni&ecirc;n&nbsp;của Veneto nhằm tạo sự đo&agrave;n kết, gắn b&oacute; c&aacute;c bộ phận, ph&ograve;ng ban trong c&ocirc;ng ty. B&ecirc;n cạnh đ&oacute;, đ&acirc;y cũng l&agrave; dịp để mọi người c&oacute; cơ hội sinh hoạt chung, hiểu biết nhiều hơn về c&aacute;c đồng nghiệp của m&igrave;nh ngo&agrave;i những giờ ph&uacute;t tập trung cho c&ocirc;ng việc.</span></span></p>\r\n\r\n<p>&nbsp;</p>\r\n\r\n<p style=\"text-align:center\"><img alt=\"\" src=\"//veneto.vn/images/201610/_MG_0611veneto_dulich_2016_1309162439.jpg\" style=\"border:none; height:467px; line-height:20.8px; max-width:100%; width:700px\" /></p>\r\n\r\n<p>&nbsp;</p>\r\n\r\n<p style=\"text-align:center\"><span style=\"font-size:14px\"><span style=\"color:rgb(0, 0, 0)\"><img alt=\"\" src=\"//veneto.vn/images/201610/_MG_0695veneto_dulich_2016_1309163728.jpg\" style=\"border:none; height:469px; max-width:100%; width:700px\" /></span></span><br />\r\n&nbsp;</p>\r\n\r\n<p><span style=\"font-size:14px\"><span style=\"color:rgb(0, 0, 0)\">CBNV của Veneto đ&atilde; c&oacute; cơ hội trải nghiệm tại khu du lịch B&atilde;i Ch&aacute;y&amp; tham quan, kh&aacute;m ph&aacute; vịnh Hạ Long,...&nbsp;Nh&acirc;n vi&ecirc;n của Veneto hầu hết l&agrave; c&aacute;c bạn trẻ v&ocirc; c&ugrave;ng năng động v&agrave; s&aacute;ng tạo, vậy n&ecirc;n trong suốt chuyến đi, kh&ocirc;ng kh&iacute; dường như trở n&ecirc;n s&ocirc;i động v&agrave; cuồng nhiệt hơn bao giờ hết bởi những tiếng cười rộn r&atilde;, những tiếng h&ograve; h&eacute;t cổ vũ v&agrave; những tr&ograve; chơi team-bulding tưng bừng tr&ecirc;n b&atilde;i biển.</span></span><br />\r\n&nbsp;</p>\r\n\r\n<p style=\"text-align:center\"><img alt=\"\" src=\"//veneto.vn/images/201610/_MG_0719veneto_dulich_2016_1309165533.jpg\" style=\"border:none; height:467px; max-width:100%; width:700px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/_MG_0732veneto_dulich_2016_1309165541.jpg\" style=\"border:none; height:467px; max-width:100%; width:700px\" /><br />\r\n<em>C&aacute;c th&agrave;nh vi&ecirc;n h&ograve;a m&igrave;nh v&agrave;o c&aacute;c tr&ograve; chơi team-bulding</em><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/_MG_0741veneto_dulich_2016_1309165559.jpg\" style=\"border:none; height:467px; max-width:100%; width:700px\" /><br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/_MG_0746veneto_dulich_2016_1309165615.jpg\" style=\"border:none; height:469px; max-width:100%; width:700px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/_MG_0749veneto_dulich_2016_1309165623.jpg\" style=\"border:none; height:469px; max-width:100%; width:700px\" /><br />\r\n<em>Tinh thần bất khuất của hội &quot;anh em&quot; v&agrave; hội &quot;chị em&quot; trước khi bắt đầu tr&ograve; chơi</em><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/_MG_0752veneto_dulich_2016_1309165830.jpg\" style=\"border:none; height:467px; max-width:100%; width:700px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/_MG_0759veneto_dulich_2016_1309165851.jpg\" style=\"border:none; height:469px; max-width:100%; width:700px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/_MG_0757veneto_dulich_2016_1309165911.jpg\" style=\"border:none; height:469px; max-width:100%; width:700px\" /><br />\r\n<em>Khi &quot;cuộc chiến cam go&quot; b&ugrave;ng nổ</em><br />\r\n&nbsp;</p>\r\n\r\n<p style=\"text-align:center\"><img alt=\"\" src=\"//veneto.vn/images/201610/_MG_0773veneto_dulich_2016_1309170159.jpg\" style=\"border:none; height:469px; max-width:100%; width:700px\" /><br />\r\n<em>D&ugrave; chịu phạt v&igrave; l&agrave; đội thua nhưng vẫn rất tươi ạ</em><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/_MG_0829veneto_dulich_2016_1309170336.jpg\" style=\"border:none; color:rgb(0, 0, 0); font-size:14px; height:469px; line-height:22.4px; max-width:100%; width:700px\" /><br />\r\n<em>Kh&ocirc;ng biết điểm đến của team n&agrave;y sẽ l&agrave; ở đ&acirc;u đ&acirc;y =))</em><br />\r\n&nbsp;</p>\r\n\r\n<p><span style=\"font-family:arial,helvetica,sans-serif; font-size:14px\"><span style=\"color:rgb(0, 0, 0)\">Bạn&nbsp;<strong>Tuấn Anh</strong>&nbsp;(Ph&ograve;ng Kinh doanh) chia sẻ cảm nhận:&nbsp;<em>&quot;Cứ mỗi lần du lịch c&ugrave;ng Veneto, m&igrave;nh lại cảm thấy v&ocirc; c&ugrave;ng h&aacute;o hức. Suốt cả chặng đường d&agrave;i tinh thần đồng đội của c&aacute;c th&agrave;nh vi&ecirc;n đều rất tuyệt vời, c&aacute;c bạn vui hết m&igrave;nh v&agrave; chơi hết m&igrave;nh, kh&ocirc;ng c&ograve;n những sự e d&egrave; hai ngại ng&ugrave;ng g&igrave; hết giữa c&aacute;c nh&acirc;n vi&ecirc;n với nhau. C&aacute; nh&acirc;n m&igrave;nh thấy rất hạnh ph&uacute;c &nbsp;v&agrave; m&igrave;nh coi Veneto như một ng&ocirc;i nh&agrave; thứ 2 vậy&quot;</em></span></span><br />\r\n<br />\r\n<span style=\"font-family:arial,helvetica,sans-serif; font-size:12px\">&nbsp;</span></p>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; text-align: center;\"><img alt=\"\" src=\"//veneto.vn/images/201610/_MG_0691veneto_dulich_2016_1309165322.jpg\" style=\"border:none; height:469px; line-height:20.8px; max-width:100%; width:700px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/_MG_0676veneto_dulich_2016_1309165307.jpg\" style=\"border:none; height:469px; line-height:20.8px; max-width:100%; width:700px\" /><br />\r\n<em>Cả đo&agrave;n cũng lưu lại những khoảnh khắc funny b&atilde;i biển</em></div>\r\n\r\n<p><br />\r\n<br />\r\n<span style=\"font-family:arial,helvetica,sans-serif; font-size:14px\"><span style=\"color:rgb(0, 0, 0)\">Cũng kh&ocirc;ng k&eacute;m phần h&agrave;o hứng,&nbsp;<strong>Kiều Anh</strong>&nbsp;(Nh&acirc;n vi&ecirc;n b&aacute;n h&agrave;ng của trụ sở Qu&aacute;n Th&aacute;nh) n&oacute;i về chuyến du lịch:<em>&nbsp; M&igrave;nh cũng c&aacute;c bạn kh&ocirc;ng thể ngồi y&ecirc;n với những tiếng h&ograve; reo cổ vũ của cả đo&agrave;n. Nhờ những chuyến du lịch như thế n&agrave;y m&agrave; m&igrave;nh cảm thấy c&aacute;c th&agrave;nh vi&ecirc;n trong Veneto gắn kết với nhau hơn. Rất mong đợi đến những chuyến đi chơi xa tiếp theo của Veneto (cười)</em></span></span></p>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; text-align: center;\"><br />\r\n<span style=\"font-size:14px\"><span style=\"color:rgb(0, 0, 0)\"><img alt=\"\" src=\"//veneto.vn/images/201610/_MG_0861veneto_dulich_2016_1309170517.jpg\" style=\"border:none; height:469px; max-width:100%; width:700px\" /></span></span><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/_MG_0821veneto_dulich_2016_1309170252.jpg\" style=\"border:none; color:rgb(0, 0, 0); font-size:14px; height:469px; line-height:22.4px; max-width:100%; width:700px\" /><br />\r\n<span style=\"font-size:14px\"><span style=\"color:rgb(0, 0, 0)\"><em>M&agrave;u &aacute;o v&agrave;ng nổi bật kh&ocirc;ng lẫn v&agrave;o đ&acirc;u được của #TeamVeneto</em><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/_MG_1088veneto_dulich_2016_1309170612.jpg\" style=\"border:none; height:469px; max-width:100%; width:700px\" /><br />\r\n<em>C&aacute;c anh em say m&ecirc; với c&aacute;c m&ocirc;n thể thao</em></span></span></div>\r\n\r\n<p><br />\r\n<span style=\"font-family:arial,helvetica,sans-serif; font-size:14px\"><span style=\"color:rgb(0, 0, 0)\"><span style=\"font-family:arial,helvetica,sans-serif\">C&oacute; thể n&oacute;i chuyến du lịch h&egrave; tuy chỉ k&eacute;o d&agrave;i 2 ng&agrave;y 1 đ&ecirc;m nhưng đ&atilde; để lại những kỷ niệm đẹp, nhiều niềm vui v&agrave; t&igrave;nh cảm đối với mỗi th&agrave;nh vi&ecirc;n trong đại gia đ&igrave;nh Veneto. Veneto mong muốn sau những chuyến đi như thế n&agrave;y n&agrave;y, mỗi th&agrave;nh vi&ecirc;n sẽ lu&ocirc;n cố gắng phấn đấu để ho&agrave;n th&agrave;nh thật tốt nhiệm vụ được giao, lu&ocirc;n đo&agrave;n kết gi&uacute;p đỡ nhau trong c&ocirc;ng việc cũng như x&acirc;y dựng Veneto trở th&agrave;nh một thương hiệu mạnh tr&ecirc;n thương trường thời trang nam.</span></span></span></p>\r\n','Có thể nói chuyến du lịch hè tuy chỉ kéo dài 2 ngày 1 đêm nhưng đã để lại những kỷ niệm đẹp, nhiều niềm vui và tình cảm đối với mỗi thành viên trong đại gia đình Veneto. ','_MG_0673veneto_dulich_2016_1309163747.jpg','/201610/','Veneto cháy hết mình trong chuyến du lịch Hạ Long','Veneto cháy hết mình trong chuyến du lịch Hạ Long','thời trang nam, veneto, vest cưới, vest thời trang, lịch lãm, sang trọng, du lịch','Có thể nói chuyến du lịch hè tuy chỉ kéo dài 2 ngày 1 đêm nhưng đã để lại những kỷ niệm đẹp, nhiều niềm vui và tình cảm đối với mỗi thành viên trong đại gia đình Veneto. ','Veneto cháy hết mình trong chuyến du lịch Hạ Long',0,0,0,0,1476432667,1476802755,'quyettv','quyettv',NULL,0,NULL,NULL,NULL,1476432489,1,NULL),(913,181,'Veneto khai trương showroom tại siêu thị thời trang Mai Ngọc','','veneto-tung-bung-khai-truong-showroom-tai-sieu-thi-thoi-trang-mai-ngoc-2248-28433-article','','<p><span style=\"font-family:arial,helvetica,sans-serif; font-size:14px\"><span style=\"color:rgb(34, 34, 34); font-family:arial,sans-serif\">V&agrave;o l&uacute;c 19h ng&agrave;y 12/06/2016 vừa qua,<strong>Veneto</strong>&nbsp;h&acirc;n hoan khai trương showroom tại&nbsp;<strong>Si&ecirc;u thị thời trang Mai Ngọc</strong>&nbsp;<em>(địa chỉ: Số 2 L&ecirc; Huy Tu&acirc;n - Tĩnh Gia - Thanh H&oacute;a)</em>. B</span></span><span style=\"color:rgb(34, 34, 34); font-family:arial,sans-serif; font-size:14px\">ước đi n&agrave;y của Veneto mang tới một cơ hội trải nghiệm thuận tiện cho c&aacute;c kh&aacute;ch h&agrave;ng; c&aacute;c sản phẩm thời trang của&nbsp;<strong>Veneto&nbsp;</strong>ch&iacute;nh thức được cung cấp trực tiếp tới c&aacute;c kh&aacute;ch h&agrave;ng tại miền Trung - đ&aacute;p lại sự mong mỏi của những kh&aacute;ch h&agrave;ng tại Thanh H&oacute;a đ&atilde; từng sử dụng v&agrave; y&ecirc;u mến c&aacute;c sản phẩm thời trang của Veneto.<br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/13413059_1782046442029007_8725109955950769255_n_2006113027.jpg\" style=\"border:none; height:720px; max-width:100%; width:960px\" /></span></p>\r\n\r\n<div style=\"font-size: small; color: rgb(34, 34, 34); font-family: arial, sans-serif; line-height: normal;\">\r\n<div>&nbsp;</div>\r\n\r\n<div><span style=\"font-size:14px\">Với hơn 3 năm x&acirc;y dựng v&agrave; ph&aacute;t triển tr&ecirc;n thị trường, đến nay thương hiệu thời trang nam&nbsp;<strong>Veneto&nbsp;</strong>lu&ocirc;n kh&ocirc;ng ngừng vươn l&ecirc;n những tầm cao mới để khẳng định vị tr&iacute; của m&igrave;nh trong &nbsp;l&ograve;ng kh&aacute;c h&agrave;ng cũng như để xứng đ&aacute;ng với niềm tin v&agrave; sự kỳ vọng của c&aacute;c qu&yacute; kh&aacute;ch h&agrave;ng đ&atilde; tin d&ugrave;ng v&agrave; ủng hộ c&aacute;c sản phẩm của ch&uacute;ng t&ocirc;i.&nbsp;<br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/13319770_1033975713365722_2327485192433445283_n_2006113048.jpg\" style=\"border:none; height:720px; max-width:100%; width:960px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/13450095_1024283150980751_7847515951919229601_n_2106160358.jpg\" style=\"border:none; height:546px; max-width:100%; width:818px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/13417648_1033975616699065_8834071901609837174_n_2006113006-2.jpg\" style=\"border:none; height:720px; max-width:100%; width:960px\" /></span><br />\r\n<br />\r\n<span style=\"font-size:14px\">Với thế mạnh về chất liệu vải cao cấp được lựa chọn kỹ lưỡng, những đường n&eacute;t thiết kế tinh tế - c&ugrave;ng sự am hiểu s&acirc;u sắc về thời trang v&agrave; nhu cầu l&agrave;m đẹp của người ti&ecirc;u d&ugrave;ng, c&aacute;c trang phục của&nbsp;<strong>Veneto</strong>&nbsp;lu&ocirc;n được đ&aacute;nh gi&aacute; l&agrave; sang trọng - lịch l&atilde;m, với kiểu d&aacute;ng hiện đại, đ&aacute;p ứng tốt nhu cầu của ph&aacute;i mạnh.<br />\r\n<br />\r\n<strong>Veneto</strong>&nbsp;hy vọng rằng, c&aacute;c qu&yacute; kh&aacute;ch h&agrave;ng nam giới tại xứ Thanh sẽ c&oacute; th&ecirc;m những chọn lựa mới khi đến với gian h&agrave;ng của Veneto tại Si&ecirc;u thị thời trang Mai Ngọc.</span></div>\r\n</div>\r\n','Veneto mang tới một cơ hội trải nghiệm thuận tiện cho các khách hàng; các sản phẩm thời trang của Veneto chính thức được cung cấp trực tiếp tới các khách hàng tại miền Trung','13417648_1033975616699065_8834071901609837174_n_2006113006.jpg','/201610/','Veneto khai trương showroom tại siêu thị thời trang Mai Ngọc','Veneto khai trương showroom tại siêu thị thời trang Mai Ngọc',' thời trang nam Veneto, lịch lãm, sang trọng, khai trương, siêu thị thời trang Mai Ngọc','Veneto mang tới một cơ hội trải nghiệm thuận tiện cho các khách hàng; các sản phẩm thời trang của Veneto chính thức được cung cấp trực tiếp tới các khách hàng tại miền Trung','Veneto khai trương showroom tại siêu thị thời trang Mai Ngọc',0,0,0,0,1476432839,NULL,'quyettv',NULL,NULL,0,NULL,NULL,NULL,1476432681,1,NULL),(914,182,'Veneto Fashion Show 2016','','veneto-fashion-show-2252-28894-article','','<p><span style=\"color:rgb(0, 0, 0); font-family:arial,helvetica,sans-serif; font-size:12px\"><span style=\"font-size:14px\">Như một sự h&ograve;a quyện ngọt ng&agrave;o giữa những bộ vest cưới sang trọng, lịch l&atilde;m c&ugrave;ng những th&ocirc;ng điệp l&atilde;ng mạn về t&igrave;nh y&ecirc;u đ&ocirc;i lứa,&nbsp;<strong>Veneto Fashion Show 2016</strong>&nbsp;được đầu tư kỹ lưỡng, chuẩn bị c&ocirc;ng phu bằng cả t&acirc;m huyết của những người y&ecirc;u thời trang &ndash; say m&ecirc; với vẻ đẹp của những bộ c&aacute;nh sang trọng. Những đường n&eacute;t thiết kế vest hiện đại tạo n&ecirc;n h&igrave;nh ảnh người đ&agrave;n &ocirc;ng th&agrave;nh đạt, cuốn h&uacute;t s&aacute;nh vai b&ecirc;n c&ocirc; d&acirc;u rạng rỡ, xinh đẹp.</span></span><br />\r\n<span style=\"font-family:arial,helvetica,sans-serif; font-size:12px\">&nbsp;</span></p>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; text-align: center;\"><span style=\"color:rgb(0, 0, 0)\"><span style=\"font-size:14px\"><img alt=\"\" src=\"//veneto.vn/images/201610/veneto_fashion_show_2016_2908142423.jpg\" style=\"border:none; height:343px; max-width:100%; width:700px\" /></span></span></div>\r\n\r\n<p><br />\r\n<span style=\"color:rgb(0, 0, 0); font-family:arial,helvetica,sans-serif; font-size:12px\"><span style=\"font-size:14px\">Với định hướng ti&ecirc;n phong v&agrave; khẳng định vị thế dẫn đầu trong những xu hướng của m&ugrave;a cưới những th&aacute;ng cuối năm. Veneto gửi đến qu&yacute; kh&aacute;ch h&agrave;ng trong show diễn những mẫu vest ho&agrave;n to&agrave;n mới, đa dang về m&agrave;u sắc: từ những tone m&agrave;u trầm như xanh, xanh đen, n&acirc;u, x&aacute;m,.. cho đến những m&agrave;u sắc trẻ trung, đang l&agrave; xu hướng thịnh h&agrave;nh tr&ecirc;n những s&agrave;n diễn h&agrave;ng đầu thế giới như: pastel, m&agrave;u be, m&agrave;u trắng, x&aacute;m,&hellip; l&agrave;m to&aacute;t l&ecirc;n kh&iacute; ph&aacute;ch của một đấng m&agrave;y r&acirc;u mang trong m&igrave;nh uy lực v&agrave; sự nam t&iacute;nh căng tr&agrave;n.</span></span><br />\r\n<span style=\"font-family:arial,helvetica,sans-serif; font-size:12px\">&nbsp;</span></p>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; text-align: center;\"><span style=\"color:rgb(0, 0, 0)\"><span style=\"font-size:14px\"><img alt=\"\" src=\"//veneto.vn/images/201610/SOO_3484_2908150034.jpg\" style=\"border:none; height:467px; max-width:100%; width:700px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/SOO_3413_2908150107.jpg\" style=\"border:none; height:467px; max-width:100%; width:700px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/SOO_3364_2908150134.jpg\" style=\"border:none; height:467px; max-width:100%; width:700px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/SOO_3438_2908150449.jpg\" style=\"border:none; height:467px; max-width:100%; width:700px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/SOO_3382_2908150509.jpg\" style=\"border:none; height:467px; max-width:100%; width:700px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/SOO_3518_2908150358.jpg\" style=\"border:none; height:467px; max-width:100%; width:700px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/SOO_3464_2908150537.jpg\" style=\"border:none; height:467px; max-width:100%; width:700px\" /></span></span><br />\r\n&nbsp;</div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; text-align: justify;\"><span style=\"color:rgb(0, 0, 0)\"><span style=\"font-size:14px\">Với mong muốn mang những trải nghiệm thời trang ho&agrave;n to&agrave;n mới, đồng thời tạo n&ecirc;n một c&aacute;i nh&igrave;n kh&aacute;c biệt về thời trang bằng những sản phẩm thời trang c&oacute; t&iacute;nh ứng dụng cao; thương hiệu thời trang Veneto đang dần khẳng định vị thế của m&igrave;nh tr&ecirc;n thị trường thời trang nam v&agrave; đạt được những giải thưởng nhất định về chất lượng sản phẩm - dịch vụ.<br />\r\n<br />\r\nVới tinh thần l&agrave;m việc trẻ trung, s&aacute;ng tạo kh&ocirc;ng ngừng của bộ phận thiết kế - sản xu&aacute;t; sự tận t&acirc;m, chất lượng phục vụ được đ&agrave;o tạo chuy&ecirc;n nghiệp của nh&acirc;n vi&ecirc;n b&aacute;n h&agrave;ng&hellip; l&agrave; những yếu tố g&oacute;p phần l&agrave;m n&ecirc;n sự lớn mạnh của một trong những thương hiệu thời trang TOP đầu như Veneto hiện nay.</span></span></div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; text-align: center;\"><br />\r\n<br />\r\n<span style=\"color:rgb(0, 0, 0)\"><span style=\"font-size:14px\"><img alt=\"\" src=\"//veneto.vn/images/201610/SOO_3560_2908150601.jpg\" style=\"border:none; height:467px; max-width:100%; width:700px\" /></span></span></div>\r\n','Đến với triển lãm cưới Wedding des Art 2016, toàn bộ ekip của Veneto đầu tư kỹ lưỡng về mặt ý tưởng và thực thi, chuẩn bị công phu bằng cả tâm huyết của những người yêu thời trang – say mê với vẻ đẹp của những bộ cánh sang trọng.','veneto_fashion_show_2016.jpg','/201610/','Veneto Fashion Show 2016','Veneto Fashion Show 2016','thời trang nam, veneto, vest cưới, vest thời trang, lịch lãm, sang trọng','Đến với triển lãm cưới Wedding des Art 2016, toàn bộ ekip của Veneto đầu tư kỹ lưỡng về mặt ý tưởng và thực thi, chuẩn bị công phu bằng cả tâm huyết của những người yêu thời trang – say mê với vẻ đẹp của những bộ cánh sang trọng.','Veneto Fashion Show 2016',1,0,0,0,1476433030,NULL,'quyettv',NULL,NULL,0,NULL,NULL,NULL,1476432842,1,NULL),(915,179,'Trở thành chú rể sang trọng, lịch lãm cùng vest cưới Veneto','','tro-thanh-chu-re-sang-trong-lich-lam-cung-vest-cuoi-veneto-2250-29107-article','','<p><span style=\"color:rgb(0, 0, 0); font-family:arial,helvetica,sans-serif; font-size:12px\"><span style=\"font-size:14px\"><strong>Tại triển l&atilde;m cưới Wedding des Art vừa qua, thương hiệu thời trang nam Veneto đ&atilde; mang đến Bộ sưu tập Vest cưới 2016 Elegant Suit với phong c&aacute;ch sang trọng, lịch l&atilde;m, biến người mặc th&agrave;nh những ch&uacute; rể thời thượng, nổi bật.&nbsp;</strong><br />\r\n<br />\r\nVeneto ra mắt bộ sưu tập vest cưới Elegant suit d&agrave;nh cho ch&uacute; rể trong m&ugrave;a cưới 2016. Với nguồn cảm hứng từ h&igrave;nh tượng ch&uacute; rể th&agrave;nh đạt, sang trọng, lịch l&atilde;m, c&aacute;c mẫu thiết kế trong bộ sưu tập hứa hẹn mang đến những trải nghiệm th&uacute; vị c&ugrave;ng vẻ ngo&agrave;i ho&agrave;n hảo cho c&aacute;c &ldquo;t&acirc;n lang&rdquo; trong m&ugrave;a cưới năm nay.</span></span><br />\r\n<span style=\"font-family:arial,helvetica,sans-serif; font-size:12px\">&nbsp;</span></p>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; text-align: center;\"><span style=\"color:rgb(0, 0, 0)\"><span style=\"font-size:14px\"><img alt=\"\" src=\"//veneto.vn/images/201610/SOO_2960_compressed_2309083253.jpg\" style=\"border:none; height:467px; max-width:100%; width:700px\" /></span></span><br />\r\n&nbsp;</div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; text-align: center;\"><span style=\"color:rgb(0, 0, 0)\"><span style=\"font-size:14px\"><img alt=\"\" src=\"//veneto.vn/images/201610/SOO_3024_compressed_2309083324.jpg\" style=\"border:none; height:469px; max-width:100%; width:700px\" /></span></span></div>\r\n\r\n<p><br />\r\n<span style=\"color:rgb(0, 0, 0); font-family:arial,helvetica,sans-serif; font-size:12px\"><span style=\"font-size:14px\">C&aacute;c mẫu thiết kế của Elegant Suit l&agrave; sự h&agrave;i h&ograve;a giữa lối thiết kế tối giản về chi tiết, nhấn mạnh v&agrave;o c&aacute;c yếu tố phụ kiện như khăn c&agrave;i t&uacute;i ngực, ve &aacute;o, khuy c&agrave;i&hellip; Với chất liệu vải đứng, loại vải nhập khẩu cao cấp từ H&agrave;n Quốc, độ co gi&atilde;n tốt, tạo sự mềm mại khi mặc, Veneto đ&atilde; l&agrave;m h&agrave;i l&ograve;ng ngay cả những người mặc kh&oacute; t&iacute;nh nhất.</span></span><br />\r\n<span style=\"font-family:arial,helvetica,sans-serif; font-size:12px\">&nbsp;</span></p>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; text-align: center;\"><span style=\"color:rgb(0, 0, 0)\"><span style=\"font-size:14px\"><img alt=\"\" src=\"//veneto.vn/images/201610/IMG_0949_compressed_2309083353.jpg\" style=\"border:none; height:467px; max-width:100%; width:700px\" /></span></span></div>\r\n\r\n<p><br />\r\n<span style=\"color:rgb(0, 0, 0); font-family:arial,helvetica,sans-serif; font-size:12px\"><span style=\"font-size:14px\">C&aacute;c t&ocirc;ng m&agrave;u mới đang thịnh h&agrave;nh tr&ecirc;n thế giới như đỏ, t&iacute;m than, xanh đen cũng xuất hiện trong bộ sưu tập lần n&agrave;y của Veneto b&ecirc;n cạnh c&aacute;c mầu cơ bản như trắng, đen, xanh navy. Những ch&uacute; rể th&iacute;ch m&agrave;u sắc mới lạ, bộ sưu tập n&agrave;y sẽ l&agrave; những sự lựa chọn tuyệt vời. C&aacute;c bạn c&oacute; thể lựa chọn những mẫu &aacute;o vest m&agrave;u xanh navy, xanh da trời để diện trong album ảnh cưới. Trong ng&agrave;y cưới, kho&aacute;c l&ecirc;n m&igrave;nh những mẫu vest như t&iacute;m than, xanh đen sẽ gi&uacute;p bạn trở n&ecirc;n thật lịch l&atilde;m s&aacute;nh bước b&ecirc;n c&ocirc; d&acirc;u xinh đẹp của m&igrave;nh.<br />\r\nSang trọng trong thiết kế, lịch l&atilde;m trong phong c&aacute;ch, bộ sưu tập Elegant Suit l&agrave; m&oacute;n qu&agrave; tuyệt vời d&agrave;nh cho c&aacute;c ch&uacute; rể tương lai trong m&ugrave;a cưới 2016 n&agrave;y.<br />\r\n<br />\r\nC&aacute;c sản phẩm trong BST sẽ ch&iacute;nh thức cập bến c&aacute;c showroom của Veneto từ ng&agrave;y 20/9 vừa rồi<br />\r\nH&atilde;y trở th&agrave;nh ch&uacute; rể lịch l&atilde;m, nổi bật v&agrave; sang trọng trong ng&agrave;y trọng đại của ch&iacute;nh bạn c&ugrave;ng Veneto!<br />\r\n<br />\r\n<strong>C&aacute;c bạn c&oacute; thể chi&ecirc;m ngưỡng những mẫu thiết kế trong BST Elegant suit tại đ&acirc;y:</strong></span></span><br />\r\n<br />\r\n<span style=\"font-family:arial,helvetica,sans-serif; font-size:12px\">&nbsp;</span></p>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; text-align: center;\"><img alt=\"\" src=\"//veneto.vn/images/201610/IMGP7792-01_thoi_trang_veneto_2309083739.jpg\" style=\"border:none; height:933px; max-width:100%; width:700px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/IMGP8349-01_thoi_trang_veneto_2309083904.jpg\" style=\"border:none; height:933px; max-width:100%; width:700px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/IMGP8059-01_thoi_trang_veneto_2309083959.jpg\" style=\"border:none; height:933px; max-width:100%; width:700px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/IMGP8241-01_thoi_trang_veneto_2309083951.jpg\" style=\"border:none; height:933px; max-width:100%; width:700px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/IMGP8022-01_thoi_trang_veneto_2309083934.jpg\" style=\"border:none; height:933px; max-width:100%; width:700px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/IMGP7963-01_thoi_trang_veneto_2309083924.jpg\" style=\"border:none; height:933px; max-width:100%; width:700px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/IMGP8296-01_thoi_trang_veneto_2309083911.jpg\" style=\"border:none; height:933px; max-width:100%; width:700px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/IMGP8349-01_thoi_trang_veneto_2309083904.jpg\" style=\"border:none; height:933px; max-width:100%; width:700px\" /></div>\r\n','Tại triển lãm cưới Wedding des Art vừa qua, thương hiệu thời trang nam Veneto đã mang đến Bộ sưu tập Vest cưới 2016 Elegant Suit với phong cách sang trọng, lịch lãm, biến người mặc thành những chú rể thời thượng, nổi bật.','','/201610/','Trở thành chú rể sang trọng, lịch lãm cùng vest cưới Veneto','Trở thành chú rể sang trọng, lịch lãm cùng vest cưới Veneto','vest, veneto, vest cưới, vest thời trang, công sở, thời trang nam','Tại triển lãm cưới Wedding des Art vừa qua, thương hiệu thời trang nam Veneto đã mang đến Bộ sưu tập Vest cưới 2016 Elegant Suit với phong cách sang trọng, lịch lãm, biến người mặc thành những chú rể thời thượng, nổi bật.','Trở thành chú rể sang trọng, lịch lãm cùng vest cưới Veneto',0,0,0,0,1476433147,NULL,'quyettv',NULL,NULL,0,NULL,NULL,NULL,1476433037,1,NULL),(916,179,'Chàng trai mùa đông thanh lịch và tinh tế','','chang-trai-mua-dong-thanh-lich-va-tinh-te-2250-29152-article','','<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; text-align: justify;\"><span style=\"font-size:14px\"><strong>Nếu như thời trang d&agrave;nh cho nữ giới đa dạng với v&aacute;y, &aacute;o, quần&hellip; th&igrave; thời trang d&agrave;nh cho nam giới chỉ quanh quẩn với &aacute;o v&agrave; quần, vest. Tuy nhi&ecirc;n, nếu biết kh&eacute;o l&eacute;o vận dụng, c&aacute;c ch&agrave;ng trai ho&agrave;n to&agrave;n tạo n&ecirc;n được phong c&aacute;ch thời trang ri&ecirc;ng của m&igrave;nh với vẻ ngo&agrave;i mới mẻ, thời thượng.</strong></span><br />\r\n<br />\r\n<span style=\"font-size:14px\"><strong>1. Sắc m&agrave;u trung t&iacute;nh l&ecirc;n ng&ocirc;i</strong></span><br />\r\n<span style=\"font-size:14px\">Với bản chất hướng về chuẩn mực thanh lịch v&agrave; lu&ocirc;n thận trọng với vẻ ngo&agrave;i khi xuất hiện trước mọi người, c&aacute;c ch&agrave;ng trai sẽ cảm thấy thoải m&aacute;i hơn với những bộ c&aacute;nh t&ocirc;ng m&agrave;u trầm trang nh&atilde; như x&aacute;m, n&acirc;u khi cần thay đổi diện mạo thay v&igrave; trung th&agrave;nh với sắc đen truyền thống v&agrave; kinh điển.<br />\r\nThu đ&ocirc;ng 2016 chứng kiến sự l&ecirc;n ng&ocirc;i của những bộ suit hai h&agrave;ng n&uacute;t may bằng chất liệu caro c&oacute; m&agrave;u trung t&iacute;nh như beige, x&aacute;m đậm, x&aacute;m xanh mang lại cho người mặc vẻ trẻ trung v&agrave; chỉn chu v&ocirc; c&ugrave;ng cuốn h&uacute;t.<br />\r\n&nbsp;</span></div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; text-align: center;\"><span style=\"font-size:14px\"><img alt=\"\" src=\"//veneto.vn/images/201610/IMGP80221_thoi_trang_veneto_2309083934.jpg\" style=\"border:none; height:933px; max-width:100%; width:700px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/IMGP80591_thoi_trang_veneto_2309083959.jpg\" style=\"border:none; height:933px; max-width:100%; width:700px\" /><br />\r\n<br />\r\n<img alt=\"\" src=\"//veneto.vn/images/201610/IMGP82411_thoi_trang_veneto_2309083951.jpg\" style=\"border:none; height:933px; max-width:100%; width:700px\" /></span></div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; text-align: center;\">&nbsp;</div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; text-align: justify;\"><span style=\"font-size:14px\">&nbsp;</span><br />\r\n<span style=\"font-size:14px\"><strong>2. Đầu tư cho điểm nhấn đắt gi&aacute;</strong></span><br />\r\n<span style=\"font-size:14px\">Như đ&atilde; n&oacute;i từ đầu, trang phục nam giới kh&ocirc;ng c&oacute; nhiều đất để th&ecirc;m thắt chi tiết rườm r&agrave; cầu kỳ. Nếu kh&ocirc;ng kh&eacute;o l&eacute;o, c&aacute;c ch&agrave;ng sẽ biến m&igrave;nh th&agrave;nh một gi&aacute; treo phụ kiện lủng củng v&agrave; phản cảm. H&atilde;y thận trọng trong việc phối hợp phụ kiện cũng như điểm nhấn đắt gi&aacute; cho bộ trang phục của m&igrave;nh.<br />\r\nVới bộ suit hay &aacute;o kho&aacute;c ngo&agrave;i, đường viền lớp l&oacute;t với m&agrave;u sắc nổi bật nhưng ẩn hiện khi&ecirc;m tốn v&agrave; kh&ocirc;ng lấn &aacute;t tổng thể m&agrave;u b&ecirc;n ngo&agrave;i sẽ gi&uacute;p n&oacute;i hộ chủ nh&acirc;n rất nhiều về gu thẩm mỹ v&agrave; khả năng tiết chế t&agrave;i t&igrave;nh trong c&aacute;ch ăn vận.</span><br />\r\n&nbsp;</div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; text-align: center;\"><img alt=\"\" src=\"//veneto.vn/images/201610/IMGP82961_thoi_trang_veneto_2309083911.jpg\" style=\"border:none; height:933px; max-width:100%; width:700px\" /></div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; text-align: justify;\"><br />\r\n<span style=\"font-size:14px\">Một đ&ocirc;i gi&agrave;y vừa vặn với kiểu d&aacute;ng hay chất liệu ph&aacute; c&aacute;ch sẽ l&agrave; điểm s&aacute;ng ho&agrave;n hảo cho bộ complet đơn giản, đủ khiến người mặc tự tin thu h&uacute;t mọi &aacute;nh nh&igrave;n.<br />\r\nHay mảnh khăn nhỏ nơi t&uacute;i &aacute;o ngực cũng sẽ l&agrave; khoản đầu tư kh&ocirc;n ngoan gi&uacute;p cho bộ c&aacute;nh của bạn trở n&ecirc;n sống động, phong c&aacute;ch m&agrave; vẫn lịch l&atilde;m.<br />\r\n&nbsp;</span></div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; text-align: center;\"><img alt=\"\" src=\"//veneto.vn/images/201610/IMGP7839-01_thoi_trang_veneto_2309083815.jpg\" style=\"border:none; height:933px; max-width:100%; width:700px\" /></div>\r\n\r\n<div style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; text-align: justify;\"><span style=\"font-size:14px\">&nbsp;</span><br />\r\n<span style=\"font-size:14px\"><strong>3. Biến h&oacute;a với &aacute;o len</strong></span><br />\r\n<span style=\"font-size:14px\">&Aacute;o len mỏng mặc ngo&agrave;i để lộ cổ &aacute;o sơ mi c&agrave;i k&iacute;n n&uacute;t, thấp tho&aacute;ng chiếc nơ bướm hay cavat l&agrave; sự thay thế ho&agrave;n to&agrave;n hợp l&yacute; v&agrave; khả thi cho bộ suit c&oacute; phần hơi trịnh trọng v&agrave; nghi&ecirc;m t&uacute;c.&nbsp; Điều cần lưu &yacute; l&agrave; m&agrave;u sắc &aacute;o len cần đồng bộ hoặc kh&ocirc;ng đối nghịch với phụ kiện đi k&egrave;m như gi&agrave;y, tất hay v&iacute; cầm tay nếu c&oacute;.<br />\r\nNgo&agrave;i ra những chiếc cardigan mỏng cũng c&oacute; thể t&aacute;i sử dụng nhưng cần c&agrave;i hết n&uacute;t lại để phần cổ chữ V t&ocirc;n vinh khu&ocirc;n ngực vững ch&atilde;i v&agrave; ngợi khen chiếc &aacute;o sơ mi b&ecirc;n trong một c&aacute;ch tinh tế.</span></div>\r\n','Nếu như thời trang dành cho nữ giới đa dạng với váy, áo, quần… thì thời trang dành cho nam giới chỉ quanh quẩn với áo và quần, vest. Tuy nhiên, nếu biết khéo léo vận dụng, các chàng trai hoàn toàn tạo nên được phong cách thời trang riêng của mình với vẻ ngoài mới mẻ, thời thượng','cover_web_0210215157.jpg','/201610/','Chàng trai mùa đông thanh lịch và tinh tế','Chàng trai mùa đông thanh lịch và tinh tế',' veneto, thời trang veneto, veneto.vn, veston nam đẹp nhất, vest công sở, vest cưới','Nếu như thời trang dành cho nữ giới đa dạng với váy, áo, quần… thì thời trang dành cho nam giới chỉ quanh quẩn với áo và quần, vest. Tuy nhiên, nếu biết khéo léo vận dụng, các chàng trai hoàn toàn tạo nên được phong cách thời trang riêng của mình với vẻ ngoài mới mẻ, thời thượng','Chàng trai mùa đông thanh lịch và tinh tế',0,0,0,0,1476434447,NULL,'quyettv',NULL,NULL,0,NULL,NULL,NULL,1476433506,1,NULL),(917,179,'Siêu mẫu Mạnh Khang đọc tên những ‘luật ngầm’ khi diện suit mà quý ông không nên bỏ qua','','sieu-mau-manh-khang-doc-ten-nhung-‘luat-ngam’-khi-dien-suit-ma-quy-ong-khong-nen-bo-qua-2250-29157-article','','','Suit là trang phục đơn giản nhưng lại cất chứa cả những quy tắc ngầm mà không hẳn anh chàng nào cũng biết. Siêu mẫu Mạnh Khang sẽ giúp bạn giải đáp những thắc mắc đó.','vest_veneto_(2)_compressed_0310091336.jpg','/201610/','Siêu mẫu Mạnh Khang đọc tên những ‘luật ngầm’ khi diện suit mà quý ông không nên bỏ qua','Siêu mẫu Mạnh Khang đọc tên những ‘luật ngầm’ khi diện suit mà quý ông không nên bỏ qua','veneto, thời trang veneto, mạnh khang, áo vest đẹp nhât, áo vest lịch lãm, thời trang công sở','Suit là trang phục đơn giản nhưng lại cất chứa cả những quy tắc ngầm mà không hẳn anh chàng nào cũng biết. Siêu mẫu <NAME> sẽ giúp bạn giải đáp những thắc mắc đó.','<NAME>ẫu <NAME> đọc tên những ‘luật ngầm’ khi diện suit mà quý ông không nên bỏ qua',0,0,0,0,1476803268,1476803535,'quyettv','quyettv',NULL,0,NULL,NULL,NULL,1476803041,1,NULL),(918,181,'Làm thế nào để vừa tiết kiệm tiền mà vẫn có quần áo hàng hiệu để xài?','','lam-the-nao-de-vua-tiet-kiem-tien-ma-van-co-quan-ao-hang-hieu-de-xai-2249-29175-article','','','Các mẫu sản phẩm trong đợt xả kho vẫn đảm bảo các tiêu chí “Sản phẩm cao cấp – Mẫu mã đa dạng – Chất lượng hoàn hảo” của Veneto khi phục vụ khách hàng','sale_70_banner_web_compressed_0610151906.jpg','/201610/','Làm thế nào để vừa tiết kiệm tiền mà vẫn có quần áo hàng hiệu để xài?','Làm thế nào để vừa tiết kiệm tiền mà vẫn có quần áo hàng hiệu để xài?','sale off, xả kho, mùa hè, quần short, áo phông, sơ mi','Các mẫu sản phẩm trong đợt xả kho vẫn đảm bảo các tiêu chí “Sản phẩm cao cấp – Mẫu mã đa dạng – Chất lượng hoàn hảo” của Veneto khi phục vụ khách hàng','Làm thế nào để vừa tiết kiệm tiền mà vẫn có quần áo hàng hiệu để xài?',0,0,0,0,1476804899,NULL,'quyettv',NULL,NULL,0,NULL,NULL,NULL,1476804030,1,NULL),(919,183,'SUIT THỜI TRANG THU VỚI VENETO','','suits-thoi-trang-thu-voi-veneto-2250-28251-article','{\"1476805805\":\"suit-thoi-trang-thu-voi-veneto\"}','','Ra đời từ năm 2006, Veneto được biết đến là một trong những hãng thời trang nam bán hàng online trực tuyến đầu tiên ở Hà Nội. Phong cách mà chúng tôi hướng tới là phong cách lịch lãm, sang trọng nhưng không kém phần trẻ trung dành cho các quý ông thời thượng. Năm 2012 là mốc đánh dấu quan trọng của chúng tôi khi cho ra mắt cửa hàng đại diện đầu tiên tại Hà Nội. Cũng từ đó Veneto ngày càng lớn mạnh. Được sự yêu mến và tin dùng của quý khách hàng, trong năm 2013 Veneto đã phát triển thêm hệ thống cửa hàng củ','tin_1208182015_1006234406.png','/201610/','SUIT THỜI TRANG THU VỚI VENETO','SUIT THỜI TRANG THU VỚI VENETO','SUIT THỜI TRANG THU VỚI VENETO','Ra đời từ năm 2006, Veneto được biết đến là một trong những hãng thời trang nam bán hàng online trực tuyến đầu tiên ở Hà Nội. Phong cách mà chúng tôi hướng tới là phong cách lịch lãm, sang trọng nhưng không kém phần trẻ trung dành cho các quý ông thời thượng. Năm 2012 là mốc đánh dấu quan trọng của chúng tôi khi cho ra mắt cửa hàng đại diện đầu tiên tại Hà Nội. Cũng từ đó Veneto ngày càng lớn mạnh. Được sự yêu mến và tin dùng của quý khách hàng, trong năm 2013 Veneto đã phát triển thêm hệ thống cửa hàng củ','SUIT THỜI TRANG THU VỚI VENETO',0,0,0,0,1476805293,1476805805,'quyettv','quyettv',NULL,0,NULL,NULL,NULL,1476804951,1,NULL),(920,183,'CÁCH CHỌN SƠ MI NAM CHUẨN NHẤT','','cach-chon-so-mi-nam-chuan-nhat-2250-28252-article','','','Áo sơ mi nam là items quá quen thuộc trong tủ đồ của các bạn trai. Đặc trưng phổ biến cũng như thích hợp với mọi hoàn cảnh khiến sơ mi nam là món đồ khiến chúng ta nghĩ đến đầu tiên khi có ý định đi mua sắm. Tuy nhiên, việc chọn sơ mi nam đúng chuẩn, phù hợp cho bản thân cũng không phải là một việc đơn giản nhất là đối với các bạn nam chúng ta khá là xoàng trong việc mua sắm.','Veneto_ao_vest_94_0410094651_1006234801.jpg','/201610/','CÁCH CHỌN SƠ MI NAM CHUẨN NHẤT','CÁCH CHỌN SƠ MI NAM CHUẨN NHẤT','Cách chọn áo sơ mi nam chuẩn nhấ','Áo sơ mi nam là items quá quen thuộc trong tủ đồ của các bạn trai. Đặc trưng phổ biến cũng như thích hợp với mọi hoàn cảnh khiến sơ mi nam là món đồ khiến chúng ta nghĩ đến đầu tiên khi có ý định đi mua sắm. Tuy nhiên, việc chọn sơ mi nam đúng chuẩn, phù hợp cho bản thân cũng không phải là một việc đơn giản nhất là đối với các bạn nam chúng ta khá là xoàng trong việc mua sắm.','CÁCH CHỌN SƠ MI NAM CHUẨN NHẤT',0,0,0,0,1476805542,NULL,'quyettv',NULL,NULL,0,NULL,NULL,NULL,1476805413,1,NULL),(921,183,'VENETO GỢI Ý CÁCH CHỌN VEST TUYỆT ĐẸP CHO CÁC CHÀNG TRAI','','veneto-goi-y-cach-chon-vest-tuyet-dep-cho-cac-chang-trai-2250-28253-article','{\"1476805777\":\"veneto-goi-y-cach-chon-vest-tuyet-dep-cho-cac-chang-trai\"}','','Với đội ngũ thợ may lâu năm kinh nghiệm kết hợp cùng với phong cách thiết kế hiện đại, trịnh trọng, Veneto cung cấp rất nhiều sản phẩm vest với kiểu dáng, mẫu mã đa dạng. Veneto đáp ứng tốt những nhu cầu thẩm mỹ và xu hướng thời trang của các quý khách hàng.','IMG_2235_1610133448_1006235059.jpg','/201610/','VENETO GỢI Ý CÁCH CHỌN VEST TUYỆT ĐẸP CHO CÁC CHÀNG TRAI','VENETO GỢI Ý CÁCH CHỌN VEST TUYỆT ĐẸP CHO CÁC CHÀNG TRAI','vest cưới, vest nam, vest thời trang, veneto, hướng dẫn, lựa chọn','Với đội ngũ thợ may lâu năm kinh nghiệm kết hợp cùng với phong cách thiết kế hiện đại, trịnh trọng, Veneto cung cấp rất nhiều sản phẩm vest với kiểu dáng, mẫu mã đa dạng. Veneto đáp ứng tốt những nhu cầu thẩm mỹ và xu hướng thời trang của các quý khách hàng.','<NAME> CÁCH CHỌN VEST TUYỆT ĐẸP CHO CÁC CHÀNG TRAI',0,0,0,0,1476805755,1476805777,'quyettv','quyettv',NULL,0,NULL,NULL,NULL,1476805565,1,NULL),(922,183,'BÍ QUYẾT CHỌN VEST CƯỚI CHO NAM GIỚI','','bi-quyet-chon-vest-cuoi-cho-nam-gioi-2250-28254-article','','','Hãy cùng Veneto khám phá những bí quyết dưới đây để có thể giúp bạn chọn được một bộ vest phù hợp nhất trong ngày trọng đại của đời mình...','11243804_1048087395215854_1578243602313023990_n_2110135921_1006235310.jpg','/201610/','BÍ QUYẾT CHỌN VEST CƯỚI CHO NAM GIỚI','BÍ QUYẾT CHỌN VEST CƯỚI CHO NAM GIỚI','vest cưới, vest thời trang, Veneto, thời trang nam, lễ cưới','Hãy cùng Veneto khám phá những bí quyết dưới đây để có thể giúp bạn chọn được một bộ vest phù hợp nhất trong ngày trọng đại của đời mình...','BÍ QUYẾT CHỌN VEST CƯỚI CHO NAM GIỚI',0,0,0,0,1476806253,NULL,'quyettv',NULL,NULL,0,NULL,NULL,NULL,1476805908,1,NULL),(923,183,'QUY TẮC BẢO QUẢN ĐỒ VEST','','quy-tac-bao-quan-do-vest-2250-28255-article','','','Chiếc áo vest giúp cho các quý ông thêm phần tự tin trong giao tiếp cũng như tạo dựng hình ảnh lịch lãm, phong thái chuyên nghiệp trong các sự kiện quan trọng như: các buổi tiệc xã giao; gặp đối tác; kí kết hợp đồng; đi dự tiệc cưới','baoquan_vest6_2710114028_1006235558.jpg','/201610/','QUY TẮC BẢO QUẢN ĐỒ VEST','QUY TẮC BẢO QUẢN ĐỒ VEST','bảo quản, vest cưới, vest thời trang, Veneto, suit','Chiếc áo vest giúp cho các quý ông thêm phần tự tin trong giao tiếp cũng như tạo dựng hình ảnh lịch lãm, phong thái chuyên nghiệp trong các sự kiện quan trọng như: các buổi tiệc xã giao; gặp đối tác; kí kết hợp đồng; đi dự tiệc cưới','QUY TẮC BẢO QUẢN ĐỒ VEST',0,0,0,0,1476806401,1476806414,'quyettv','quyettv',NULL,0,NULL,NULL,NULL,1476806263,1,NULL),(924,179,'SIÊU MẪU HOÀNG GIA ANH VŨ MẶC ĐẸP VỚI BST MỚI NHẤT CỦA VENETO','','sieu-mau-hoang-gia-anh-vu-mac-dep-voi-bst-moi-nhat-cua-veneto','','','Cùng xem “hot boy 6 múi” Hoàng Gia Anh Vũ thay đổi phong cách thời trang của mình ra sao với items: măng tô, áo khoác, áo da,... trong bộ sưu tập mới nhất của Veneto...','batch-Hoang-Gia-Anh-Vu-1439140145_660x0_0801120952.jpg','/201610/','SIÊU MẪU HOÀNG GIA ANH VŨ MẶC ĐẸP VỚI BST MỚI NHẤT CỦA VENETO','SIÊU MẪU HOÀNG GIA ANH VŨ MẶC ĐẸP VỚI BST MỚI NHẤT CỦA VENETO',' Veneto, Hoàng Gia Anh Vũ, siêu mẫu, 2016, bộ sưu tập','Cùng xem “hot boy 6 múi” Hoàng Gia Anh Vũ thay đổi phong cách thời trang của mình ra sao với items: măng tô, áo khoác, áo da,... trong bộ sưu tập mới nhất của Veneto...','SIÊU MẪU HOÀNG GIA ANH VŨ MẶC ĐẸP VỚI BST MỚI NHẤT CỦA VENETO',0,0,0,0,1476806487,NULL,'quyettv',NULL,NULL,0,NULL,NULL,NULL,1476806417,1,NULL),(925,179,'CÙNG VENETO MẶC ĐẸP ĐÓN TẾT','','cung-veneto-mac-dep-don-tet-2250-28257-article','','','Veneto trân trọng gửi tới các quý khách hàng một bộ sưu tập mới; với sản phẩm chủ đạo là những chiếc áo polo với nhiều màu sắc, được thiết kế bằng chất liệu cao cấp và thoáng mát.','12931007_549937318542356_7489180640398402079_n_0404202513.jpg','/201610/','CÙNG VENETO MẶC ĐẸP ĐÓN TẾT','CÙNG VENETO MẶC ĐẸP ĐÓN TẾT',' thời trang Veneto, mặc đẹp, Tết 2016, thời trang nam','Veneto trân trọng gửi tới các quý khách hàng một bộ sưu tập mới; với sản phẩm chủ đạo là những chiếc áo polo với nhiều màu sắc, được thiết kế bằng chất liệu cao cấp và thoáng mát.','CÙ<NAME> MẶC ĐẸP ĐÓN TẾT',0,0,0,0,1476807732,NULL,'quyettv',NULL,NULL,0,NULL,NULL,NULL,1476807615,1,NULL),(926,179,'<NAME>: MẶC ÁO POLO SAO CHO ĐẸP','','veneto-mach-ban-mac-ao-polo-sao-cho-dep-2250-28259-article','','','Rất nhiều quý ông xem chiếc áo thun polo là người bạn thân vì đặc tính đầy biến hóa và dễ phối đồ. Với áo thun polo, bạn có thể \"biến hóa\" với nhiều phong cách khác nhau, từ công sở, tiệc tùng cho đến những buổi dã ngoại.','12931007_549937318542356_7489180640398402079_n_0404202513-2.jpg','/201610/','<NAME>: MẶC ÁO POLO SAO CHO ĐẸP','<NAME>: MẶC ÁO POLO SAO CHO ĐẸP','áo thun polo, thời trang nam, thời trang Veneto, khởi đầu cho sự thành công, thời trang nam công sở, áo thun đẹp 2016','Rất nhiều quý ông xem chiếc áo thun polo là người bạn thân vì đặc tính đầy biến hóa và dễ phối đồ. Với áo thun polo, bạn có thể \"biến hóa\" với nhiều phong cách khác nhau, từ công sở, tiệc tùng cho đến những buổi dã ngoại.','<NAME>: MẶC ÁO POLO SAO CHO ĐẸP',0,0,0,0,1476807857,NULL,'quyettv',NULL,NULL,0,NULL,NULL,NULL,1476807754,1,NULL),(927,179,'ÁO POLO – TRANG PHỤC NAM GIỚI NÀO CŨNG NÊN ĐẦU TƯ','','ao-polo-–-trang-phuc-nam-gioi-nao-cung-nen-dau-tu-2250-28260-article','','',' Những người đàn ông hiện đại sẽ luôn hiểu rõ đặc tính hữu dụng và khả năng thẩm mỹ của item này mang lại để lựa chọn một chiếc áo thun....','','/201610/','ÁO POLO – TRANG PHỤC NAM GIỚI NÀO CŨNG NÊN ĐẦU TƯ','ÁO POLO – TRANG PHỤC NAM GIỚI NÀO CŨNG NÊN ĐẦU TƯ','áo phông, áo polo Veneto, thời trang hè, thời trang nam, công sở',' Những người đàn ông hiện đại sẽ luôn hiểu rõ đặc tính hữu dụng và khả năng thẩm mỹ của item này mang lại để lựa chọn một chiếc áo thun....','ÁO POLO – TRANG PHỤC NAM GIỚI NÀO CŨNG NÊN ĐẦU TƯ',0,0,0,0,1476808207,NULL,'quyettv',NULL,NULL,0,NULL,NULL,NULL,1476807883,1,NULL),(928,179,'HỌC BÍ QUYẾT DIỆN VEST CỰC CHUẨN VỚI DIỄN VIÊN TRẺ PHẠM ANH TUẤN','','hoc-bi-quyet-dien-vest-cuc-chuan-voi-dien-vien-tre-pham-anh-tuan-2250-28261-article','','','Để tìm hiểu rõ hơn về phong cách thời trang của Phạm Anh Tuấn, hãy cùng xem qua một số shoot hình thời trang của chàng diễn viên trẻ này.','Untitled-1_1804124805.jpg','/201610/','HỌC BÍ QUYẾT DIỆN VEST CỰC CHUẨN VỚI DIỄN VIÊN TRẺ PHẠM ANH TUẤN','HỌC BÍ QUYẾT DIỆN VEST CỰC CHUẨN VỚI DIỄN VIÊN TRẺ PHẠM ANH TUẤN','diễn viên <NAME>, điện ảnh, thời trang, trái tim có nắng, diễn viên','Để tìm hiểu rõ hơn về phong cách thời trang của Phạm Anh Tuấn, hãy cùng xem qua một số shoot hình thời trang của chàng diễn viên trẻ này.','HỌC BÍ QUYẾT DIỆN VEST CỰC CHUẨN VỚI DIỄN VIÊN TRẺ PHẠM ANH TUẤN',0,0,0,0,1476808406,1476808491,'quyettv','quyettv',NULL,0,NULL,NULL,NULL,1476808226,1,NULL),(929,179,'ÁO THUN POLO – TẠI SAO KHÔNG?','','ao-thun-polo-–-tai-sao-khong-2250-28262-article','','','Không chỉ những bộ cánh đứng đắn, những chiếc áo vest dự tiệc tùng mới làm tôn lên dáng vẻ lịch lãm, phong độ của anh em. Những chiếc áo phông polo nếu biết cách phố hợp với quần và phụ kiện đi kèm c','_MI81761_0505094136.jpg','/201610/','ÁO THUN POLO – TẠI SAO KHÔNG?','ÁO THUN POLO – TẠI SAO KHÔNG?','Thời trang Veneto, áo phông polo, mùa hè, mặc đẹp, nam giới','Không chỉ những bộ cánh đứng đắn, những chiếc áo vest dự tiệc tùng mới làm tôn lên dáng vẻ lịch lãm, phong độ của anh em. Những chiếc áo phông polo nếu biết cách phố hợp với quần và phụ kiện đi kèm c','ÁO THUN POLO – TẠI SAO KHÔNG?',0,0,0,0,1476808651,NULL,'quyettv',NULL,NULL,0,NULL,NULL,NULL,1476808494,1,NULL),(930,179,'VENETO CHIA SẺ BÍ QUYẾT: DIỆN SHORT CHO THẬT CHUẨN','','veneto-chia-se-bi-quyet-dien-vest-cho-that-chuan-2250-28263-article','{\"1476808792\":\"veneto-chia-se-bi-quyet-dien-short-cho-that-chuan\"}','','Để mỗi chàng trai đều các chàng trai đều tự tin, không phải bận tâm bất cứ điều gì mỗi khi diện quần short. Hôm nay với những câu hỏi ngắn - đáp nhanh dưới đây, Veneto sẽ mách nhỏ anh em một số bí quyết dễ nhớ - dễ áp dụng để diện short - trang phục nổi bật trong những ngày hè cho thật phù hợp','Short_3_1005151900.jpg','/201610/','VENETO CHIA SẺ BÍ QUYẾT: DIỆN SHORT CHO THẬT CHUẨN','VENETO CHIA SẺ BÍ QUYẾT: DIỆN SHORT CHO THẬT CHUẨN','quần short nam, mua hè, diện short, tự tin, thời trang Veneto','Để mỗi chàng trai đều các chàng trai đều tự tin, không phải bận tâm bất cứ điều gì mỗi khi diện quần short. Hôm nay với những câu hỏi ngắn - đáp nhanh dưới đây, Veneto sẽ mách nhỏ anh em một số bí quyết dễ nhớ - dễ áp dụng để diện short - trang phục nổi bật trong những ngày hè cho thật phù hợp','<NAME> BÍ QUYẾT: DIỆN SHORT CHO THẬT CHUẨN',0,0,0,0,1476808775,1476808792,'quyettv','quyettv',NULL,0,NULL,NULL,NULL,1476808662,1,NULL),(931,179,'ÁO THUN VÀ QUẦN SHORT: CẶP ĐÔI HOÀN HẢO CHO NGÀY HÈ','','ao-thun-va-quan-short-cap-doi-hoan-hao-cho-ngay-he-2250-28264-article','','','Đối với phái mạnh, những người ưa thích và trung thành với những trang phục đem lại thoải mái, năng động; chỉ với một chiếc áo thun và chiếc quần short - nhìn các chàng đã cực kỳ lôi cuốn và lịch lãm. ','K_N_3196_1205160300.jpg','/201610/','ÁO THUN VÀ QUẦN SHORT: CẶP ĐÔI HOÀN HẢO CHO NGÀY HÈ','ÁO THUN VÀ QUẦN SHORT: CẶP ĐÔI HOÀN HẢO CHO NGÀY HÈ','mùa hè, quần short, áp phông, áo thun, thời trang veneto, khởi đầu của sự thành công','Đối với phái mạnh, những người ưa thích và trung thành với những trang phục đem lại thoải mái, năng động; chỉ với một chiếc áo thun và chiếc quần short - nhìn các chàng đã cực kỳ lôi cuốn và lịch lãm. ','ÁO THUN VÀ QUẦN SHORT: CẶP ĐÔI HOÀN HẢO CHO NGÀY HÈ',0,0,0,0,1476808898,NULL,'quyettv',NULL,NULL,0,NULL,NULL,NULL,1476808795,1,NULL),(932,179,'SƠMI PHONG CÁCH CASUAL – XU HƯỚNG MỚI CỦA HÈ 2016','','somi-phong-cach-casual-–-xu-huong-moi-cua-he-2250-28265-article','','','Áo sơmi luôn là chủ đề được các đấng mày râu - đây là trang phục đẹp nhất, tôn lên dáng vẻ phong trần, nam tính của phái mạnh...','tuxmain3_1405130314.jpg','/201610/','SƠMI PHONG CÁCH CASUAL – XU HƯỚNG MỚI CỦA HÈ 2016','SƠMI PHONG CÁCH CASUAL – XU HƯỚNG MỚI CỦA HÈ 2016','sơmi, casual, phong cách, mùa hè, thời trang Veneto, 2016','Áo sơmi luôn là chủ đề được các đấng mày râu - đây là trang phục đẹp nhất, tôn lên dáng vẻ phong trần, nam tính của phái mạnh...','SƠMI PHONG CÁCH CASUAL – XU HƯỚNG MỚI CỦA HÈ 2016',0,0,0,0,1476808990,NULL,'quyettv',NULL,NULL,0,NULL,NULL,NULL,1476808909,1,NULL),(933,179,'NHỮNG GAM MÀU QUẦN ÁO LÀM DỊU CÁI NÓNG MÙA HÈ','','nhung-gam-mau-quan-ao-lam-diu-cai-nong-mua-he-2250-28267-article','{\"1476809122\":\"nhung-gam-mau-quan-ao-lam-diu-cai-nong-mua-he\"}','','Với những gam màu dịu mát của trang phục sẽ khiến mùa hè của bạn được giảm nhiệt và không còn nóng nực nữa.','crush-francisco-lachowski-handsome-model-Favim.com-3636315_1605152608.jpg','/201610/','NHỮNG GAM MÀU QUẦN ÁO LÀM DỊU CÁI NÓNG MÙA HÈ','NHỮNG GAM MÀU QUẦN ÁO LÀM DỊU CÁI NÓNG MÙA HÈ','màu sắc, trang phục, mùa hè, thời trang nam, menswear, thời trang veneto','Với những gam màu dịu mát của trang phục sẽ khiến mùa hè của bạn được giảm nhiệt và không còn nóng nực nữa.','NHỮNG GAM MÀU QUẦN ÁO LÀM DỊU CÁI NÓNG MÙA HÈ',0,0,0,0,1476809081,1476809122,'quyettv','quyettv',NULL,0,NULL,NULL,NULL,1476808992,1,NULL),(934,179,'DIỆN QUẦN SHORT - NHỮNG ĐỀU NÊN & KHÔNG NÊN','','xu-huong-thoi-trang/dien-quan-short-nhung-dieu-nen-va-khong-nen-2250-28268-article','','','Chọn quần short như thế nào là hợp lý không phải ai cũng biết cách. Dưới đây là những cách đơn giản giúp cho các chàng dễ dàng hơn khi lựa chọn chiếc quần cho chuyến dạo chơi mùa hè của mình.','publish-summer-2015-open-mind-lookbook-01_1905153453.jpg','/201610/','DIỆN QUẦN SHORT - NHỮNG ĐỀU NÊN & KHÔNG NÊN','DIỆN QUẦN SHORT - NHỮNG ĐỀU NÊN & KHÔNG NÊN','Quần short, mùa hè, tự tin, thời trang Veneto','Chọn quần short như thế nào là hợp lý không phải ai cũng biết cách. Dưới đây là những cách đơn giản giúp cho các chàng dễ dàng hơn khi lựa chọn chiếc quần cho chuyến dạo chơi mùa hè của mình.','DIỆN QUẦN SHORT - NHỮNG ĐỀU NÊN & KHÔNG NÊN',0,0,0,0,1476809203,NULL,'quyettv',NULL,NULL,0,NULL,NULL,NULL,1476809133,1,NULL),(935,179,'THẮT CÀ VẠT SAO CHO ĐẸP?','','that-ca-vat-the-nao-cho-dep-2250-28269-article','{\"1476809858\":\"that-ca-vat-sao-cho-dep\"}','','Hôm nay Veneto sẽ hướng dẫn các bạn cách thắt cà vạt đẹp nhất đối với cà vạt thường và cà vạt nơ. Ngoài ra, bạn cũng nên biết những lưu ý về cách bảo quản chiếc cà vạt của mình.','nut-that-ca-vat-four-in-hand_2705152846.jpg','/201610/','THẮT CÀ VẠT SAO CHO ĐẸP?','THẮT CÀ VẠT SAO CHO ĐẸP?','cà vạt, caravat đẹp, phụ kiện, thời trang nam, vest cưới, thời trang Veneto','Hôm nay Veneto sẽ hướng dẫn các bạn cách thắt cà vạt đẹp nhất đối với cà vạt thường và cà vạt nơ. Ngoài ra, bạn cũng nên biết những lưu ý về cách bảo quản chiếc cà vạt của mình.','THẮT CÀ VẠT SAO CHO ĐẸP?',0,0,0,0,1476809306,1476809858,'quyettv','quyettv',NULL,0,NULL,NULL,NULL,1476809207,1,NULL),(936,179,'5 LỖI THỜI TRANG CÁNH MÀY RÂU THƯỜNG XUYÊN MẮC PHẢI','','-loi-thoi-trang-canh-may-rau-thuong-xuyen-mac-phai-2250-28270-article','','','Thời trang nam thường không phức tạp như của phụ nữ và rất dễ phối đồ, nhưng nhiều người vẫn mắc lỗi cơ bản. Hãy xem 5 lỗi thời trang cánh mày râu thường xuyên mắc phải để kịp rút kinh nghiệm nhé.','5_loi_thoi_trang_canh_may_rau_thuong_xuyen_mac_phai7_2705154753.jpg','/201610/','5 LỖI THỜI TRANG CÁNH MÀY RÂU THƯỜNG XUYÊN MẮC PHẢI','5 LỖI THỜI TRANG CÁNH MÀY RÂU THƯỜNG XUYÊN MẮC PHẢI',' lỗi, thời trang, bí quyết, mặc đẹp, nam giới, thời trang Veneto','Thời trang nam thường không phức tạp như của phụ nữ và rất dễ phối đồ, nhưng nhiều người vẫn mắc lỗi cơ bản. Hãy xem 5 lỗi thời trang cánh mày râu thường xuyên mắc phải để kịp rút kinh nghiệm nhé.','5 LỖI THỜI TRANG CÁNH MÀY RÂU THƯỜNG XUYÊN MẮC PHẢI',0,0,0,0,1476809439,NULL,'quyettv',NULL,NULL,0,NULL,NULL,NULL,1476809311,1,NULL),(937,179,'BÍ QUYẾT LỊCH LÃM CHO NAM GIỚI TRONG MÙA HÈ NÓNG NỰC','','bi-quyet-lich-lam-cho-nam-gioi-trong-mua-he-nong-nuc-2250-28271-article','','','Trang phục nam giới không những phải bắt mắt và lịch lãm, mà còn cần phù hợp với mùa và khí hậu tại thời điểm sử dụng.','bi-quyet-lich-lam-cho-nam-gioi-trong-mua-he-nong-nuc_0306141432.png','/201610/','BÍ QUYẾT LỊCH LÃM CHO NAM GIỚI TRONG MÙA HÈ NÓNG NỰC','BÍ QUYẾT LỊCH LÃM CHO NAM GIỚI TRONG MÙA HÈ NÓNG NỰC','nam giới, công sở, thời trang veneto, mặc đẹp, mùa hè, lịch lãm, phong cách','Trang phục nam giới không những phải bắt mắt và lịch lãm, mà còn cần phù hợp với mùa và khí hậu tại thời điểm sử dụng.','<NAME>T LỊCH LÃM CHO NAM GIỚI TRONG MÙA HÈ NÓNG NỰC',0,0,0,0,1476809577,NULL,'quyettv',NULL,NULL,0,NULL,NULL,NULL,1476809442,1,NULL),(938,179,'ĐỂ CÁC CHÀNG LUÔN CUỐN HÚT VỚI QUẦN ÂU','','de-cac-chang-luon-cuon-hut-voi-quan-au-2250-28272-article','','',' Bộ trang phục công sở kết hợp giữa chiếc quần âu và áo sơ mi khoác ngoài chiếc áo vest chắc hẳn sẽ khiến cho các cô nàng phải đổ gục trước bạn bởi vẻ nam tính, mạnh mẽ và cuốn hút kỳ lạ. Sơ mi và quần âu là trang phục gắn liền với phái mạnh từ xưa và luôn làm cho người ta cảm giác cứng nhắc khi diện những bộ trang phục này.','Massimo-Dutti-May-Mens-Lookbook-08_0906150006.jpg','/201610/','ĐỂ CÁC CHÀNG LUÔN CUỐN HÚT VỚI QUẦN ÂU','ĐỂ CÁC CHÀNG LUÔN CUỐN HÚT VỚI QUẦN ÂU','ĐỂ CÁC CHÀNG LUÔN CUỐN HÚT VỚI QUẦN ÂU',' Bộ trang phục công sở kết hợp giữa chiếc quần âu và áo sơ mi khoác ngoài chiếc áo vest chắc hẳn sẽ khiến cho các cô nàng phải đổ gục trước bạn bởi vẻ nam tính, mạnh mẽ và cuốn hút kỳ lạ. Sơ mi và quần âu là trang phục gắn liền với phái mạnh từ xưa và luôn làm cho người ta cảm giác cứng nhắc khi diện những bộ trang phục này.','ĐỂ CÁC CHÀNG LUÔN CUỐN HÚT VỚI QUẦN ÂU',0,0,0,0,1476809667,NULL,'quyettv',NULL,NULL,0,NULL,NULL,NULL,1476809581,1,NULL),(939,179,'SAO KHÔNG THỬ DIỆN SHORT THANH LỊCH VỚI SƠMI','','sao-khong-thu-dien-short-thanh-lich-voi-somi-2250-28273-article','{\"1476809827\":\"sao-khong-thu-dien-short-thanh-lich-voi-somi\"}','','Những chiếc quần ngắn là trang phục không thể thiếu của các chàng trai trong những kỳ nghỉ ngày hè.','summer-essentials-for-every-guy-who-wants-to-look-stylish-652x400-1-1464260529_1006165727.jpg','/201610/','SAO KHÔNG THỬ DIỆN SHORT THANH LỊCH VỚI SƠMI','SAO KHÔNG THỬ DIỆN SHORT THANH LỊCH VỚI SƠMI',' quần short, thời trang nam, lịch lãm, thời trang veneto, nam giới','Những chiếc quần ngắn là trang phục không thể thiếu của các chàng trai trong những kỳ nghỉ ngày hè.','SAO KHÔNG THỬ DIỆN SHORT THANH LỊCH VỚI SƠMI',0,0,0,0,1476809765,1476809827,'quyettv','quyettv',NULL,0,NULL,NULL,NULL,1476809671,1,NULL),(940,179,'CÁCH CHỌN SƠ MI NGẮN TAY ĐỂ CHÀNG THÊM CUỐN HÚT','','cach-chon-so-mi-ngan-tay-de-chang-them-cuon-hut-2250-28524-article','','','Khi những chiếc áo sơ mi nam tay dài đã khiến bạn trở nên nhàm chán, đôi khi thật nóng nực và bạn cần một sự thay đổi để có thể làm mới mình hơn. Nếu như vậy còn lựa chọn nào tốt hơn áo sơ mi nam tay ngắn, một chiếc áo vừa mang lại cho bạn tự tươi trẻ, năng động và cá tính mặc khác vẫn rất thanh lịch để bạn diện trong những dịp quan trọng.','somi_veneto_thoi_trang_0707110141.jpg','/201610/','CÁCH CHỌN SƠ MI NGẮN TAY ĐỂ CHÀNG THÊM CUỐN HÚT','CÁCH CHỌN SƠ MI NGẮN TAY ĐỂ CHÀNG THÊM CUỐN HÚT','veneto, thời trang nam veneto, sơ mi nam, so mi nam, sơ mi nam ngắn tay, nam giới','Khi những chiếc áo sơ mi nam tay dài đã khiến bạn trở nên nhàm chán, đôi khi thật nóng nực và bạn cần một sự thay đổi để có thể làm mới mình hơn. Nếu như vậy còn lựa chọn nào tốt hơn áo sơ mi nam tay ngắn, một chiếc áo vừa mang lại cho bạn tự tươi trẻ, năng động và cá tính mặc khác vẫn rất thanh lịch để bạn diện trong những dịp quan trọng.','CÁCH CHỌN SƠ MI NGẮN TAY ĐỂ CHÀNG THÊM CUỐN HÚT',3,0,0,0,1476809977,NULL,'quyettv',NULL,NULL,0,NULL,NULL,NULL,1476809861,1,NULL),(941,179,'BÍ QUYẾT ĐỂ ÁO SƠ MI NAM LUÔN NHƯ MỚI','','bi-quyet-de-ao-so-mi-nam-luon-nhu-moi-2250-28563-article','','','Áo sơ mi là loại áo không thể thiếu trong tủ đồ của phái nam. Chiếc áo của bạn qua vài lần sử dụng nhưng bạn không biết cách bảo quản khiến nó trở nên cũ màu. Bạn đừng quá lo lắng Veneto sẽ giúp bạn một số mẹo nhỏ để biến chiếc áo đó trở lại như mới.','bao_quan_ao_so_mi_1807143604.jpg','/201610/','BÍ QUYẾT ĐỂ ÁO SƠ MI NAM LUÔN NHƯ MỚI','BÍ QUYẾT ĐỂ ÁO SƠ MI NAM LUÔN NHƯ MỚI','BÍ QUYẾT ĐỂ ÁO SƠ MI NAM LUÔN NHƯ MỚI','Áo sơ mi là loại áo không thể thiếu trong tủ đồ của phái nam. Chiếc áo của bạn qua vài lần sử dụng nhưng bạn không biết cách bảo quản khiến nó trở nên cũ màu. Bạn đừng quá lo lắng Veneto sẽ giúp bạn một số mẹo nhỏ để biến chiếc áo đó trở lại như mới.','BÍ QUYẾT ĐỂ ÁO SƠ MI NAM LUÔN NHƯ MỚI',2,0,0,0,1476810094,1477390182,'quyettv','quyettv',NULL,0,NULL,NULL,NULL,1476809981,1,NULL); /*Table structure for table `article_category` */ DROP TABLE IF EXISTS `article_category`; CREATE TABLE `article_category` ( `id` int(11) NOT NULL AUTO_INCREMENT, `name` varchar(255) COLLATE utf8_unicode_ci NOT NULL DEFAULT '', `label` varchar(255) COLLATE utf8_unicode_ci DEFAULT '', `slug` varchar(255) COLLATE utf8_unicode_ci NOT NULL DEFAULT '', `old_slugs` varchar(2000) COLLATE utf8_unicode_ci DEFAULT '', `parent_id` int(11) DEFAULT NULL, `description` varchar(511) COLLATE utf8_unicode_ci DEFAULT '', `long_description` text COLLATE utf8_unicode_ci, `meta_title` varchar(511) COLLATE utf8_unicode_ci DEFAULT '', `meta_description` varchar(511) COLLATE utf8_unicode_ci DEFAULT '', `meta_keywords` varchar(511) COLLATE utf8_unicode_ci DEFAULT '', `h1` varchar(511) COLLATE utf8_unicode_ci DEFAULT '', `page_title` varchar(511) COLLATE utf8_unicode_ci DEFAULT '', `image` varchar(511) COLLATE utf8_unicode_ci DEFAULT '', `banner` varchar(511) COLLATE utf8_unicode_ci DEFAULT '', `image_path` varchar(511) COLLATE utf8_unicode_ci DEFAULT '', `status` tinyint(2) DEFAULT NULL, `is_hot` tinyint(1) DEFAULT NULL, `sort_order` int(11) DEFAULT NULL, `created_at` int(11) NOT NULL, `updated_at` int(11) DEFAULT NULL, `created_by` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `updated_by` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `is_active` tinyint(1) DEFAULT NULL, `type` tinyint(2) DEFAULT NULL, PRIMARY KEY (`id`), UNIQUE KEY `slug` (`slug`), KEY `fk_parent_idx` (`parent_id`), CONSTRAINT `fk_parent` FOREIGN KEY (`parent_id`) REFERENCES `article_category` (`id`) ON DELETE SET NULL ON UPDATE CASCADE ) ENGINE=InnoDB AUTO_INCREMENT=184 DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; /*Data for the table `article_category` */ insert into `article_category`(`id`,`name`,`label`,`slug`,`old_slugs`,`parent_id`,`description`,`long_description`,`meta_title`,`meta_description`,`meta_keywords`,`h1`,`page_title`,`image`,`banner`,`image_path`,`status`,`is_hot`,`sort_order`,`created_at`,`updated_at`,`created_by`,`updated_by`,`is_active`,`type`) values (178,'Tin tức Veneto','','tin-tuc-veneto','{\"1476431327\":\"tin-tuc\"}',NULL,'','','Tin tức Veneto','','','Tin tức Veneto','Tin tức Veneto','','','/201610/',NULL,0,NULL,1475772976,1476431327,'quyettv','quyettv',1,1),(179,'Xu hướng thời trang','','xu-huong-thoi-trang','',NULL,'','','Xu hướng thời trang','','','Xu hướng thời trang','Xu hướng thời trang','','','/201610/',NULL,0,NULL,1476428973,NULL,'quyettv',NULL,1,2),(180,'Sự kiện','','su-kien','',NULL,'','','Sự kiện','','','Sự kiện','Sự kiện','','','/201610/',NULL,0,NULL,1476430740,1476432080,'quyettv','quyettv',1,1),(181,'Tin khuyến mãi','','tin-khuyen-mai','',NULL,'','','Tin khuyến mãi','','','Tin khuyến mãi','Tin khuyến mãi','','','/201610/',NULL,0,NULL,1476431626,1476432088,'quyettv','quyettv',1,1),(182,'Tin tiêu điểm','','tin-tieu-diem','',NULL,'','','Tin tiêu điểm','','','Tin tiêu điểm','Tin tiêu điểm','','','/201610/',NULL,0,NULL,1476432056,1476432061,'quyettv','quyettv',1,1),(183,'Xu hướng','','xu-huong','',NULL,'','','Xu hướng','','','Xu hướng','Xu hướng','','','/201610/',NULL,0,NULL,1476805321,1476805373,'quyettv','quyettv',1,2); /*Table structure for table `article_related` */ DROP TABLE IF EXISTS `article_related`; CREATE TABLE `article_related` ( `id` int(11) NOT NULL AUTO_INCREMENT, `article_id` int(11) NOT NULL, `related_id` int(11) NOT NULL, PRIMARY KEY (`id`), KEY `article_id` (`article_id`), KEY `related_id` (`related_id`), CONSTRAINT `article_related_ibfk_1` FOREIGN KEY (`article_id`) REFERENCES `article` (`id`) ON DELETE CASCADE ON UPDATE CASCADE, CONSTRAINT `article_related_ibfk_2` FOREIGN KEY (`related_id`) REFERENCES `article` (`id`) ON DELETE CASCADE ON UPDATE CASCADE ) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; /*Data for the table `article_related` */ insert into `article_related`(`id`,`article_id`,`related_id`) values (1,941,903); /*Table structure for table `article_to_tag` */ DROP TABLE IF EXISTS `article_to_tag`; CREATE TABLE `article_to_tag` ( `id` int(11) NOT NULL AUTO_INCREMENT, `article_id` int(11) NOT NULL, `tag_id` int(11) NOT NULL, PRIMARY KEY (`id`), UNIQUE KEY `UNIQUE` (`article_id`,`tag_id`), KEY `fk_tag_id_idx` (`tag_id`), CONSTRAINT `fk2_article_id` FOREIGN KEY (`article_id`) REFERENCES `article` (`id`) ON DELETE CASCADE ON UPDATE CASCADE, CONSTRAINT `fk_tag_id` FOREIGN KEY (`tag_id`) REFERENCES `tag` (`id`) ON DELETE CASCADE ON UPDATE CASCADE ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; /*Data for the table `article_to_tag` */ /*Table structure for table `auth_assignment` */ DROP TABLE IF EXISTS `auth_assignment`; CREATE TABLE `auth_assignment` ( `item_name` varchar(64) COLLATE utf8_unicode_ci NOT NULL, `user_id` varchar(64) COLLATE utf8_unicode_ci NOT NULL, `created_at` int(11) DEFAULT NULL, PRIMARY KEY (`item_name`,`user_id`), CONSTRAINT `auth_assignment_ibfk_1` FOREIGN KEY (`item_name`) REFERENCES `auth_item` (`name`) ON DELETE CASCADE ON UPDATE CASCADE ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; /*Data for the table `auth_assignment` */ insert into `auth_assignment`(`item_name`,`user_id`,`created_at`) values ('ADMIN','1',1452681631); /*Table structure for table `auth_item` */ DROP TABLE IF EXISTS `auth_item`; CREATE TABLE `auth_item` ( `name` varchar(64) COLLATE utf8_unicode_ci NOT NULL, `type` int(11) NOT NULL, `description` text COLLATE utf8_unicode_ci, `rule_name` varchar(64) COLLATE utf8_unicode_ci DEFAULT NULL, `data` text COLLATE utf8_unicode_ci, `created_at` int(11) DEFAULT NULL, `updated_at` int(11) DEFAULT NULL, PRIMARY KEY (`name`), KEY `rule_name` (`rule_name`), KEY `type` (`type`), CONSTRAINT `auth_item_ibfk_1` FOREIGN KEY (`rule_name`) REFERENCES `auth_rule` (`name`) ON DELETE SET NULL ON UPDATE CASCADE ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; /*Data for the table `auth_item` */ insert into `auth_item`(`name`,`type`,`description`,`rule_name`,`data`,`created_at`,`updated_at`) values ('/*',2,NULL,NULL,NULL,1452681631,1452681631),('ADMIN',2,NULL,NULL,NULL,1452681631,1452681631); /*Table structure for table `auth_item_child` */ DROP TABLE IF EXISTS `auth_item_child`; CREATE TABLE `auth_item_child` ( `parent` varchar(64) COLLATE utf8_unicode_ci NOT NULL, `child` varchar(64) COLLATE utf8_unicode_ci NOT NULL, PRIMARY KEY (`parent`,`child`), KEY `child` (`child`), CONSTRAINT `auth_item_child_ibfk_1` FOREIGN KEY (`parent`) REFERENCES `auth_item` (`name`) ON DELETE CASCADE ON UPDATE CASCADE, CONSTRAINT `auth_item_child_ibfk_2` FOREIGN KEY (`child`) REFERENCES `auth_item` (`name`) ON DELETE CASCADE ON UPDATE CASCADE ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; /*Data for the table `auth_item_child` */ insert into `auth_item_child`(`parent`,`child`) values ('ADMIN','/*'); /*Table structure for table `auth_rule` */ DROP TABLE IF EXISTS `auth_rule`; CREATE TABLE `auth_rule` ( `name` varchar(64) COLLATE utf8_unicode_ci NOT NULL, `data` text COLLATE utf8_unicode_ci, `created_at` int(11) DEFAULT NULL, `updated_at` int(11) DEFAULT NULL, PRIMARY KEY (`name`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; /*Data for the table `auth_rule` */ /*Table structure for table `contact` */ DROP TABLE IF EXISTS `contact`; CREATE TABLE `contact` ( `id` int(11) NOT NULL AUTO_INCREMENT, `name` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `address` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `message` varchar(2023) COLLATE utf8_unicode_ci DEFAULT NULL, `email` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `phone_number` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, PRIMARY KEY (`id`) ) ENGINE=InnoDB AUTO_INCREMENT=18 DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; /*Data for the table `contact` */ insert into `contact`(`id`,`name`,`address`,`message`,`email`,`phone_number`) values (16,'<NAME>',NULL,'Áo này có dễ giặt ko shop nhỉ','<EMAIL>',''),(17,'<NAME>',NULL,'gggggg','<EMAIL>','1643694807'); /*Table structure for table `customer` */ DROP TABLE IF EXISTS `customer`; CREATE TABLE `customer` ( `id` int(11) NOT NULL AUTO_INCREMENT, `username` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `password_hash` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `password_reset_token` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `auth_key` varchar(32) COLLATE utf8_unicode_ci NOT NULL, `email` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `phone_number` varchar(25) COLLATE utf8_unicode_ci DEFAULT NULL, `address` varchar(511) COLLATE utf8_unicode_ci DEFAULT NULL, `firstname` varchar(511) COLLATE utf8_unicode_ci DEFAULT NULL, `lastname` varchar(511) COLLATE utf8_unicode_ci DEFAULT NULL, `dob` int(11) DEFAULT NULL, `gender` tinyint(1) DEFAULT NULL, `image` varchar(511) COLLATE utf8_unicode_ci DEFAULT NULL, `image_path` varchar(511) COLLATE utf8_unicode_ci DEFAULT NULL, `language_id` int(11) DEFAULT NULL, `zip_postal_code` varchar(25) COLLATE utf8_unicode_ci DEFAULT NULL, `is_active` tinyint(1) NOT NULL DEFAULT '0', `status` smallint(6) NOT NULL DEFAULT '10', `created_at` int(11) NOT NULL, `updated_at` int(11) DEFAULT NULL, `total_purchase_orders` int(11) DEFAULT '0', `total_purchase_products` int(11) DEFAULT '0', `total_purchase_value` int(11) DEFAULT '0', `activation_token` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, PRIMARY KEY (`id`), UNIQUE KEY `username_UNIQUE` (`username`), UNIQUE KEY `email_UNIQUE` (`email`), UNIQUE KEY `password_reset_token_UNIQUE` (`password_reset_token`), KEY `fk7_language_id_idx` (`language_id`) ) ENGINE=InnoDB AUTO_INCREMENT=8 DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; /*Data for the table `customer` */ insert into `customer`(`id`,`username`,`password_<PASSWORD>`,`password_<PASSWORD>_<PASSWORD>`,`auth_key`,`email`,`phone_number`,`address`,`firstname`,`lastname`,`dob`,`gender`,`image`,`image_path`,`language_id`,`zip_postal_code`,`is_active`,`status`,`created_at`,`updated_at`,`total_purchase_orders`,`total_purchase_products`,`total_purchase_value`,`activation_token`) values (5,'quyet2','$2y$13$i/CLD0TENwb1bagcRS0BUuDSkwfqmeIzscoLmqWQ3KCrQO7TFg6kC',NULL,'K7VaIi_nq6Ke9UdikxnwYGzq1p6udJRQ','<EMAIL>','',NULL,NULL,NULL,0,NULL,'sale_70_banner_web_compressed_0610151906-57f9d1a4f0046.jpg','/u/201610/',NULL,NULL,0,1,1475989924,1476060843,0,0,0,NULL),(6,'quyet3','$2y$13$cv3OkDptozl8vE4seSv7wOOLNdUvggamU0oMA/CffK6zZq860kUEm',NULL,'HzI7oWcl1-ioL9LnhU3uu3nWD8w90TQB','<EMAIL>','+84 164 369 4807',NULL,'Trần','Văn Quyết',0,NULL,'cover_web_0210215157-57f9d389063c5.jpg','/u/201610/',NULL,NULL,0,1,1475990409,1476008734,0,0,0,NULL),(7,'quyettvq','$2y$13$ToErwWlDGwEhCkr0UVSu3OUpl3s/W9.vtTMX3Til7N65IdtBkTqN2',NULL,'buKt0RbOAxvovBy3UJzyZlmdYt1ineZX','<EMAIL>','',NULL,NULL,NULL,0,NULL,NULL,NULL,NULL,NULL,0,2,1476002039,1476002039,0,0,0,'YSXya3WaT2GOSOt6bzzg0RPNUWkeIQUd_1476002039'); /*Table structure for table `customer_log` */ DROP TABLE IF EXISTS `customer_log`; CREATE TABLE `customer_log` ( `id` int(11) NOT NULL AUTO_INCREMENT, `customer_id` int(11) NOT NULL, `action` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `object_class` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `object_pk` int(11) DEFAULT NULL, `created_at` int(11) NOT NULL, `is_success` tinyint(1) DEFAULT '0', PRIMARY KEY (`id`), KEY `fk_customer_id` (`customer_id`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; /*Data for the table `customer_log` */ /*Table structure for table `info` */ DROP TABLE IF EXISTS `info`; CREATE TABLE `info` ( `id` int(11) NOT NULL AUTO_INCREMENT, `name` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `type` smallint(4) NOT NULL, `slug` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `is_active` tinyint(1) DEFAULT NULL, `status` smallint(4) DEFAULT NULL, `page_title` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `h1` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `meta_title` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `meta_description` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `meta_keywords` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `long_description` text COLLATE utf8_unicode_ci, `description` varchar(511) COLLATE utf8_unicode_ci DEFAULT NULL, `content` text COLLATE utf8_unicode_ci NOT NULL, `image` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `image_path` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `old_slugs` varchar(2000) COLLATE utf8_unicode_ci DEFAULT NULL, `created_at` int(11) NOT NULL, `created_by` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `updated_at` int(11) DEFAULT NULL, `updated_by` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, PRIMARY KEY (`id`), UNIQUE KEY `UNIQUE2` (`slug`,`is_active`) ) ENGINE=InnoDB AUTO_INCREMENT=13 DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; /*Data for the table `info` */ insert into `info`(`id`,`name`,`type`,`slug`,`is_active`,`status`,`page_title`,`h1`,`meta_title`,`meta_description`,`meta_keywords`,`long_description`,`description`,`content`,`image`,`image_path`,`old_slugs`,`created_at`,`created_by`,`updated_at`,`updated_by`) values (11,'Giới thiệu về Veneto',2,'gioi-thieu-ve-veneto',1,NULL,'Giới thiệu về Veneto','Giới thiệu về Veneto','Giới thiệu về Veneto','','',NULL,NULL,'<div class=\"singer-entry\" style=\"width: 720px; font-size: 12px; margin:0 auto\">\r\n<img alt=\"\" src=\"http://veneto-quyettv.rhcloud.com/frontend/web/images/201610/1_2505162443.jpg\" style=\"border:none; height:490px; max-width:100%; width:700px\" /><br />\r\n<img alt=\"\" src=\"http://veneto-quyettv.rhcloud.com/frontend/web/images/201610/2_2505160725.jpg\" style=\"border:none; height:490px; max-width:100%; width:700px\" /><br />\r\n<br />\r\n<span style=\"font-size:14px\"><span style=\"font-size:16px\"><strong>GIỚI THIỆU VỀ VENETO</strong></span></span>\r\n\r\n<div>\r\n<hr /></div>\r\n\r\n<div style=\"text-align: justify;\"><span style=\"font-size:14px\">Với mong muốn mang những trải nghiệm thời trang ho&agrave;n to&agrave;n mới, tạo n&ecirc;n một c&aacute;i nh&igrave;n kh&aacute;c biệt về thời trang; gi&uacute;p ph&aacute;i mạnh th&ecirc;m tự tin khi lựa chọn những sản phẩm thời trang cao cấp - năm 2013&nbsp;<strong>C&ocirc;ng ty TNHH Thời trang Veneto&nbsp;</strong>đ&atilde; được th&agrave;nh lập.</span><br />\r\n&nbsp;</div>\r\n\r\n<div style=\"text-align: justify;\"><span style=\"font-size:14px\">Sự quản l&yacute; chặt chẽ, chuy&ecirc;n nghiệp của đội ngũ quản l&yacute; c&ugrave;ng với tinh thần l&agrave;m việc trẻ trung, s&aacute;ng tạo kh&ocirc;ng ngừng của bộ phận thiết kế - sản xu&aacute;t; sự tận t&acirc;m, chất lượng phục vụ được đ&agrave;o tạo b&agrave;i bản của nh&acirc;n vi&ecirc;n b&aacute;n h&agrave;ng&hellip; l&agrave; những yếu tố g&oacute;p phần l&agrave;m n&ecirc;n sự lớn mạnh của một trong những thương hiệu thời trang top đầu Việt Nam như&nbsp;<strong>Veneto</strong>&nbsp;hiện nay.</span></div>\r\n<br />\r\n<img alt=\"\" src=\"http://veneto-quyettv.rhcloud.com/frontend/web/images/201610/3_2505131948.jpg\" style=\"border:none; height:456px; max-width:100%; width:700px\" />\r\n<div style=\"text-align: justify;\"><br />\r\n<span style=\"font-size:14px\">Được c&aacute;c kh&aacute;ch h&agrave;ng biết tới như một thương hiệu mạnh, chuy&ecirc;n cung cấp c&aacute;c sản phẩm thời trang nam thiết kế,&nbsp;<strong>Veneto&nbsp;</strong>hiện đ&atilde; cho ra mắt thị trường h&agrave;ng ng&agrave;n sản phẩm đa dạng về kiểu d&aacute;ng, mẫu m&atilde;: từ những trang phục độc t&ocirc;n của c&aacute;nh m&agrave;y r&acirc;u như:&nbsp;<em>thời trang c&ocirc;ng sở, vest cưới, &aacute;o sơ mi, quần t&acirc;y,&hellip;&nbsp;</em>cho đến c&aacute;c trang phục thời trang như:&nbsp;<em>&aacute;o thun, &aacute;o kho&aacute;c, &aacute;o len, quần kaki&hellip;</em>&nbsp;c&ugrave;ng với c&aacute;c phụ kiện thời trang đều được thiết kế một c&aacute;ch ho&agrave;n hảo, hiện đại.<br />\r\n<br />\r\nCh&uacute;ng t&ocirc;i lu&ocirc;n quan niệm thời trang l&agrave; sự t&igrave;m t&ograve;i v&agrave; s&aacute;ng tạo kh&ocirc;ng ngừng; ch&iacute;nh v&igrave; l&yacute; do ấy m&agrave; c&aacute;c sản phẩm thời trang của&nbsp;<strong>Veneto</strong>&nbsp;đều được thiết kế với phong c&aacute;ch lịch l&atilde;m, m&agrave;u sắc trẻ trung, hiện đại lu&ocirc;n theo kịp những xu hướng thời trang tr&ecirc;n thế giới.&nbsp;<br />\r\n<br />\r\n<img alt=\"\" src=\"http://veneto-quyettv.rhcloud.com/frontend/web/images/201610/4_2005093538.jpg\" style=\"border:none; height:auto !important; max-width:100%; width:700px\" /><br />\r\n<br />\r\n<span style=\"font-size:16px\"><strong>TẦM NH&Igrave;N &ndash; SỨ MỆNH</strong></span></span>\r\n\r\n<div>\r\n<hr /></div>\r\n<span style=\"font-size:14px\">Việt Nam đang hội nhập với bạn b&egrave; quốc tế, mở ra nhiều cơ hội mới, v&igrave; vậy h&igrave;nh ảnh ph&aacute;i nam cần trở n&ecirc;n lịch l&atilde;m hơn, phong c&aacute;ch hơn để h&ograve;a nhập với sự ph&aacute;t triển của thế giới v&agrave; c&aacute;c xu hướng thời trang đang thịnh h&agrave;nh.<strong>Veneto&nbsp;</strong>lu&ocirc;n nỗ lực v&agrave; s&aacute;ng tạo kh&ocirc;ng ngừng để tạo ra những sản phẩm thời trang nam cao cấp, đ&aacute;p ứng tốt nhu cầu, thị hiếu của nam giới.<br />\r\n<br />\r\n<img alt=\"\" src=\"http://veneto-quyettv.rhcloud.com/frontend/web/images/201610/5_2505132147.jpg\" style=\"border:none; height:456px; max-width:100%; width:700px\" /><br />\r\n<br />\r\nB&ecirc;nh cạnh hoạt động kinh doanh, đội ngũ quản l&yacute; của Veneto mong muốn tạo ra một mội trường l&agrave;m việc hiện đại: ph&aacute;t huy sự năng động, nhiệt huyết v&agrave; hiệu quả cho c&aacute;c bạn nh&acirc;n vi&ecirc;n trẻ.<br />\r\n<br />\r\n<strong>Veneto</strong>&nbsp;đặc biệt quan t&acirc;m v&agrave; lu&ocirc;n hướng tới cộng đồng, ch&uacute;ng t&ocirc;i lu&ocirc;n cố gắng đ&oacute;ng g&oacute;p cho x&atilde; hội những gi&aacute; trị hữu &iacute;ch nhất, thiết thực nhất từ ch&iacute;nh kết quả của hoạt động kinh doanh của c&ocirc;ng ty.</span><br />\r\n<br />\r\n<img alt=\"\" src=\"http://veneto-quyettv.rhcloud.com/frontend/web/images/201610/6_2005094459.jpg\" style=\"border:none; height:490px; max-width:100%; width:700px\" /><br />\r\n<br />\r\n&nbsp;<br />\r\n<span style=\"color:rgb(0, 0, 0)\"><span style=\"font-size:14px\"><span style=\"font-size:16px\"><strong>GI&Aacute; TRỊ CỐT L&Otilde;I</strong></span></span></span>\r\n\r\n<div>\r\n<hr /></div>\r\n<strong>Veneto&nbsp;</strong><span style=\"color:rgb(0, 0, 0); font-size:14px\">x&acirc;y dựng h&igrave;nh ảnh thời trang nam kh&aacute;c biệt. Đề cao yếu tố sang trọng, lịch l&atilde;m trong từng đường n&eacute;t thiết kế - chất liệu của sản phẩm. Ch&uacute;ng t&ocirc;i lu&ocirc;n nỗ lực mang những sản phẩm thời trang cao cấp đến gần hơn với b&agrave;n tay người ti&ecirc;u d&ugrave;ng tr&ecirc;n khắp cả nước v&agrave; vươn xa hơn tại thị trường thế giới n&oacute;i chung, khu vực Đ&ocirc;ng Nam &Aacute; n&oacute;i ri&ecirc;ng.</span>&nbsp;<br />\r\n<br />\r\n<br />\r\n<span style=\"font-size:14px\"><span style=\"color:rgb(0, 0, 0)\"><strong><img alt=\"\" src=\"http://veneto-quyettv.rhcloud.com/frontend/web/images/201610/7_2005101243.jpg\" style=\"border:none; height:490px; max-width:100%; width:700px\" /><br />\r\n<br />\r\n<span style=\"font-size:16px\">CAM KẾT VỀ CHẤT LƯỢNG SẢN PHẨM</span></strong></span></span>\r\n\r\n<div>\r\n<hr /></div>\r\n<span style=\"font-size:14px\"><span style=\"color:rgb(0, 0, 0)\">&nbsp;<br />\r\nVới bề d&agrave;y kinh nghiệm v&agrave; &uacute;y t&iacute;n tr&ecirc;n tr&ecirc;n thị trường thời trang, gi&aacute; trị của c&aacute;c mặt h&agrave;ng được sản xuất thủ c&ocirc;ng tạo ra đ&atilde; được khẳng định bằng những đ&aacute;nh gi&aacute; tốt từ ph&iacute;a người ti&ecirc;u d&ugrave;ng. Sản phẩm thời trang của&nbsp;<strong>Veneto</strong>đem lại sự thoải m&aacute;i, diện mạo sang trọng, lịch l&atilde;m cho người sử dụng. Được sản xuất từ những kiệt t&aacute;c về kỹ thuật may đo, c&aacute;c sản phẩm thời trang của Veneto l&agrave; c&acirc;n bằng ho&agrave;n hảo của c&aacute;c yếu tố:&nbsp;<em><strong>thời trang, phong c&aacute;ch, lịch sử, văn h&oacute;a.&nbsp;</strong></em>&nbsp;&nbsp;&nbsp;<br />\r\n<br />\r\n<img alt=\"\" src=\"http://veneto-quyettv.rhcloud.com/frontend/web/images/201610/8_2505132356.jpg\" style=\"border:none; height:456px; max-width:100%; width:700px\" /><br />\r\n<br />\r\nCh&uacute;ng t&ocirc;i sử dụng loại vải cao cấp nhập khẩu từ H&agrave;n Quốc: đảm bảo sự bền l&acirc;u về m&agrave;u sắc, form d&aacute;ng của sản phẩm cũng như gi&uacute;p người mặc c&oacute; cảm gi&aacute;c dễ chịu khi diện đồ.<br />\r\n&nbsp;</span></span><br />\r\n<br />\r\n<img alt=\"\" src=\"http://veneto-quyettv.rhcloud.com/frontend/web/images/201610/9_2005103511.jpg\" style=\"border:none; height:490px; max-width:100%; width:700px\" /><br />\r\n<br />\r\n<span style=\"font-size:16px\"><span style=\"color:rgb(0, 0, 0)\"><strong>HOẠT ĐỘNG X&Atilde; HỘI</strong></span></span>\r\n\r\n<div>\r\n<hr /></div>\r\n<span style=\"font-size:14px\"><span style=\"color:rgb(0, 0, 0)\">B&ecirc;n cạnh hoạt động kinh doanh ng&agrave;nh h&agrave;ng thời trang,&nbsp;<strong>C&ocirc;ng ty TNHH Thời trang Veneto</strong>&nbsp;cũng t&iacute;ch cực tham gia c&aacute;c hoạt động x&atilde; hội, c&aacute;c chương tr&igrave;nh cộng đồng. Trong những năm qua, thương hiệu Veneto đ&atilde; tham gia t&agrave;i trợ cho c&aacute;c chương tr&igrave;nh, c&aacute;c cuộc thi tại một số trường Đại học như:&nbsp;<em>ĐH Ngoại thương, ĐH Kinh doanh &ndash; C&ocirc;ng nghệ, ĐH Thương mại,&hellip;</em>&nbsp;gi&uacute;p c&aacute;c bạn sinh vi&ecirc;n tỏa s&aacute;ng, thực hiện ước mơ của bản th&acirc;n.<br />\r\n<br />\r\n<img alt=\"\" src=\"http://veneto-quyettv.rhcloud.com/frontend/web/images/201610/10_2505132615.jpg\" style=\"border:none; height:456px; max-width:100%; width:700px\" /><br />\r\n<br />\r\nĐội ngũ c&aacute;n bộ, nh&acirc;n vi&ecirc;n c&ocirc;ng ty cũng đ&atilde; c&oacute; những chuyến đi tới c&aacute;c bản l&agrave;ng v&ugrave;ng cao, tổ chức những chương tr&igrave;nh thiện nguyện, gi&uacute;p đỡ trẻ em ngh&egrave;o &ndash; kh&ocirc;ng được đến trường; những gia đ&igrave;nh ho&agrave;n cảnh kh&oacute; khăn. Với mong muốn san sẻ phần n&agrave;o những kh&oacute; khăn, gi&uacute;p x&atilde; hội ng&agrave;y c&agrave;ng gi&agrave;u mạnh&nbsp;<strong>Veneto</strong>&nbsp;đ&atilde; hiện thực h&oacute;a những mong muốn ấy bằng h&agrave;nh động c&oacute; &iacute;ch cho cộng đồng.</span></span><br />\r\n<br />\r\n<img alt=\"\" src=\"http://veneto-quyettv.rhcloud.com/frontend/web/images/201610/11_2005110430.jpg\" style=\"border:none; height:490px; max-width:100%; width:700px\" /><br />\r\n<br />\r\n<br />\r\n<span style=\"font-size:14px\"><span style=\"font-size:16px\"><span style=\"color:rgb(0, 0, 0)\"><strong>HỆ THỐNG SHOWROOM</strong></span></span></span>\r\n\r\n<div>\r\n<hr /></div>\r\n<span style=\"color:rgb(0, 0, 0)\"><span style=\"font-size:14px\">Hiện tại&nbsp;<strong>Veneto</strong>&nbsp;đ&atilde; c&oacute; 10 cửa h&agrave;ng sang trọng, quy m&ocirc; nằm tại H&agrave; Nội v&agrave; c&aacute;c tỉnh th&agrave;nh kh&aacute;c với hơn 16 đại l&yacute; cấp 2.&nbsp;</span></span><span style=\"font-size:14px\"><span style=\"color:rgb(0, 0, 0)\">Veneto kh&ocirc;ng ngừng vươn m&igrave;nh, mở rộng mạng lưới chi nh&aacute;nh tr&ecirc;n khắp cả nước; đưa c&aacute;c sản phẩm thời trang cao cấp tới gần hơn b&agrave;n tay người ti&ecirc;u d&ugrave;ng.<br />\r\n<br />\r\n<img alt=\"\" src=\"http://veneto-quyettv.rhcloud.com/frontend/web/images/201610/12_2505132931.jpg\" style=\"border:none; height:929px; max-width:100%; width:700px\" /><br />\r\n&nbsp;<br />\r\nQuan trọng hơn, kh&ocirc;ng chỉ đặt mục ti&ecirc;u về số lượng, Veneto đặc biệt ch&uacute; trọng h&agrave;ng đấu đến chất lượng của từng showroom: thiết kế, c&aacute;ch b&agrave;y tr&iacute; sản phẩm v&agrave; quan trọng nhất đ&oacute; l&agrave; chất lượng phục vụ.<br />\r\n<br />\r\nĐể l&agrave;m h&agrave;i l&ograve;ng v&agrave; thỏa m&atilde;n tốt nhất kh&aacute;ch h&agrave;ng đến mua sắm, ch&uacute;ng t&ocirc;i gi&aacute;m s&aacute;t chặt chẽ to&agrave;n bộ hệ thống showroom tr&ecirc;n to&agrave;n quốc; lu&ocirc;n lu&ocirc;n đặt chỉ ti&ecirc;u, khuyến kh&iacute;ch nh&acirc;n vi&ecirc;n. B&ecirc;n cạnh đ&oacute;, Veneto thường xuy&ecirc;n tổ chức c&aacute;c hoạt động traning kỹ năng tư vấn, phục vụ kh&aacute;ch h&agrave;ng cho nh&acirc;n vi&ecirc;n; kiểm tra, đ&aacute;nh gi&aacute; thường kỳ. Với những sự đầu tư đ&oacute;, Veneto kỳ vọng sẽ lu&ocirc;n l&agrave; địa chỉ mua sắm tin cậy, l&agrave; h&igrave;nh ảnh đầu ti&ecirc;n trong t&acirc;m tr&iacute; kh&aacute;ch h&agrave;ng khi nghĩ về thời trang nam</span></span><br />\r\n<br />\r\n<br />\r\n<strong><span style=\"color:rgb(29, 33, 41); font-family:helvetica,arial,sans-serif; font-size:14px\">HỆ THỐNG SHOWROOM CỦA VENETO</span></strong>\r\n\r\n<hr />\r\n<div style=\"margin-left: 40px;\"><span style=\"color:rgb(29, 33, 41); font-family:helvetica,arial,sans-serif; font-size:14px\">■ STORE 1 : 27 QU&Aacute;N TH&Aacute;NH - HN</span><br />\r\n<span style=\"color:rgb(29, 33, 41); font-family:helvetica,arial,sans-serif; font-size:14px\">■ STORE 2 : 259 CH&Ugrave;A BỘC - HN</span><br />\r\n<span style=\"color:rgb(29, 33, 41); font-family:helvetica,arial,sans-serif; font-size:14px\">■ STORE 3 : 126 CẦU GIẤY - HN</span><br />\r\n<span style=\"color:rgb(29, 33, 41); font-family:helvetica,arial,sans-serif; font-size:14px\">■ STORE 4 : 93 XU&Acirc;N THỦY &ndash; HN</span><br />\r\n<span style=\"color:rgb(29, 33, 41); font-family:helvetica,arial,sans-serif; font-size:14px\">■ STORE 5: 19 PHỐ HUẾ - HN&nbsp;</span><br />\r\n<span style=\"color:rgb(29, 33, 41); font-family:helvetica,arial,sans-serif; font-size:14px\">■ STORE 6 : 32 TRẦN HƯNG ĐẠO - HẢI DƯƠNG</span><br />\r\n<span style=\"color:rgb(29, 33, 41); font-family:helvetica,arial,sans-serif; font-size:14px\">■ STORE 7 : 52 M&Ecirc; LINH - L&Ecirc; CH&Acirc;N - HẢI PH&Ograve;NG</span><br />\r\n<span style=\"color:rgb(29, 33, 41); font-family:helvetica,arial,sans-serif; font-size:14px\">■ STORE 8 : HẠ LONG - QUẢNG NINH (OPENING SOON)</span><br />\r\n<span style=\"color:rgb(29, 33, 41); font-family:helvetica,arial,sans-serif; font-size:14px\">■ STORE 9 : 316 L&Ecirc; VĂN SỸ - TP.HCM</span><br />\r\n<span style=\"color:rgb(29, 33, 41); font-family:helvetica,arial,sans-serif; font-size:14px\">■ STORE 10 : VI&Ecirc;NG CHĂN - L&Agrave;O</span></div>\r\n\r\n<div>&nbsp;</div>\r\n</div>\r\n</div>\r\n\r\n<div class=\"face-book\" style=\"float: left; width: 720px; clear: both; font-family: Arial, Helvetica, sans-serif; font-size: 12px;\">&nbsp;</div>\r\n','','/201610/',NULL,1475920768,'quyettv',1475921731,'quyettv'),(12,'Chính sách đại lý',5,'chinh-sach-dai-ly',1,NULL,'Chính sách đại lý','Chính sách đại lý','Chính sách đại lý','','',NULL,NULL,'<p>Ch&iacute;nh s&aacute;ch hợp t&aacute;c b&aacute;n h&agrave;ng đại l&yacute;</p>\r\n','','/201610/',NULL,1476029598,'quyettv',NULL,NULL); /*Table structure for table `migration` */ DROP TABLE IF EXISTS `migration`; CREATE TABLE `migration` ( `version` varchar(180) COLLATE utf8_unicode_ci NOT NULL, `apply_time` int(11) DEFAULT NULL, PRIMARY KEY (`version`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; /*Data for the table `migration` */ /*Table structure for table `product` */ DROP TABLE IF EXISTS `product`; CREATE TABLE `product` ( `id` int(11) NOT NULL AUTO_INCREMENT, `category_id` int(11) DEFAULT NULL, `name` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `label` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `slug` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `code` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `old_slugs` varchar(2000) COLLATE utf8_unicode_ci DEFAULT NULL, `price` int(11) DEFAULT '0', `original_price` int(11) DEFAULT '0', `image` varchar(511) COLLATE utf8_unicode_ci DEFAULT NULL, `banner` varchar(511) COLLATE utf8_unicode_ci DEFAULT NULL, `image_path` varchar(511) COLLATE utf8_unicode_ci DEFAULT NULL, `description` varchar(511) COLLATE utf8_unicode_ci DEFAULT NULL, `long_description` text COLLATE utf8_unicode_ci, `details` text COLLATE utf8_unicode_ci, `content` text COLLATE utf8_unicode_ci, `page_title` varchar(511) COLLATE utf8_unicode_ci DEFAULT NULL, `h1` varchar(511) COLLATE utf8_unicode_ci DEFAULT NULL, `meta_title` varchar(511) COLLATE utf8_unicode_ci DEFAULT NULL, `meta_description` varchar(511) COLLATE utf8_unicode_ci DEFAULT NULL, `meta_keywords` varchar(511) COLLATE utf8_unicode_ci DEFAULT NULL, `is_hot` tinyint(1) DEFAULT NULL, `is_active` tinyint(1) DEFAULT NULL, `status` tinyint(2) DEFAULT NULL, `sort_order` int(11) DEFAULT NULL, `view_count` int(11) DEFAULT '0', `like_count` int(11) DEFAULT '0', `share_count` int(11) DEFAULT '0', `comment_count` int(11) DEFAULT '0', `published_at` int(11) NOT NULL, `created_at` int(11) NOT NULL, `updated_at` int(11) DEFAULT NULL, `created_by` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `updated_by` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `auth_alias` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `available_quantity` int(11) DEFAULT '0', `order_quantity` int(11) DEFAULT '0', `sold_quantity` int(11) DEFAULT '0', `total_quantity` int(11) DEFAULT '0', `total_revenue` int(11) DEFAULT '0', `review_score` int(11) DEFAULT '0', `manufacturer` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `color` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `malterial` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `style` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `use_duration` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `manufacturing_date` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `size` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `weight` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `ingredient` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `model` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `type` tinyint(2) DEFAULT NULL, PRIMARY KEY (`id`), UNIQUE KEY `slug_UNIQUE` (`slug`), KEY `category_id` (`category_id`), CONSTRAINT `product_ibfk_1` FOREIGN KEY (`category_id`) REFERENCES `product_category` (`id`) ON DELETE CASCADE ON UPDATE CASCADE ) ENGINE=InnoDB AUTO_INCREMENT=28 DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; /*Data for the table `product` */ insert into `product`(`id`,`category_id`,`name`,`label`,`slug`,`code`,`old_slugs`,`price`,`original_price`,`image`,`banner`,`image_path`,`description`,`long_description`,`details`,`content`,`page_title`,`h1`,`meta_title`,`meta_description`,`meta_keywords`,`is_hot`,`is_active`,`status`,`sort_order`,`view_count`,`like_count`,`share_count`,`comment_count`,`published_at`,`created_at`,`updated_at`,`created_by`,`updated_by`,`auth_alias`,`available_quantity`,`order_quantity`,`sold_quantity`,`total_quantity`,`total_revenue`,`review_score`,`manufacturer`,`color`,`malterial`,`style`,`use_duration`,`manufacturing_date`,`size`,`weight`,`ingredient`,`model`,`type`) values (26,17,'Xe đẩy Combi Granpaseo LZ600',NULL,'xe-day-combi-granpaseo-lz600','CG445',NULL,9990000,11100000,'XE-DAY-COMBI-GRANPASEO-LZ600.jpg',NULL,'/201610/','',NULL,NULL,'<p style=\"text-align:justify\">Xe đẩy du lịch cho b&eacute; BaoBaoHao 711B rất tiện dụng trong việc chăm s&oacute;c b&eacute;, đưa b&eacute; ra ngo&agrave;i, cho b&eacute; đi chơi hoặc đi mua sắm c&ugrave;ng bố mẹ. Sản phẩm c&oacute; thiết kế đẹp mắt, nhiều t&iacute;nh năng vượt trội v&agrave; sự cải tiến hơn so với những chiếc xe đẩy em b&eacute; b&igrave;nh thường kh&aacute;c n&ecirc;n hiện đang được rất nhiều gia đ&igrave;nh tại Việt Nam ưa chuộng.</p>\r\n\r\n<p>&nbsp;</p>\r\n\r\n<p style=\"text-align:center\"><img alt=\"Xe đẩy du lịch BaoHaoHao 711B\" src=\"//localhost/bongyeu.vn/frontend/web/images/201610/xe-day-du-lich-baohaohao-711b.jpg\" style=\"border:0px; box-shadow:rgb(0, 0, 0) 0em 0em 0em; margin:0px; padding:0px; vertical-align:top\" title=\"Xe đẩy du lịch BaoHaoHao 711B\" /></p>\r\n\r\n<p style=\"text-align:center\"><em>Xe đẩy du lịch cho b&eacute; BaoBaoHao 711B</em></p>\r\n\r\n<h2 style=\"text-align:justify\">Đặc điểm nổi bật của xe đẩy trẻ em BaoBaoHao 711B</h2>\r\n\r\n<ul>\r\n <li>Xe đẩy BaoBaoHao 711B&nbsp;được sản xuất theo ti&ecirc;u chuẩn ch&acirc;u &Acirc;u EN1888, đ&aacute;p ứng được những y&ecirc;u cầu khắt khe nhất về chất lượng cũng như độ an to&agrave;n.</li>\r\n <li>Xe c&oacute; thiết kế nổi bật v&agrave; m&agrave;u sắc bắt mắt, dễ d&agrave;ng chiếm được cảm t&igrave;nh của c&aacute;c bậc phụ huynh.</li>\r\n <li>Kết cấu khung bằng hợp kim chịu lực chắc chắn, chất liệu vải bọc cao cấp v&agrave; lớp nệm &ecirc;m &aacute;i, thấm h&uacute;t mồ h&ocirc;i tốt, đặc biệt l&agrave; an to&agrave;n cho sức khỏe của b&eacute;.</li>\r\n <li>Thiết kế lớp lưới tho&aacute;ng kh&iacute;, c&oacute; cửa sổ PU trong đ&oacute;n &aacute;nh s&aacute;ng v&agrave; hệ thống lưới chống n&oacute;ng, kết hợp ghế ngồi cao hơn so với mặt đất, gi&uacute;p tạo khoảng c&aacute;ch cho trẻ khỏi sức n&oacute;ng v&agrave; bụi bẩn, cho khoảng c&aacute;ch an to&agrave;n cho trẻ khỏi sức n&oacute;ng của mặt đất, mặt đường.</li>\r\n <li>Xe đẩy em b&eacute; 711B&nbsp;c&oacute; giỏ đựng đồ lớn, tiện dụng để ba mẹ đựng c&aacute;c loại quần &aacute;o v&agrave; vật dụng chăm s&oacute;c cho b&eacute; khi ra ngo&agrave;i; hoặc đựng đồ d&ugrave;ng vật dụng khi ba mẹ c&oacute; nhu cầu đi mua sắm.</li>\r\n <li>Khoang xe rộng r&atilde;i v&agrave; tho&aacute;ng m&aacute;t, ph&ugrave; hợp với sự ph&aacute;t triển của b&eacute; qua nhiều giai đoạn.</li>\r\n</ul>\r\n\r\n<p>&nbsp;</p>\r\n\r\n<p style=\"text-align:center\"><img alt=\"Xe đẩy du lịch BaoHaoHao 711B\" src=\"//localhost/bongyeu.vn/frontend/web/images/201610/xe-day-du-lich-baohaohao-711b-nauy.jpg\" style=\"border:0px; box-shadow:rgb(0, 0, 0) 0em 0em 0em; margin:0px; padding:0px; vertical-align:top\" title=\"Xe đẩy du lịch BaoHaoHao 711B\" /></p>\r\n\r\n<p style=\"text-align:center\"><em>Xe đẩy du lịch BaoBaoHao 711B c&oacute; 2 m&agrave;u sắc lựa chọn</em></p>\r\n\r\n<h2 style=\"text-align:justify\">Lưu &yacute; cho bố mẹ khi chọn mua xe đẩy cho b&eacute;:</h2>\r\n\r\n<ul>\r\n <li>Với b&eacute; dưới 6 th&aacute;ng tuổi, b&eacute; chưa c&oacute; khả năng ngồi vững được v&igrave; xương sống của b&eacute; c&ograve;n chưa ổn định, ba mẹ n&ecirc;n chọn cho b&eacute; d&ograve;ng xe đẩy c&oacute; thể nằm được (tốt nhất l&agrave; c&aacute;c loại xe c&oacute; đầy đủ c&aacute;c tư thế nằm, ngồi, ngả ...); c&aacute;c chế độ ngả v&agrave; ngồi sẽ được sử dụng khi b&eacute; hơn 6 th&aacute;ng.</li>\r\n <li>Xe đẩy 2 chiều sẽ tốt hơn 1 chiều, gi&uacute;p bố mẹ c&oacute; thể hướng mặt v&agrave;o b&eacute;, giao tiếp với b&eacute;, vui đ&ugrave;a c&ugrave;ng b&eacute; khi đưa b&eacute; ra ngo&agrave;i, b&eacute; sẽ cảm thấy th&iacute;ch th&uacute;, kh&ocirc;ng c&ograve;n cảm gi&aacute;c lo lắng sợ sệt...</li>\r\n <li>Ba mẹ n&ecirc;n chọn mua những sản phẩm xe đẩy c&oacute; thương hiệu tại những địa điểm ph&acirc;n phối uy t&iacute;n, đảm bảo sở hữu được sản phẩm chất lượng với gi&aacute; th&agrave;nh hợp l&yacute;.</li>\r\n</ul>\r\n\r\n<p>&nbsp;</p>\r\n\r\n<p style=\"text-align:center\"><em><img alt=\"Xe đẩy du lịch BaoHaoHao 711B\" src=\"//localhost/bongyeu.vn/frontend/web/images/201610/xe-day-du-lich-baohaohao-711b-nau.jpg\" style=\"border:0px; box-shadow:rgb(0, 0, 0) 0em 0em 0em; margin:0px; padding:0px; vertical-align:top\" title=\"Xe đẩy du lịch BaoHaoHao 711B\" /></em></p>\r\n\r\n<p style=\"text-align:center\"><em><img alt=\"Xe đẩy du lịch BaoHaoHao 711B\" src=\"//localhost/bongyeu.vn/frontend/web/images/201610/xe-day-du-lich-baohaohao-711b-hd.jpg\" style=\"border:0px; box-shadow:rgb(0, 0, 0) 0em 0em 0em; margin:0px; padding:0px; vertical-align:top\" title=\"Xe đẩy du lịch BaoHaoHao 711B\" /></em></p>\r\n\r\n<p style=\"text-align:center\"><em>C&aacute;ch gấp Xe đẩy du lịch BaoBaoHao 711B&nbsp;</em></p>\r\n\r\n<p><em>Tham khảo th&ecirc;m thật nhiều mẫu xe đẩy tiện dụng kh&aacute;c cho b&eacute;&nbsp;<a href=\"http://babimart.com/xe-tre-em/xe-day-em-be/?limit=30\" style=\"margin: 0px; padding: 0px; text-decoration: none; color: rgb(68, 68, 68);\">tại đ&acirc;y</a>!</em></p>\r\n','Xe đẩy Combi Granpaseo LZ600','Xe đẩy Combi Granpaseo LZ600','Xe đẩy Combi Granpaseo LZ600','','',0,1,NULL,NULL,334,0,0,0,1477466179,1477466500,1477483419,'quyettv','quyettv',NULL,29,0,0,30,0,0,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL),(27,17,'Xe đẩy Combi Well Comfort Cozy WT-200D',NULL,'xe-day-combi-well-comfort-cozy-wt-200d','',NULL,NULL,NULL,'fqi1461238357.jpg',NULL,'/201610/','',NULL,NULL,'','Xe đẩy Combi Well Comfort Cozy WT-200D','Xe đẩy Combi Well Comfort Cozy WT-200D','Xe đẩy Combi Well Comfort Cozy WT-200D','','',0,1,NULL,NULL,35,0,0,0,1477476869,1477477345,1477916394,'quyettv','quyettv',NULL,0,0,0,0,0,0,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL); /*Table structure for table `product_attribute` */ DROP TABLE IF EXISTS `product_attribute`; CREATE TABLE `product_attribute` ( `id` int(11) NOT NULL AUTO_INCREMENT, `group_id` int(11) NOT NULL, `name` varchar(511) COLLATE utf8_unicode_ci NOT NULL, `label` varchar(511) COLLATE utf8_unicode_ci DEFAULT NULL, `sort_order` int(11) DEFAULT NULL, PRIMARY KEY (`id`), KEY `group_id` (`group_id`), CONSTRAINT `product_attribute_ibfk_1` FOREIGN KEY (`group_id`) REFERENCES `product_attribute_group` (`id`) ON DELETE CASCADE ON UPDATE CASCADE ) ENGINE=InnoDB AUTO_INCREMENT=7 DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; /*Data for the table `product_attribute` */ insert into `product_attribute`(`id`,`group_id`,`name`,`label`,`sort_order`) values (1,1,'2 - 5 tuổi',NULL,NULL),(2,1,'5 - 7 tuổi',NULL,NULL),(3,1,'7 - 10 tuổi',NULL,NULL),(4,2,'Seebaby',NULL,NULL),(5,2,'Baohaohao',NULL,NULL),(6,2,'Combi Corporation Japan','<span class=\"text-dark-blue\">Combi Corporation Japan</span>',NULL); /*Table structure for table `product_attribute_group` */ DROP TABLE IF EXISTS `product_attribute_group`; CREATE TABLE `product_attribute_group` ( `id` int(11) NOT NULL AUTO_INCREMENT, `name` varchar(511) COLLATE utf8_unicode_ci NOT NULL, `label` varchar(511) COLLATE utf8_unicode_ci DEFAULT NULL, `sort_order` int(11) DEFAULT NULL, PRIMARY KEY (`id`) ) ENGINE=InnoDB AUTO_INCREMENT=3 DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; /*Data for the table `product_attribute_group` */ insert into `product_attribute_group`(`id`,`name`,`label`,`sort_order`) values (1,'Độ tuổi',NULL,2),(2,'Hãng sản xuất',NULL,1); /*Table structure for table `product_category` */ DROP TABLE IF EXISTS `product_category`; CREATE TABLE `product_category` ( `id` int(11) NOT NULL AUTO_INCREMENT, `name` varchar(255) COLLATE utf8_unicode_ci NOT NULL DEFAULT '', `label` varchar(255) COLLATE utf8_unicode_ci DEFAULT '', `slug` varchar(255) COLLATE utf8_unicode_ci NOT NULL DEFAULT '', `old_slugs` varchar(2000) COLLATE utf8_unicode_ci DEFAULT '', `parent_id` int(11) DEFAULT NULL, `description` varchar(511) COLLATE utf8_unicode_ci DEFAULT '', `long_description` text COLLATE utf8_unicode_ci, `page_title` varchar(511) COLLATE utf8_unicode_ci DEFAULT '', `h1` varchar(511) COLLATE utf8_unicode_ci DEFAULT '', `meta_title` varchar(511) COLLATE utf8_unicode_ci DEFAULT '', `meta_description` varchar(511) COLLATE utf8_unicode_ci DEFAULT '', `meta_keywords` varchar(511) COLLATE utf8_unicode_ci DEFAULT '', `image` varchar(511) COLLATE utf8_unicode_ci DEFAULT '', `banner` varchar(511) COLLATE utf8_unicode_ci DEFAULT '', `image_path` varchar(511) COLLATE utf8_unicode_ci DEFAULT '', `is_hot` tinyint(1) DEFAULT NULL, `is_active` tinyint(1) DEFAULT NULL, `status` tinyint(2) DEFAULT NULL, `sort_order` int(11) DEFAULT NULL, `created_at` int(11) NOT NULL, `updated_at` int(11) DEFAULT NULL, `created_by` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `updated_by` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `type` tinyint(2) DEFAULT NULL, PRIMARY KEY (`id`), UNIQUE KEY `slug` (`slug`), KEY `fk2_parent_idx` (`parent_id`), CONSTRAINT `product_category_ibfk_1` FOREIGN KEY (`parent_id`) REFERENCES `product_category` (`id`) ON DELETE SET NULL ON UPDATE CASCADE ) ENGINE=InnoDB AUTO_INCREMENT=20 DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; /*Data for the table `product_category` */ insert into `product_category`(`id`,`name`,`label`,`slug`,`old_slugs`,`parent_id`,`description`,`long_description`,`page_title`,`h1`,`meta_title`,`meta_description`,`meta_keywords`,`image`,`banner`,`image_path`,`is_hot`,`is_active`,`status`,`sort_order`,`created_at`,`updated_at`,`created_by`,`updated_by`,`type`) values (17,'Xe đẩy cho bé','<i class=\"icon stroller-icon\"></i>&nbsp; Xe đẩy cho bé','xe-day-cho-be','',NULL,'','','Xe đẩy cho bé','Xe đẩy cho bé','Xe đẩy cho bé','','','','','/201610/',0,1,NULL,NULL,1477464145,NULL,'quyettv',NULL,NULL),(18,'Xe đạp cho bé','<i class=\"icon bicycle-icon\"></i>&nbsp; Xe đạp cho bé','xe-dap-cho-be','',NULL,'','','Xe đạp cho bé','Xe đạp cho bé','Xe đạp cho bé','','','','','/201610/',0,1,NULL,NULL,1477464209,NULL,'quyettv',NULL,NULL),(19,'Xe lắc cho bé','<i class=\"icon swing-car-icon\"></i>&nbsp; Xe lắc cho bé','xe-lac-cho-be','',NULL,'','','Xe lắc cho bé','Xe lắc cho bé','Xe lắc cho bé','','','','','/201610/',0,1,NULL,NULL,1477464663,NULL,'quyettv',NULL,NULL); /*Table structure for table `product_customization` */ DROP TABLE IF EXISTS `product_customization`; CREATE TABLE `product_customization` ( `id` int(11) NOT NULL AUTO_INCREMENT, `product_id` int(11) NOT NULL, `name` varchar(511) COLLATE utf8_unicode_ci NOT NULL, `label` varchar(511) COLLATE utf8_unicode_ci DEFAULT NULL, `review_score` int(11) DEFAULT '0', `order_quantity` int(11) DEFAULT '0', `sold_quantity` int(11) DEFAULT '0', `available_quantity` int(11) DEFAULT '0', `total_quantity` int(11) DEFAULT '0', `price` int(11) DEFAULT '0', `original_price` int(11) DEFAULT '0', `total_revenue` int(11) DEFAULT '0', `sort_order` int(11) DEFAULT NULL, PRIMARY KEY (`id`), KEY `product_id` (`product_id`), CONSTRAINT `product_customization_ibfk_1` FOREIGN KEY (`product_id`) REFERENCES `product` (`id`) ON DELETE CASCADE ON UPDATE CASCADE ) ENGINE=InnoDB AUTO_INCREMENT=4 DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; /*Data for the table `product_customization` */ insert into `product_customization`(`id`,`product_id`,`name`,`label`,`review_score`,`order_quantity`,`sold_quantity`,`available_quantity`,`total_quantity`,`price`,`original_price`,`total_revenue`,`sort_order`) values (1,26,'Màu đỏ','',0,0,0,19,20,8000000,NULL,0,NULL),(2,26,'Màu xanh','',0,0,0,10,10,12000000,12100000,0,NULL),(3,26,'Màu trắng','',0,0,0,NULL,NULL,NULL,NULL,0,NULL); /*Table structure for table `product_customization_to_image` */ DROP TABLE IF EXISTS `product_customization_to_image`; CREATE TABLE `product_customization_to_image` ( `id` int(11) NOT NULL AUTO_INCREMENT, `customization_id` int(11) NOT NULL, `image_id` int(11) NOT NULL, PRIMARY KEY (`id`), KEY `customization_id` (`customization_id`), KEY `image_id` (`image_id`), CONSTRAINT `product_customization_to_image_ibfk_1` FOREIGN KEY (`customization_id`) REFERENCES `product_customization` (`id`) ON DELETE CASCADE ON UPDATE CASCADE, CONSTRAINT `product_customization_to_image_ibfk_2` FOREIGN KEY (`image_id`) REFERENCES `product_image` (`id`) ON DELETE CASCADE ON UPDATE CASCADE ) ENGINE=InnoDB AUTO_INCREMENT=11 DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; /*Data for the table `product_customization_to_image` */ insert into `product_customization_to_image`(`id`,`customization_id`,`image_id`) values (1,2,1),(4,2,2),(5,2,13),(6,1,4),(7,1,5),(8,1,11),(9,3,9),(10,3,10); /*Table structure for table `product_customization_to_option` */ DROP TABLE IF EXISTS `product_customization_to_option`; CREATE TABLE `product_customization_to_option` ( `id` int(11) NOT NULL AUTO_INCREMENT, `customization_id` int(11) NOT NULL, `option_id` int(11) NOT NULL, PRIMARY KEY (`id`), KEY `statistic_id` (`customization_id`), KEY `option_id` (`option_id`), CONSTRAINT `product_customization_to_option_ibfk_1` FOREIGN KEY (`customization_id`) REFERENCES `product_customization` (`id`) ON DELETE CASCADE ON UPDATE CASCADE, CONSTRAINT `product_customization_to_option_ibfk_2` FOREIGN KEY (`option_id`) REFERENCES `product_option` (`id`) ON DELETE CASCADE ON UPDATE CASCADE ) ENGINE=InnoDB AUTO_INCREMENT=7 DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; /*Data for the table `product_customization_to_option` */ insert into `product_customization_to_option`(`id`,`customization_id`,`option_id`) values (1,1,2),(2,2,1),(3,2,5),(4,1,7),(5,3,4),(6,3,5); /*Table structure for table `product_image` */ DROP TABLE IF EXISTS `product_image`; CREATE TABLE `product_image` ( `id` int(11) NOT NULL AUTO_INCREMENT, `product_id` int(11) NOT NULL, `image` varchar(511) COLLATE utf8_unicode_ci NOT NULL, `image_path` varchar(511) COLLATE utf8_unicode_ci NOT NULL, `color` varchar(127) COLLATE utf8_unicode_ci DEFAULT NULL, `sort_order` int(11) DEFAULT NULL, PRIMARY KEY (`id`), KEY `fk_product_id_idx` (`product_id`), CONSTRAINT `product_image_ibfk_1` FOREIGN KEY (`product_id`) REFERENCES `product` (`id`) ON DELETE CASCADE ON UPDATE CASCADE ) ENGINE=InnoDB AUTO_INCREMENT=15 DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; /*Data for the table `product_image` */ insert into `product_image`(`id`,`product_id`,`image`,`image_path`,`color`,`sort_order`) values (1,26,'xe-day1-5.jpg','/201610/',NULL,NULL),(2,26,'xe-day2-5.jpg','/201610/',NULL,NULL),(3,26,'xe-day3-5.jpg','/201610/',NULL,NULL),(4,26,'xe-day4-5.jpg','/201610/',NULL,NULL),(5,26,'xe-day5-5.jpg','/201610/',NULL,NULL),(6,27,'7_1448943501_XD00073.jpg','/201610/',NULL,NULL),(7,27,'fqi1461238357-2.jpg','/201610/',NULL,NULL),(8,27,'images.jpg','/201610/',NULL,NULL),(9,26,'ARIEL 126 - PINK 05.png','/201610/',NULL,NULL),(10,26,'fqi1461238357-3.jpg','/201610/',NULL,NULL),(11,26,'images-2.jpg','/201610/',NULL,NULL),(12,26,'sanpham1.jpg','/201610/',NULL,NULL),(13,26,'xe-day1-6.jpg','/201610/',NULL,NULL),(14,26,'xe-day2-6.jpg','/201610/',NULL,NULL); /*Table structure for table `product_option` */ DROP TABLE IF EXISTS `product_option`; CREATE TABLE `product_option` ( `id` int(11) NOT NULL AUTO_INCREMENT, `name` varchar(511) COLLATE utf8_unicode_ci NOT NULL, `label` varchar(511) COLLATE utf8_unicode_ci DEFAULT NULL, `group_id` int(11) NOT NULL, `sort_order` int(11) DEFAULT NULL, PRIMARY KEY (`id`), KEY `group_id` (`group_id`), CONSTRAINT `product_option_ibfk_1` FOREIGN KEY (`group_id`) REFERENCES `product_option_group` (`id`) ON DELETE CASCADE ON UPDATE CASCADE ) ENGINE=InnoDB AUTO_INCREMENT=8 DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; /*Data for the table `product_option` */ insert into `product_option`(`id`,`name`,`label`,`group_id`,`sort_order`) values (1,'Xanh','<span style=\"color:blue\">Xanh</span>',1,NULL),(2,'Đỏ','<span style=\"color:red\">Đỏ</span>',1,NULL),(3,'Đen','',1,NULL),(4,'Trắng','',1,NULL),(5,'4kg','',2,NULL),(6,'5kg','',2,NULL),(7,'6kg','',2,NULL); /*Table structure for table `product_option_group` */ DROP TABLE IF EXISTS `product_option_group`; CREATE TABLE `product_option_group` ( `id` int(11) NOT NULL AUTO_INCREMENT, `name` varchar(511) COLLATE utf8_unicode_ci NOT NULL, `label` varchar(511) COLLATE utf8_unicode_ci DEFAULT NULL, `sort_order` int(11) DEFAULT NULL, PRIMARY KEY (`id`) ) ENGINE=InnoDB AUTO_INCREMENT=3 DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; /*Data for the table `product_option_group` */ insert into `product_option_group`(`id`,`name`,`label`,`sort_order`) values (1,'Màu sắc',NULL,NULL),(2,'Khối lượng',NULL,NULL); /*Table structure for table `product_related` */ DROP TABLE IF EXISTS `product_related`; CREATE TABLE `product_related` ( `id` int(11) NOT NULL AUTO_INCREMENT, `product_id` int(11) NOT NULL, `related_id` int(11) NOT NULL, PRIMARY KEY (`id`), KEY `product_id` (`product_id`), KEY `related_id` (`related_id`), CONSTRAINT `product_related_ibfk_1` FOREIGN KEY (`product_id`) REFERENCES `product` (`id`) ON DELETE CASCADE ON UPDATE CASCADE, CONSTRAINT `product_related_ibfk_2` FOREIGN KEY (`related_id`) REFERENCES `product` (`id`) ON DELETE CASCADE ON UPDATE CASCADE ) ENGINE=InnoDB AUTO_INCREMENT=3 DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; /*Data for the table `product_related` */ insert into `product_related`(`id`,`product_id`,`related_id`) values (1,27,26),(2,26,27); /*Table structure for table `product_to_attribute` */ DROP TABLE IF EXISTS `product_to_attribute`; CREATE TABLE `product_to_attribute` ( `id` int(11) NOT NULL AUTO_INCREMENT, `product_id` int(11) NOT NULL, `attribute_id` int(11) NOT NULL, PRIMARY KEY (`id`), KEY `product_id` (`product_id`), KEY `attribute_id` (`attribute_id`), CONSTRAINT `product_to_attribute_ibfk_1` FOREIGN KEY (`product_id`) REFERENCES `product` (`id`) ON DELETE CASCADE ON UPDATE CASCADE, CONSTRAINT `product_to_attribute_ibfk_2` FOREIGN KEY (`attribute_id`) REFERENCES `product_attribute` (`id`) ON DELETE CASCADE ON UPDATE CASCADE ) ENGINE=InnoDB AUTO_INCREMENT=6 DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; /*Data for the table `product_to_attribute` */ insert into `product_to_attribute`(`id`,`product_id`,`attribute_id`) values (1,26,2),(3,26,6),(4,27,2),(5,27,4); /*Table structure for table `product_to_category` */ DROP TABLE IF EXISTS `product_to_category`; CREATE TABLE `product_to_category` ( `id` int(11) NOT NULL AUTO_INCREMENT, `category_id` int(11) NOT NULL, `product_id` int(11) NOT NULL, PRIMARY KEY (`id`), UNIQUE KEY `UNIQUE` (`category_id`,`product_id`), KEY `fk_product_category_id_idx` (`category_id`), KEY `fk2_product_id_idx` (`product_id`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; /*Data for the table `product_to_category` */ /*Table structure for table `product_to_tag` */ DROP TABLE IF EXISTS `product_to_tag`; CREATE TABLE `product_to_tag` ( `id` int(11) NOT NULL AUTO_INCREMENT, `product_id` int(11) NOT NULL, `tag_id` int(11) NOT NULL, PRIMARY KEY (`id`), KEY `product_id` (`product_id`), KEY `product_category_id` (`tag_id`), CONSTRAINT `product_to_tag_ibfk_1` FOREIGN KEY (`product_id`) REFERENCES `product` (`id`) ON DELETE CASCADE ON UPDATE CASCADE, CONSTRAINT `product_to_tag_ibfk_2` FOREIGN KEY (`tag_id`) REFERENCES `tag` (`id`) ON DELETE CASCADE ON UPDATE CASCADE ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; /*Data for the table `product_to_tag` */ /*Table structure for table `product_tracking` */ DROP TABLE IF EXISTS `product_tracking`; CREATE TABLE `product_tracking` ( `id` int(11) NOT NULL AUTO_INCREMENT, `customization_id` int(11) DEFAULT NULL, `product_id` int(11) DEFAULT NULL, `order_quantity` int(11) DEFAULT NULL, `sold_quantity` int(11) DEFAULT NULL, `available_quantity` int(11) DEFAULT NULL, `total_quantity` int(11) DEFAULT NULL, `price` int(11) DEFAULT NULL, `original_price` int(11) DEFAULT NULL, `created_at` int(11) DEFAULT NULL, `created_by` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, PRIMARY KEY (`id`), KEY `customization_id` (`customization_id`), KEY `product_id` (`product_id`), CONSTRAINT `product_tracking_ibfk_1` FOREIGN KEY (`customization_id`) REFERENCES `product_customization` (`id`) ON DELETE CASCADE ON UPDATE CASCADE, CONSTRAINT `product_tracking_ibfk_2` FOREIGN KEY (`product_id`) REFERENCES `product` (`id`) ON DELETE CASCADE ON UPDATE CASCADE ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; /*Data for the table `product_tracking` */ /*Table structure for table `purchase_order` */ DROP TABLE IF EXISTS `purchase_order`; CREATE TABLE `purchase_order` ( `id` int(11) NOT NULL AUTO_INCREMENT, `code` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `status` tinyint(2) NOT NULL, `created_at` int(11) NOT NULL, `customer_id` int(11) DEFAULT NULL, `customer_name` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `customer_email` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `customer_phone_number` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `customer_address` varchar(511) COLLATE utf8_unicode_ci NOT NULL, `customer_address_2` varchar(511) COLLATE utf8_unicode_ci DEFAULT NULL, `customer_city` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `customer_note` varchar(2000) COLLATE utf8_unicode_ci DEFAULT NULL, `user_note` varchar(2000) COLLATE utf8_unicode_ci DEFAULT NULL, `updated_at` int(11) DEFAULT NULL, `updated_by` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `shipping_fee` int(11) DEFAULT NULL, `shipping_duration` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `tax` int(11) DEFAULT NULL, PRIMARY KEY (`id`), UNIQUE KEY `code` (`code`), KEY `customer_id` (`customer_id`), CONSTRAINT `purchase_order_ibfk_1` FOREIGN KEY (`customer_id`) REFERENCES `customer` (`id`) ON DELETE CASCADE ON UPDATE CASCADE ) ENGINE=InnoDB AUTO_INCREMENT=15 DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; /*Data for the table `purchase_order` */ insert into `purchase_order`(`id`,`code`,`status`,`created_at`,`customer_id`,`customer_name`,`customer_email`,`customer_phone_number`,`customer_address`,`customer_address_2`,`customer_city`,`customer_note`,`user_note`,`updated_at`,`updated_by`,`shipping_fee`,`shipping_duration`,`tax`) values (10,'49517723',1,1478000305,NULL,'<NAME>','<EMAIL>','01643694807','Phuc Xuan, Thai Nguyen',NULL,NULL,'',NULL,NULL,NULL,NULL,NULL,NULL),(11,'23803598',1,1478001280,NULL,'<NAME>','<EMAIL>','01643694807','Ha Noi',NULL,NULL,'',NULL,NULL,NULL,NULL,NULL,NULL),(12,'90284704',1,1478002083,NULL,'Ngu<NAME>','<EMAIL>','34434343434','Nguyen Van Nam, Ha Noi',NULL,NULL,'',NULL,NULL,NULL,NULL,NULL,NULL),(13,'53042718',1,1478002183,NULL,'<NAME>','<EMAIL>','01643694807','Thai Nguyen',NULL,NULL,'',NULL,NULL,NULL,NULL,NULL,NULL),(14,'41668158',1,1478002751,NULL,'<NAME>','<EMAIL>','01643694807','Phúc Xuân, Thái Nguyen',NULL,NULL,'',NULL,NULL,NULL,NULL,NULL,NULL); /*Table structure for table `purchase_order_detail` */ DROP TABLE IF EXISTS `purchase_order_detail`; CREATE TABLE `purchase_order_detail` ( `id` int(11) NOT NULL AUTO_INCREMENT, `purchase_order_id` int(11) NOT NULL, `product_customization_id` int(11) DEFAULT NULL, `product_id` int(11) NOT NULL, `purchase_order_code` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `product_code` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `product_customization_name` varchar(511) COLLATE utf8_unicode_ci DEFAULT NULL, `product_name` varchar(511) COLLATE utf8_unicode_ci DEFAULT NULL, `product_description` varchar(511) COLLATE utf8_unicode_ci DEFAULT NULL, `product_color` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `product_style` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `product_size` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `product_weight` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `product_model` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `unit_price` int(11) NOT NULL, `quantity` int(11) NOT NULL, `discount` float DEFAULT NULL, PRIMARY KEY (`id`), KEY `purchase_order_detail_ibfk_1` (`purchase_order_id`), KEY `purchase_order_detail_ibfk_2` (`product_id`), KEY `product_customization_id` (`product_customization_id`), CONSTRAINT `purchase_order_detail_ibfk_1` FOREIGN KEY (`purchase_order_id`) REFERENCES `purchase_order` (`id`) ON DELETE CASCADE ON UPDATE CASCADE, CONSTRAINT `purchase_order_detail_ibfk_2` FOREIGN KEY (`product_id`) REFERENCES `product` (`id`) ON DELETE NO ACTION ON UPDATE NO ACTION, CONSTRAINT `purchase_order_detail_ibfk_3` FOREIGN KEY (`product_customization_id`) REFERENCES `product_customization` (`id`) ON DELETE NO ACTION ON UPDATE NO ACTION ) ENGINE=InnoDB AUTO_INCREMENT=10 DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; /*Data for the table `purchase_order_detail` */ insert into `purchase_order_detail`(`id`,`purchase_order_id`,`product_customization_id`,`product_id`,`purchase_order_code`,`product_code`,`product_customization_name`,`product_name`,`product_description`,`product_color`,`product_style`,`product_size`,`product_weight`,`product_model`,`unit_price`,`quantity`,`discount`) values (1,10,1,26,'49517723','CG445','Màu đỏ','Xe đẩy Combi Granpaseo LZ600','',NULL,NULL,NULL,NULL,NULL,9990000,19,10),(2,10,2,26,'49517723','CG445','Màu xanh','Xe đẩy Combi Granpaseo LZ600','',NULL,NULL,NULL,NULL,NULL,9990000,9,10),(3,11,1,26,'23803598','CG445','Màu đỏ','Xe đẩy Combi Granpaseo LZ600','',NULL,NULL,NULL,NULL,NULL,9990000,1,10),(4,11,3,26,'23803598','CG445','Màu trắng','Xe đẩy Combi Granpaseo LZ600','',NULL,NULL,NULL,NULL,NULL,9990000,1,10),(5,12,1,26,'90284704','CG445','Màu đỏ','Xe đẩy Combi Granpaseo LZ600','',NULL,NULL,NULL,NULL,NULL,9990000,1,10),(6,13,1,26,'53042718','CG445','Màu đỏ','Xe đẩy Combi Granpaseo LZ600','',NULL,NULL,NULL,NULL,NULL,9990000,1,10),(7,14,1,26,'41668158','CG445','Màu đỏ','Xe đẩy Combi Granpaseo LZ600','',NULL,NULL,NULL,NULL,NULL,9990000,8,10),(8,14,2,26,'41668158','CG445','Màu xanh','Xe đẩy Combi Granpaseo LZ600','',NULL,NULL,NULL,NULL,NULL,9990000,10,10),(9,14,3,26,'41668158','CG445','Màu trắng','Xe đẩy Combi Granpaseo LZ600','',NULL,NULL,NULL,NULL,NULL,9990000,1,10); /*Table structure for table `redirect_url` */ DROP TABLE IF EXISTS `redirect_url`; CREATE TABLE `redirect_url` ( `id` int(11) NOT NULL AUTO_INCREMENT, `from_urls` text COLLATE utf8_unicode_ci NOT NULL, `to_url` varchar(511) COLLATE utf8_unicode_ci NOT NULL, `created_by` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `created_at` int(11) NOT NULL, `updated_by` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `updated_at` int(11) DEFAULT NULL, `is_active` tinyint(1) NOT NULL DEFAULT '1', `status` smallint(4) DEFAULT NULL, PRIMARY KEY (`id`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; /*Data for the table `redirect_url` */ /*Table structure for table `seo_info` */ DROP TABLE IF EXISTS `seo_info`; CREATE TABLE `seo_info` ( `id` int(11) NOT NULL AUTO_INCREMENT, `url` varchar(511) COLLATE utf8_unicode_ci NOT NULL DEFAULT '', `type` tinyint(2) DEFAULT NULL, `is_active` tinyint(1) NOT NULL, `meta_title` varchar(511) COLLATE utf8_unicode_ci NOT NULL DEFAULT '', `meta_keywords` varchar(511) COLLATE utf8_unicode_ci NOT NULL DEFAULT '', `meta_description` varchar(511) COLLATE utf8_unicode_ci NOT NULL DEFAULT '', `h1` varchar(511) COLLATE utf8_unicode_ci NOT NULL DEFAULT '', `page_title` varchar(511) COLLATE utf8_unicode_ci NOT NULL DEFAULT '', `long_description` text COLLATE utf8_unicode_ci, `image` varchar(511) COLLATE utf8_unicode_ci DEFAULT '', `image_path` varchar(511) COLLATE utf8_unicode_ci DEFAULT '', `created_at` int(11) NOT NULL, `created_by` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `updated_at` int(11) DEFAULT NULL, `updated_by` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, PRIMARY KEY (`id`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; /*Data for the table `seo_info` */ /*Table structure for table `site_param` */ DROP TABLE IF EXISTS `site_param`; CREATE TABLE `site_param` ( `id` int(11) NOT NULL AUTO_INCREMENT, `name` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `value` varchar(2000) COLLATE utf8_unicode_ci NOT NULL, PRIMARY KEY (`id`) ) ENGINE=InnoDB AUTO_INCREMENT=10 DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; /*Data for the table `site_param` */ insert into `site_param`(`id`,`name`,`value`) values (6,'video_source','https://www.youtube.com/embed/dK06JD9XTwM?feature=player_embedded'),(7,'video_source','https://www.youtube.com/embed/SeVxItw97s0?feature=player_embedded'),(8,'video_source','https://www.youtube.com/embed/07_DDSrgXg4?feature=player_embedded'),(9,'phone_number','(08)3559-4398'); /*Table structure for table `slideshow_item` */ DROP TABLE IF EXISTS `slideshow_item`; CREATE TABLE `slideshow_item` ( `id` int(11) NOT NULL AUTO_INCREMENT, `image` varchar(511) COLLATE utf8_unicode_ci NOT NULL, `image_path` varchar(511) COLLATE utf8_unicode_ci NOT NULL, `link` varchar(511) COLLATE utf8_unicode_ci DEFAULT NULL, `caption` varchar(511) COLLATE utf8_unicode_ci DEFAULT NULL, `sort_order` int(11) DEFAULT NULL, `is_active` tinyint(1) NOT NULL, `created_at` int(11) NOT NULL, `created_by` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `updated_at` int(11) DEFAULT NULL, `updated_by` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `type` tinyint(2) DEFAULT NULL, PRIMARY KEY (`id`) ) ENGINE=InnoDB AUTO_INCREMENT=3 DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; /*Data for the table `slideshow_item` */ insert into `slideshow_item`(`id`,`image`,`image_path`,`link`,`caption`,`sort_order`,`is_active`,`created_at`,`created_by`,`updated_at`,`updated_by`,`type`) values (1,'1.jpg','/201610/','','',NULL,1,1477458153,'quyettv',NULL,NULL,NULL),(2,'2.jpg','/201610/','','',NULL,1,1477458221,'quyettv',1477458243,'quyettv',NULL); /*Table structure for table `store` */ DROP TABLE IF EXISTS `store`; CREATE TABLE `store` ( `id` int(11) NOT NULL AUTO_INCREMENT, `name` varchar(255) CHARACTER SET utf8 COLLATE utf8_unicode_ci NOT NULL, `address` varchar(2000) CHARACTER SET utf8 COLLATE utf8_unicode_ci NOT NULL, `province` varchar(255) CHARACTER SET utf8 COLLATE utf8_unicode_ci DEFAULT NULL, `district` varchar(255) CHARACTER SET utf8 COLLATE utf8_unicode_ci DEFAULT NULL, `hotline` varchar(255) CHARACTER SET utf8 COLLATE utf8_unicode_ci DEFAULT NULL, `email` varchar(255) CHARACTER SET utf8 COLLATE utf8_unicode_ci DEFAULT NULL, `city` varchar(255) CHARACTER SET utf8 COLLATE utf8_unicode_ci DEFAULT NULL, `country` varchar(255) CHARACTER SET utf8 COLLATE utf8_unicode_ci DEFAULT NULL, `sort_order` varchar(255) CHARACTER SET utf8 COLLATE utf8_unicode_ci DEFAULT NULL, PRIMARY KEY (`id`) ) ENGINE=InnoDB AUTO_INCREMENT=62 DEFAULT CHARSET=latin1; /*Data for the table `store` */ insert into `store`(`id`,`name`,`address`,`province`,`district`,`hotline`,`email`,`city`,`country`,`sort_order`) values (52,'27 Quán Thánh - Hà Nội','27 Quán Thánh - Hà Nội','','','','','','',''),(53,'259 Chùa Bộc - Hà Nội','259 Chùa Bộc - Hà Nội','','','','','','',''),(54,'126 Cầu Giấy - Hà Nội','126 Cầu Giấy - Hà Nội','','','','','','',''),(55,'93 Xuân Thủy - Hà Nội','93 Xuân Thủy - Hà Nội','','','','','','',''),(56,'19 Phố Huế - Hà Nội','19 Phố Huế - Hà Nội','','','','','','',''),(57,'32 Trần Hưng Đạo - Hải Dương','32 Trần Hưng Đạo - Hải Dương','','','','','','',''),(58,'52 Mê Linh - Lê Chân - Hải Phòng','52 Mê Linh - Lê Chân - Hải Phòng','','','','','','',''),(59,'Hạ Long - Quảng Ninh (OPENING SOON)','H<NAME> - Quảng Ninh (OPENING SOON)','','','','','','',''),(60,'316 Lê Văn Sỹ- TP.HCM','316 Lê Văn Sỹ- TP.HCM','','','','','','',''),(61,'Viêng Chăn - Lào','Viêng Chăn - Lào','','','','','','',''); /*Table structure for table `tag` */ DROP TABLE IF EXISTS `tag`; CREATE TABLE `tag` ( `id` int(11) NOT NULL AUTO_INCREMENT, `name` varchar(255) COLLATE utf8_unicode_ci NOT NULL DEFAULT '', `label` varchar(255) COLLATE utf8_unicode_ci DEFAULT '', `slug` varchar(255) COLLATE utf8_unicode_ci NOT NULL DEFAULT '', `old_slugs` varchar(2000) COLLATE utf8_unicode_ci DEFAULT '', `page_title` varchar(511) COLLATE utf8_unicode_ci DEFAULT '', `h1` varchar(511) COLLATE utf8_unicode_ci DEFAULT '', `meta_title` varchar(511) COLLATE utf8_unicode_ci DEFAULT '', `meta_description` varchar(511) COLLATE utf8_unicode_ci DEFAULT '', `meta_keywords` varchar(511) COLLATE utf8_unicode_ci DEFAULT '', `description` varchar(511) COLLATE utf8_unicode_ci DEFAULT '', `sort_order` int(11) DEFAULT NULL, `long_description` text COLLATE utf8_unicode_ci, `image` varchar(511) COLLATE utf8_unicode_ci DEFAULT '', `image_path` varchar(511) COLLATE utf8_unicode_ci DEFAULT '', `is_active` tinyint(1) DEFAULT NULL, `is_hot` tinyint(1) DEFAULT NULL, `status` smallint(2) DEFAULT NULL, `created_at` int(11) NOT NULL, `created_by` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `updated_at` int(11) DEFAULT NULL, `updated_by` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `type` tinyint(2) DEFAULT NULL, PRIMARY KEY (`id`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; /*Data for the table `tag` */ /*Table structure for table `user` */ DROP TABLE IF EXISTS `user`; CREATE TABLE `user` ( `id` int(11) NOT NULL AUTO_INCREMENT, `username` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `auth_key` varchar(32) COLLATE utf8_unicode_ci NOT NULL, `password_hash` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `password_reset_token` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `email` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `status` smallint(6) NOT NULL DEFAULT '10', `created_at` int(11) NOT NULL, `updated_at` int(11) NOT NULL, `firstname` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `lastname` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `dob` int(11) DEFAULT NULL, `alias` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `gender` tinyint(1) DEFAULT NULL, `image` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, `image_path` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL, PRIMARY KEY (`id`), UNIQUE KEY `username` (`username`), UNIQUE KEY `email` (`email`), UNIQUE KEY `password_reset_token` (`<PASSWORD>`) ) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; /*Data for the table `user` */ insert into `user`(`id`,`username`,`auth_key`,`password_hash`,`password_reset_token`,`email`,`status`,`created_at`,`updated_at`,`firstname`,`lastname`,`dob`,`alias`,`gender`,`image`,`image_path`) values (1,'quyettv','<KEY>','<KEY>',NULL,'<EMAIL>',10,0,0,NULL,NULL,NULL,'Văn Quyết',NULL,NULL,NULL); /*Table structure for table `user_log` */ DROP TABLE IF EXISTS `user_log`; CREATE TABLE `user_log` ( `id` int(11) NOT NULL AUTO_INCREMENT, `username` varchar(255) COLLATE utf8_unicode_ci NOT NULL DEFAULT '', `action` varchar(255) COLLATE utf8_unicode_ci NOT NULL DEFAULT '', `created_at` int(11) NOT NULL, `is_success` tinyint(1) DEFAULT '0', `object_class` varchar(255) COLLATE utf8_unicode_ci NOT NULL DEFAULT '', `object_pk` int(11) DEFAULT NULL, PRIMARY KEY (`id`), KEY `fk_username` (`username`) ) ENGINE=InnoDB AUTO_INCREMENT=2902 DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci; /*Data for the table `user_log` */ insert into `user_log`(`id`,`username`,`action`,`created_at`,`is_success`,`object_class`,`object_pk`) values (2429,'quyettv','Create',1475515965,1,'SlideshowItem',5),(2430,'quyettv','Create',1475515982,1,'SlideshowItem',6),(2431,'quyettv','Create',1475515998,1,'SlideshowItem',7),(2432,'quyettv','Create',1475544516,1,'ProductCategory',9),(2433,'quyettv','Create',1475544556,1,'ProductCategory',10),(2434,'quyettv','Create',1475544576,1,'ProductCategory',11),(2435,'quyettv','Create',1475544590,1,'ProductCategory',12),(2436,'quyettv','Create',1475544605,1,'ProductCategory',13),(2437,'quyettv','Create',1475544619,1,'ProductCategory',14),(2438,'quyettv','Create',1475544631,1,'ProductCategory',15),(2439,'quyettv','Create',1475544644,1,'ProductCategory',16),(2440,'quyettv','Update',1475606791,1,'ProductCategory',9),(2441,'quyettv','Update',1475609023,1,'ProductCategory',10),(2442,'quyettv','Update',1475609072,1,'ProductCategory',11),(2443,'quyettv','Update',1475609197,1,'ProductCategory',12),(2444,'quyettv','Create',1475688549,1,'Product',10),(2445,'quyettv','Update',1475688563,1,'Product',10),(2446,'quyettv','Create',1475688704,1,'Product',11),(2447,'quyettv','Update',1475688730,1,'Product',11),(2448,'quyettv','Update',1475688768,1,'Product',11),(2449,'quyettv','Create',1475688870,1,'Product',12),(2450,'quyettv','Update',1475689031,1,'Product',12),(2451,'quyettv','Create',1475693341,1,'ProductImage',15),(2452,'quyettv','Create',1475693355,1,'ProductImage',16),(2453,'quyettv','Create',1475693390,1,'ProductImage',17),(2454,'quyettv','Create',1475693423,1,'ProductImage',18),(2455,'quyettv','Create',1475772369,1,'Article',899),(2456,'quyettv','Create',1475772976,1,'ArticleCategory',178),(2457,'quyettv','Update',1475772989,1,'Article',899),(2458,'quyettv','Create',1475773954,1,'Article',900),(2459,'quyettv','Create',1475774117,1,'Article',901),(2460,'quyettv','Create',1475774293,1,'Article',902),(2461,'quyettv','Create',1475920439,1,'Store',52),(2462,'quyettv','Create',1475920467,1,'Store',53),(2463,'quyettv','Create',1475920476,1,'Store',54),(2464,'quyettv','Create',1475920489,1,'Store',55),(2465,'quyettv','Create',1475920497,1,'Store',56),(2466,'quyettv','Create',1475920505,1,'Store',57),(2467,'quyettv','Create',1475920515,1,'Store',58),(2468,'quyettv','Create',1475920524,1,'Store',59),(2469,'quyettv','Create',1475920532,1,'Store',60),(2470,'quyettv','Create',1475920540,1,'Store',61),(2471,'quyettv','Create',1475920768,1,'Info',11),(2472,'quyettv','Update',1475921635,1,'Info',11),(2473,'quyettv','Update',1475921706,1,'Info',11),(2474,'quyettv','Update',1475921731,1,'Info',11),(2475,'quyettv','Create',1475922952,1,'SiteParam',6),(2476,'quyettv','Create',1475922974,1,'SiteParam',7),(2477,'quyettv','Create',1475922993,1,'SiteParam',8),(2478,'quyettv','Create',1476029598,1,'Info',12),(2479,'quyettv','Delete',1476428901,1,'Article',902),(2480,'quyettv','Delete',1476428904,1,'Article',901),(2481,'quyettv','Delete',1476428908,1,'Article',900),(2482,'quyettv','Delete',1476428911,1,'Article',899),(2483,'quyettv','Create',1476428973,1,'ArticleCategory',179),(2484,'quyettv','Delete',1476428994,1,'PurchaseOrder',40),(2485,'quyettv','Delete',1476428996,1,'PurchaseOrder',39),(2486,'quyettv','Delete',1476428999,1,'PurchaseOrder',38),(2487,'quyettv','Delete',1476429001,1,'PurchaseOrder',37),(2488,'quyettv','Delete',1476429007,1,'SlideshowItem',7),(2489,'quyettv','Delete',1476429009,1,'SlideshowItem',6),(2490,'quyettv','Delete',1476429012,1,'SlideshowItem',5),(2491,'quyettv','Create',1476430740,1,'ArticleCategory',180),(2492,'quyettv','Create',1476430873,1,'Article',903),(2493,'quyettv','Update',1476430982,1,'Article',903),(2494,'quyettv','Create',1476431171,1,'Article',904),(2495,'quyettv','Create',1476431299,1,'Article',905),(2496,'quyettv','Update',1476431327,1,'ArticleCategory',178),(2497,'quyettv','Create',1476431466,1,'Article',906),(2498,'quyettv','Create',1476431596,1,'Article',907),(2499,'quyettv','Create',1476431626,1,'ArticleCategory',181),(2500,'quyettv','Update',1476431637,1,'Article',907),(2501,'quyettv','Update',1476431671,1,'Article',907),(2502,'quyettv','Create',1476431899,1,'Article',908),(2503,'quyettv','Create',1476432019,1,'Article',909),(2504,'quyettv','Update',1476432037,1,'Article',909),(2505,'quyettv','Create',1476432056,1,'ArticleCategory',182),(2506,'quyettv','Update',1476432061,1,'ArticleCategory',182),(2507,'quyettv','Update',1476432080,1,'ArticleCategory',180),(2508,'quyettv','Update',1476432088,1,'ArticleCategory',181),(2509,'quyettv','Update',1476432113,1,'Article',909),(2510,'quyettv','Create',1476432318,1,'Article',910),(2511,'quyettv','Create',1476432454,1,'Article',911),(2512,'quyettv','Update',1476432474,1,'Article',911),(2513,'quyettv','Create',1476432667,1,'Article',912),(2514,'quyettv','Create',1476432839,1,'Article',913),(2515,'quyettv','Create',1476433030,1,'Article',914),(2516,'quyettv','Create',1476433147,1,'Article',915),(2517,'quyettv','Create',1476434447,1,'Article',916),(2518,'quyettv','Update',1476802412,1,'Article',903),(2519,'quyettv','Update',1476802467,1,'Article',904),(2520,'quyettv','Update',1476802512,1,'Article',904),(2521,'quyettv','Update',1476802544,1,'Article',905),(2522,'quyettv','Update',1476802572,1,'Article',906),(2523,'quyettv','Update',1476802632,1,'Article',908),(2524,'quyettv','Update',1476802685,1,'Article',910),(2525,'quyettv','Update',1476802732,1,'Article',911),(2526,'quyettv','Update',1476802755,1,'Article',912),(2527,'quyettv','Create',1476803268,1,'Article',917),(2528,'quyettv','Update',1476803535,1,'Article',917),(2529,'quyettv','Create',1476804899,1,'Article',918),(2530,'quyettv','Create',1476805293,1,'Article',919),(2531,'quyettv','Create',1476805321,1,'ArticleCategory',183),(2532,'quyettv','Update',1476805341,1,'ArticleCategory',183),(2533,'quyettv','Update',1476805373,1,'ArticleCategory',183),(2534,'quyettv','Update',1476805385,1,'Article',919),(2535,'quyettv','Create',1476805542,1,'Article',920),(2536,'quyettv','Create',1476805755,1,'Article',921),(2537,'quyettv','Update',1476805777,1,'Article',921),(2538,'quyettv','Update',1476805805,1,'Article',919),(2539,'quyettv','Create',1476806253,1,'Article',922),(2540,'quyettv','Create',1476806401,1,'Article',923),(2541,'quyettv','Update',1476806414,1,'Article',923),(2542,'quyettv','Create',1476806487,1,'Article',924),(2543,'quyettv','Create',1476807732,1,'Article',925),(2544,'quyettv','Create',1476807857,1,'Article',926),(2545,'quyettv','Create',1476808207,1,'Article',927),(2546,'quyettv','Create',1476808406,1,'Article',928),(2547,'quyettv','Update',1476808491,1,'Article',928),(2548,'quyettv','Create',1476808651,1,'Article',929),(2549,'quyettv','Create',1476808775,1,'Article',930),(2550,'quyettv','Update',1476808792,1,'Article',930),(2551,'quyettv','Create',1476808898,1,'Article',931),(2552,'quyettv','Create',1476808990,1,'Article',932),(2553,'quyettv','Create',1476809081,1,'Article',933),(2554,'quyettv','Update',1476809122,1,'Article',933),(2555,'quyettv','Create',1476809203,1,'Article',934),(2556,'quyettv','Create',1476809306,1,'Article',935),(2557,'quyettv','Create',1476809439,1,'Article',936),(2558,'quyettv','Create',1476809577,1,'Article',937),(2559,'quyettv','Create',1476809667,1,'Article',938),(2560,'quyettv','Create',1476809765,1,'Article',939),(2561,'quyettv','Update',1476809827,1,'Article',939),(2562,'quyettv','Update',1476809858,1,'Article',935),(2563,'quyettv','Create',1476809977,1,'Article',940),(2564,'quyettv','Create',1476810094,1,'Article',941),(2565,'quyettv','Create',1477368708,1,'ProductOptionGroup',1),(2566,'quyettv','Create',1477368717,1,'ProductOptionGroup',2),(2567,'quyettv','Create',1477369032,1,'ProductOption',1),(2568,'quyettv','Create',1477369041,1,'ProductOption',2),(2569,'quyettv','Create',1477369055,1,'ProductOption',3),(2570,'quyettv','Create',1477369062,1,'ProductOption',4),(2571,'quyettv','Create',1477369073,1,'ProductOption',5),(2572,'quyettv','Create',1477369084,1,'ProductOption',6),(2573,'quyettv','Create',1477369093,1,'ProductOption',7),(2574,'quyettv','Create',1477379230,0,'Product',NULL),(2575,'quyettv','Create',1477379286,0,'Product',NULL),(2576,'quyettv','Create',1477379339,1,'Product',13),(2577,'quyettv','Update',1477379454,1,'Product',13),(2578,'quyettv','Update',1477379496,1,'Product',13),(2579,'quyettv','Update',1477379593,1,'Product',13),(2580,'quyettv','Update',1477379643,1,'Product',13),(2581,'quyettv','Update',1477379677,1,'Product',13),(2582,'quyettv','Update',1477379836,1,'Product',13),(2583,'quyettv','Update',1477379849,1,'Product',13),(2584,'quyettv','Update',1477379889,1,'Product',13),(2585,'quyettv','Update',1477379900,1,'Product',13),(2586,'quyettv','Update',1477379988,1,'Product',13),(2587,'quyettv','Update',1477379997,1,'Product',13),(2588,'quyettv','Update',1477380015,1,'Product',13),(2589,'quyettv','Update',1477380042,1,'Product',13),(2590,'quyettv','Create',1477380304,1,'Product',14),(2591,'quyettv','Create',1477380520,1,'Product',15),(2592,'quyettv','Create',1477380567,1,'Product',16),(2593,'quyettv','Create',1477380661,0,'Product',NULL),(2594,'quyettv','Create',1477380675,1,'Product',17),(2595,'quyettv','Create',1477380685,0,'Product',NULL),(2596,'quyettv','Create',1477380696,1,'Product',18),(2597,'quyettv','Create',1477380764,0,'Product',NULL),(2598,'quyettv','Create',1477380774,1,'Product',19),(2599,'quyettv','Create',1477380798,1,'Product',20),(2600,'quyettv','Create',1477380817,1,'Product',21),(2601,'quyettv','Create',1477380853,0,'Product',NULL),(2602,'quyettv','Create',1477380865,1,'Product',22),(2603,'quyettv','Create',1477380917,1,'Product',23),(2604,'quyettv','Create',1477380926,0,'Product',NULL),(2605,'quyettv','Create',1477380938,1,'Product',24),(2606,'quyettv','Create',1477380938,1,'ProductImage',19),(2607,'quyettv','Create',1477380939,1,'ProductImage',20),(2608,'quyettv','Create',1477380939,1,'ProductImage',21),(2609,'quyettv','Create',1477381029,1,'Product',25),(2610,'quyettv','Create',1477381030,1,'ProductImage',22),(2611,'quyettv','Create',1477381030,1,'ProductImage',23),(2612,'quyettv','Create',1477381030,1,'ProductImage',24),(2613,'quyettv','Create',1477381069,1,'Product',26),(2614,'quyettv','Create',1477381069,1,'ProductImage',25),(2615,'quyettv','Create',1477381069,1,'ProductImage',26),(2616,'quyettv','Create',1477381069,1,'ProductImage',27),(2617,'quyettv','Update',1477381956,1,'Product',26),(2618,'quyettv','Delete',1477381956,1,'ProductImage',25),(2619,'quyettv','Delete',1477381956,1,'ProductImage',26),(2620,'quyettv','Delete',1477381956,1,'ProductImage',27),(2621,'quyettv','Create',1477381956,1,'ProductImage',28),(2622,'quyettv','Update',1477381975,1,'Product',26),(2623,'quyettv','Delete',1477381975,1,'ProductImage',28),(2624,'quyettv','Create',1477381975,1,'ProductImage',29),(2625,'quyettv','Create',1477381975,1,'ProductImage',30),(2626,'quyettv','Update',1477382053,1,'Product',26),(2627,'quyettv','Delete',1477382053,1,'ProductImage',29),(2628,'quyettv','Delete',1477382053,1,'ProductImage',30),(2629,'quyettv','Create',1477382053,1,'ProductImage',31),(2630,'quyettv','Create',1477382053,1,'ProductImage',32),(2631,'quyettv','Create',1477382053,1,'ProductImage',33),(2632,'quyettv','Update',1477382092,1,'Product',26),(2633,'quyettv','Create',1477382092,1,'ProductImage',34),(2634,'quyettv','Create',1477382093,1,'ProductImage',35),(2635,'quyettv','Create',1477382093,1,'ProductImage',36),(2636,'quyettv','Create',1477382093,1,'ProductImage',37),(2637,'quyettv','Update',1477382158,1,'Product',26),(2638,'quyettv','Create',1477382158,1,'ProductImage',38),(2639,'quyettv','Create',1477382158,1,'ProductImage',39),(2640,'quyettv','Create',1477382159,1,'ProductImage',40),(2641,'quyettv','Update',1477382200,1,'Product',26),(2642,'quyettv','Create',1477382201,1,'ProductImage',41),(2643,'quyettv','Create',1477382201,1,'ProductImage',42),(2644,'quyettv','Create',1477382201,1,'ProductImage',43),(2645,'quyettv','Update',1477382221,1,'Product',26),(2646,'quyettv','Create',1477382221,1,'ProductImage',44),(2647,'quyettv','Create',1477382221,1,'ProductImage',45),(2648,'quyettv','Update',1477382300,1,'Product',26),(2649,'quyettv','Update',1477382348,1,'Product',26),(2650,'quyettv','Create',1477382348,1,'ProductImage',46),(2651,'quyettv','Create',1477382348,1,'ProductImage',47),(2652,'quyettv','Update',1477382362,1,'Product',26),(2653,'quyettv','Create',1477382362,1,'ProductImage',48),(2654,'quyettv','Create',1477382362,1,'ProductImage',49),(2655,'quyettv','Update',1477382383,1,'Product',26),(2656,'quyettv','Create',1477382383,1,'ProductImage',50),(2657,'quyettv','Create',1477382384,1,'ProductImage',51),(2658,'quyettv','Create',1477382384,1,'ProductImage',52),(2659,'quyettv','Update',1477382407,1,'Product',26),(2660,'quyettv','Create',1477382407,1,'ProductImage',53),(2661,'quyettv','Create',1477382408,1,'ProductImage',54),(2662,'quyettv','Update',1477382449,1,'Product',26),(2663,'quyettv','Update',1477382631,1,'Product',26),(2664,'quyettv','Create',1477382631,1,'ProductImage',55),(2665,'quyettv','Create',1477382631,1,'ProductImage',56),(2666,'quyettv','Update',1477382652,1,'Product',26),(2667,'quyettv','Create',1477382652,1,'ProductImage',57),(2668,'quyettv','Create',1477382653,1,'ProductImage',58),(2669,'quyettv','Create',1477382653,1,'ProductImage',59),(2670,'quyettv','Update',1477382719,1,'Product',26),(2671,'quyettv','Update',1477382729,1,'Product',26),(2672,'quyettv','Create',1477382729,1,'ProductImage',60),(2673,'quyettv','Create',1477382729,1,'ProductImage',61),(2674,'quyettv','Update',1477382787,1,'Product',26),(2675,'quyettv','Update',1477382807,1,'Product',26),(2676,'quyettv','Update',1477382838,1,'Product',26),(2677,'quyettv','Create',1477382838,1,'ProductImage',62),(2678,'quyettv','Delete',1477385387,1,'ProductImage',62),(2679,'quyettv','Delete',1477385421,1,'ProductImage',59),(2680,'quyettv','Delete',1477385789,1,'ProductImage',58),(2681,'quyettv','Delete',1477385792,1,'ProductImage',57),(2682,'quyettv','Update',1477386141,1,'Product',26),(2683,'quyettv','Update',1477386181,1,'Product',26),(2684,'quyettv','Update',1477386197,1,'Product',26),(2685,'quyettv','Update',1477386291,1,'Product',26),(2686,'quyettv','Update',1477386301,1,'Product',26),(2687,'quyettv','Update',1477386347,1,'Product',26),(2688,'quyettv','Create',1477386347,1,'ProductImage',63),(2689,'quyettv','Create',1477386348,1,'ProductImage',64),(2690,'quyettv','Create',1477386348,1,'ProductImage',65),(2691,'quyettv','Update',1477386361,1,'Product',26),(2692,'quyettv','Update',1477386620,1,'Product',26),(2693,'quyettv','Update',1477386641,1,'Product',26),(2694,'quyettv','Create',1477386641,1,'ProductImage',66),(2695,'quyettv','Delete',1477386655,1,'ProductImage',63),(2696,'quyettv','Update',1477390111,1,'Article',941),(2697,'quyettv','Update',1477390128,1,'Article',941),(2698,'quyettv','Update',1477390174,1,'Article',941),(2699,'quyettv','Create',1477390174,1,'ArticleRelated',1),(2700,'quyettv','Create',1477390175,1,'ArticleRelated',2),(2701,'quyettv','Update',1477390182,1,'Article',941),(2702,'quyettv','Delete',1477390182,1,'ArticleRelated',2),(2703,'quyettv','Update',1477390508,0,'Product',26),(2704,'quyettv','Update',1477390532,1,'Product',26),(2705,'quyettv','Create',1477390532,1,'ProductRelated',1),(2706,'quyettv','Create',1477390532,1,'ProductRelated',2),(2707,'quyettv','Update',1477390542,1,'Product',26),(2708,'quyettv','Create',1477390542,1,'ProductRelated',3),(2709,'quyettv','Update',1477390553,1,'Product',26),(2710,'quyettv','Create',1477390553,1,'ProductRelated',4),(2711,'quyettv','Delete',1477390553,1,'ProductRelated',1),(2712,'quyettv','Delete',1477390553,1,'ProductRelated',2),(2713,'quyettv','Create',1477390952,1,'ProductCustomization',1),(2714,'quyettv','Update',1477391000,1,'ProductCustomization',1),(2715,'quyettv','Create',1477391000,1,'ProductCustomizationToOption',1),(2716,'quyettv','Create',1477391000,1,'ProductCustomizationToOption',2),(2717,'quyettv','Update',1477391007,1,'ProductCustomization',1),(2718,'quyettv','Delete',1477391007,1,'ProductCustomizationToOption',2),(2719,'quyettv','Update',1477391014,1,'ProductCustomization',1),(2720,'quyettv','Create',1477391014,1,'ProductCustomizationToOption',3),(2721,'quyettv','Create',1477391014,1,'ProductCustomizationToOption',4),(2722,'quyettv','Update',1477391018,1,'ProductCustomization',1),(2723,'quyettv','Delete',1477391018,1,'ProductCustomizationToOption',3),(2724,'quyettv','Create',1477391025,1,'ProductCustomization',2),(2725,'quyettv','Create',1477391062,1,'ProductCustomization',3),(2726,'quyettv','Create',1477391062,1,'ProductCustomizationToOption',5),(2727,'quyettv','Create',1477391063,1,'ProductCustomizationToOption',6),(2728,'quyettv','Update',1477391127,1,'ProductCustomization',3),(2729,'quyettv','Update',1477391698,1,'ProductCustomization',3),(2730,'quyettv','Update',1477391708,1,'ProductCustomization',3),(2731,'quyettv','Update',1477391751,1,'ProductCustomization',3),(2732,'quyettv','Create',1477391752,1,'ProductImage',67),(2733,'quyettv','Create',1477391752,1,'ProductImage',68),(2734,'quyettv','Create',1477391753,1,'ProductImage',69),(2735,'quyettv','Create',1477391753,1,'ProductImage',70),(2736,'quyettv','Delete',1477391760,1,'ProductImage',70),(2737,'quyettv','Update',1477391784,1,'ProductCustomization',1),(2738,'quyettv','Create',1477391784,1,'ProductImage',71),(2739,'quyettv','Create',1477391784,1,'ProductImage',72),(2740,'quyettv','Create',1477391785,1,'ProductImage',73),(2741,'quyettv','Create',1477391785,1,'ProductImage',74),(2742,'quyettv','Create',1477391814,1,'ProductCustomization',4),(2743,'quyettv','Create',1477391814,1,'ProductImage',75),(2744,'quyettv','Create',1477391814,1,'ProductImage',76),(2745,'quyettv','Create',1477391815,1,'ProductImage',77),(2746,'quyettv','Create',1477391815,1,'ProductCustomizationToOption',7),(2747,'quyettv','Create',1477391815,1,'ProductCustomizationToOption',8),(2748,'quyettv','Delete',1477391832,1,'ProductImage',77),(2749,'quyettv','Delete',1477391837,1,'ProductImage',76),(2750,'quyettv','Update',1477391987,1,'ProductCustomization',4),(2751,'quyettv','Create',1477391999,1,'ProductCustomization',5),(2752,'quyettv','Create',1477391999,1,'ProductImage',78),(2753,'quyettv','Create',1477391999,1,'ProductImage',79),(2754,'quyettv','Update',1477392139,1,'ProductCustomization',5),(2755,'quyettv','Create',1477392140,1,'ProductCustomizationToOption',9),(2756,'quyettv','Delete',1477392846,1,'ProductCustomization',4),(2757,'quyettv','Delete',1477392857,1,'ProductCustomization',5),(2758,'quyettv','Delete',1477392859,1,'ProductCustomization',3),(2759,'quyettv','Delete',1477392873,1,'ProductCustomization',2),(2760,'quyettv','Delete',1477392880,1,'ProductCustomization',1),(2761,'quyettv','Delete',1477392926,1,'ProductImage',73),(2762,'quyettv','Delete',1477392928,1,'ProductImage',69),(2763,'quyettv','Delete',1477392930,1,'ProductImage',71),(2764,'quyettv','Delete',1477392932,1,'ProductImage',74),(2765,'quyettv','Delete',1477392934,1,'ProductImage',72),(2766,'quyettv','Delete',1477392935,1,'ProductImage',75),(2767,'quyettv','Delete',1477392937,1,'ProductImage',78),(2768,'quyettv','Delete',1477392939,1,'ProductImage',79),(2769,'quyettv','Create',1477392951,1,'ProductCustomization',6),(2770,'quyettv','Create',1477392951,1,'ProductImage',80),(2771,'quyettv','Create',1477392952,1,'ProductImage',81),(2772,'quyettv','Create',1477392952,1,'ProductImage',82),(2773,'quyettv','Create',1477392953,1,'ProductImage',83),(2774,'quyettv','Create',1477392953,1,'ProductImage',84),(2775,'quyettv','Create',1477392954,1,'ProductCustomizationToOption',10),(2776,'quyettv','Delete',1477392961,1,'ProductCustomization',6),(2777,'quyettv','Create',1477393147,1,'ProductCustomization',7),(2778,'quyettv','Create',1477393147,1,'ProductImage',85),(2779,'quyettv','Create',1477393147,1,'ProductImage',86),(2780,'quyettv','Create',1477393148,1,'ProductImage',87),(2781,'quyettv','Create',1477393148,1,'ProductImage',88),(2782,'quyettv','Create',1477393148,1,'ProductCustomizationToOption',11),(2783,'quyettv','Delete',1477393163,1,'ProductCustomization',7),(2784,'quyettv','Create',1477393184,1,'ProductCustomization',8),(2785,'quyettv','Create',1477393184,1,'ProductImage',89),(2786,'quyettv','Create',1477393185,1,'ProductImage',90),(2787,'quyettv','Create',1477393185,1,'ProductImage',91),(2788,'quyettv','Create',1477393185,1,'ProductCustomizationToOption',12),(2789,'quyettv','Create',1477393194,1,'ProductCustomization',9),(2790,'quyettv','Create',1477393194,1,'ProductImage',92),(2791,'quyettv','Create',1477393194,1,'ProductImage',93),(2792,'quyettv','Create',1477393195,1,'ProductCustomizationToOption',13),(2793,'quyettv','Delete',1477393203,1,'ProductCustomization',8),(2794,'quyettv','Delete',1477393227,1,'Product',26),(2795,'quyettv','Create',1477451080,1,'ProductAttributeGroup',1),(2796,'quyettv','Update',1477451083,1,'ProductAttributeGroup',1),(2797,'quyettv','Create',1477451093,1,'ProductAttributeGroup',2),(2798,'quyettv','Create',1477451122,1,'ProductAttribute',1),(2799,'quyettv','Create',1477451134,1,'ProductAttribute',2),(2800,'quyettv','Create',1477451145,1,'ProductAttribute',3),(2801,'quyettv','Create',1477451155,1,'ProductAttribute',4),(2802,'quyettv','Create',1477451165,1,'ProductAttribute',5),(2803,'quyettv','Create',1477455493,1,'SiteParam',9),(2804,'quyettv','Create',1477458153,1,'SlideshowItem',1),(2805,'quyettv','Create',1477458221,1,'SlideshowItem',2),(2806,'quyettv','Update',1477458235,1,'SlideshowItem',2),(2807,'quyettv','Update',1477458243,1,'SlideshowItem',2),(2808,'quyettv','Delete',1477458299,1,'ProductCategory',16),(2809,'quyettv','Delete',1477458301,1,'ProductCategory',15),(2810,'quyettv','Delete',1477458303,1,'ProductCategory',14),(2811,'quyettv','Delete',1477458305,1,'ProductCategory',13),(2812,'quyettv','Delete',1477458309,1,'ProductCategory',12),(2813,'quyettv','Delete',1477458311,1,'ProductCategory',11),(2814,'quyettv','Delete',1477458312,1,'ProductCategory',10),(2815,'quyettv','Delete',1477458315,1,'ProductCategory',9),(2816,'quyettv','Create',1477464145,1,'ProductCategory',17),(2817,'quyettv','Create',1477464209,1,'ProductCategory',18),(2818,'quyettv','Create',1477464663,1,'ProductCategory',19),(2819,'quyettv','Delete',1477466155,1,'Product',25),(2820,'quyettv','Delete',1477466157,1,'Product',24),(2821,'quyettv','Delete',1477466158,1,'Product',23),(2822,'quyettv','Delete',1477466161,1,'Product',22),(2823,'quyettv','Delete',1477466163,1,'Product',21),(2824,'quyettv','Delete',1477466165,1,'Product',20),(2825,'quyettv','Delete',1477466167,1,'Product',19),(2826,'quyettv','Delete',1477466169,1,'Product',18),(2827,'quyettv','Delete',1477466172,1,'Product',17),(2828,'quyettv','Delete',1477466174,1,'Product',16),(2829,'quyettv','Delete',1477466176,1,'Product',15),(2830,'quyettv','Delete',1477466178,1,'Product',14),(2831,'quyettv','Create',1477466500,1,'Product',26),(2832,'quyettv','Create',1477466501,1,'ProductImage',1),(2833,'quyettv','Create',1477466502,1,'ProductImage',2),(2834,'quyettv','Create',1477466502,1,'ProductImage',3),(2835,'quyettv','Create',1477466503,1,'ProductImage',4),(2836,'quyettv','Create',1477466503,1,'ProductImage',5),(2837,'quyettv','Create',1477466503,1,'ProductToAttribute',1),(2838,'quyettv','Create',1477466503,1,'ProductToAttribute',2),(2839,'quyettv','Create',1477466569,1,'ProductAttribute',6),(2840,'quyettv','Update',1477466582,1,'Product',26),(2841,'quyettv','Create',1477466582,1,'ProductToAttribute',3),(2842,'quyettv','Delete',1477466582,1,'ProductToAttribute',2),(2843,'quyettv','Create',1477477345,1,'Product',27),(2844,'quyettv','Create',1477477347,1,'ProductImage',6),(2845,'quyettv','Create',1477477347,1,'ProductImage',7),(2846,'quyettv','Create',1477477347,1,'ProductImage',8),(2847,'quyettv','Create',1477477348,1,'ProductToAttribute',4),(2848,'quyettv','Update',1477477356,1,'Product',27),(2849,'quyettv','Create',1477477356,1,'ProductRelated',1),(2850,'quyettv','Update',1477477370,1,'Product',27),(2851,'quyettv','Update',1477477381,1,'Product',27),(2852,'quyettv','Update',1477483408,1,'Product',26),(2853,'quyettv','Update',1477483419,1,'Product',26),(2854,'quyettv','Create',1477483419,1,'ProductRelated',2),(2855,'quyettv','Create',1477483532,1,'ProductCustomization',1),(2856,'quyettv','Create',1477483533,1,'ProductImage',9),(2857,'quyettv','Create',1477483533,1,'ProductImage',10),(2858,'quyettv','Create',1477483534,1,'ProductImage',11),(2859,'quyettv','Create',1477483534,1,'ProductCustomizationToOption',1),(2860,'quyettv','Create',1477483563,1,'ProductCustomization',2),(2861,'quyettv','Create',1477483564,1,'ProductImage',12),(2862,'quyettv','Create',1477483564,1,'ProductImage',13),(2863,'quyettv','Create',1477483565,1,'ProductImage',14),(2864,'quyettv','Create',1477483565,1,'ProductCustomizationToOption',2),(2865,'quyettv','Update',1477484235,1,'ProductAttribute',6),(2866,'quyettv','Update',1477536243,1,'ProductCustomization',2),(2867,'quyettv','Create',1477536244,1,'ProductCustomizationToImage',1),(2868,'quyettv','Create',1477536244,1,'ProductCustomizationToImage',2),(2869,'quyettv','Update',1477539543,1,'ProductCustomization',2),(2870,'quyettv','Create',1477539543,1,'ProductCustomizationToImage',3),(2871,'quyettv','Update',1477539559,1,'ProductCustomization',2),(2872,'quyettv','Create',1477539559,1,'ProductCustomizationToImage',4),(2873,'quyettv','Create',1477539559,1,'ProductCustomizationToImage',5),(2874,'quyettv','Delete',1477539559,1,'ProductCustomizationToImage',2),(2875,'quyettv','Delete',1477539560,1,'ProductCustomizationToImage',3),(2876,'quyettv','Update',1477539575,1,'ProductCustomization',1),(2877,'quyettv','Create',1477539575,1,'ProductCustomizationToImage',6),(2878,'quyettv','Create',1477539575,1,'ProductCustomizationToImage',7),(2879,'quyettv','Create',1477539575,1,'ProductCustomizationToImage',8),(2880,'quyettv','Update',1477541926,1,'ProductCustomization',2),(2881,'quyettv','Create',1477541926,1,'ProductCustomizationToOption',3),(2882,'quyettv','Update',1477541933,1,'ProductCustomization',1),(2883,'quyettv','Create',1477541933,1,'ProductCustomizationToOption',4),(2884,'quyettv','Update',1477542913,1,'ProductOption',1),(2885,'quyettv','Update',1477542924,1,'ProductOption',1),(2886,'quyettv','Update',1477542942,1,'ProductOption',2),(2887,'quyettv','Update',1477543560,1,'ProductCustomization',2),(2888,'quyettv','Update',1477543617,1,'ProductCustomization',1),(2889,'quyettv','Update',1477543650,1,'ProductCustomization',2),(2890,'quyettv','Update',1477543912,1,'ProductCustomization',2),(2891,'quyettv','Update',1477543919,1,'ProductCustomization',1),(2892,'quyettv','Create',1477566442,1,'ProductCustomization',3),(2893,'quyettv','Create',1477566442,1,'ProductCustomizationToOption',5),(2894,'quyettv','Create',1477566442,1,'ProductCustomizationToOption',6),(2895,'quyettv','Create',1477566443,1,'ProductCustomizationToImage',9),(2896,'quyettv','Create',1477566443,1,'ProductCustomizationToImage',10),(2897,'quyettv','Update',1477570544,1,'ProductCustomization',2),(2898,'quyettv','Update',1477571525,1,'ProductCustomization',2),(2899,'quyettv','Update',1477571602,1,'ProductCustomization',1),(2900,'quyettv','Update',1477916394,1,'Product',27),(2901,'quyettv','Create',1477916394,1,'ProductToAttribute',5); /*!40101 SET SQL_MODE=@OLD_SQL_MODE */; /*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */; /*!40014 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS */; /*!40111 SET SQL_NOTES=@OLD_SQL_NOTES */;

DROP FUNCTION IF EXISTS pg_catalog.network_larger(inet, inet) CASCADE; SET LOCAL inplace_upgrade_next_system_object_oids = IUO_PROC, 6666; CREATE FUNCTION pg_catalog.network_larger ( inet, inet ) RETURNS inet LANGUAGE INTERNAL STRICT as 'network_larger'; DROP FUNCTION IF EXISTS pg_catalog.network_smaller(inet, inet) CASCADE; SET LOCAL inplace_upgrade_next_system_object_oids = IUO_PROC, 6667; CREATE FUNCTION pg_catalog.network_smaller ( inet, inet ) RETURNS inet LANGUAGE INTERNAL STRICT as 'network_smaller'; DROP aggregate IF EXISTS pg_catalog.max(inet) CASCADE; SET LOCAL inplace_upgrade_next_system_object_oids = IUO_PROC, 6668; create aggregate max(inet) ( sfunc = network_larger, stype = inet ); DROP aggregate IF EXISTS pg_catalog.min(inet) CASCADE; SET LOCAL inplace_upgrade_next_system_object_oids = IUO_PROC, 6669; create aggregate min(inet) ( sfunc = network_smaller, stype = inet );

SELECT FirstName+'.'+LastName+'@<EMAIL>' AS FullEmailAdress FROM Employees

-- Create Tables CREATE TABLE EMPLOYEE ( PRIMARY KEY (ID) , ID BIGINT NOT NULL GENERATED ALWAYS AS IDENTITY (START WITH 1, INCREMENT BY 1), NAME VARCHAR(50) NOT NULL, DATE_OF_BIRTH DATE NOT NULL, SURNAME VARCHAR(50), PERCENT_CUSTOMER DOUBLE, PERCENT_DATE TIMESTAMP ); CREATE TABLE CUSTOMER ( PRIMARY KEY (ID) , ID BIGINT NOT NULL GENERATED ALWAYS AS IDENTITY (START WITH 1, INCREMENT BY 1), NAME VARCHAR(50) NOT NULL, EMPLOYEE_ID BIGINT NOT NULL, SURNAME VARCHAR(50), PERCENT_PRODUCT DOUBLE, PERCENT_DATE TIMESTAMP, FOREIGN KEY (EMPLOYEE_ID) REFERENCES EMPLOYEE (ID) ); CREATE TABLE PRODUCT ( PRIMARY KEY (ID), ID BIGINT NOT NULL GENERATED ALWAYS AS IDENTITY (START WITH 1, INCREMENT BY 1), NAME VARCHAR(50) NOT NULL, DESCRIPTION VARCHAR(500) ); CREATE TABLE PRODUCT_CUSTOMER ( PRIMARY KEY (PRODUCT_ID, CUSTOMER_ID), PRODUCT_ID BIGINT NOT NULL, CUSTOMER_ID BIGINT NOT NULL, CREATION_DATE TIMESTAMP NOT NULL, FOREIGN KEY (CUSTOMER_ID) REFERENCES CUSTOMER (ID), FOREIGN KEY (PRODUCT_ID) REFERENCES PRODUCT (ID) );

-- phpMyAdmin SQL Dump -- version 5.0.1 -- https://www.phpmyadmin.net/ -- -- Host: 127.0.0.1 -- Waktu pembuatan: 13 Mar 2021 pada 13.49 -- Versi server: 10.4.11-MariaDB -- Versi PHP: 7.4.3 SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO"; SET AUTOCOMMIT = 0; START TRANSACTION; SET time_zone = "+00:00"; /*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */; /*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */; /*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */; /*!40101 SET NAMES utf8mb4 */; -- -- Database: `db_inventaris` -- -- -------------------------------------------------------- -- -- Struktur dari tabel `tb_user` -- CREATE TABLE `tb_user` ( `id_user` int(15) NOT NULL, `npm` varchar(12) NOT NULL, `username` varchar(25) NOT NULL, `password` varchar(25) NOT NULL, `akses` varchar(15) NOT NULL, `created` datetime NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=latin1; -- -- Dumping data untuk tabel `tb_user` -- INSERT INTO `tb_user` (`id_user`, `npm`, `username`, `password`, `akses`, `created`) VALUES (1, '<PASSWORD>', 'admin', '<PASSWORD>', 'admin', '2021-03-07 05:23:16'); -- -- Indexes for dumped tables -- -- -- Indeks untuk tabel `tb_user` -- ALTER TABLE `tb_user` ADD PRIMARY KEY (`id_user`); -- -- AUTO_INCREMENT untuk tabel yang dibuang -- -- -- AUTO_INCREMENT untuk tabel `tb_user` -- ALTER TABLE `tb_user` MODIFY `id_user` int(15) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2; COMMIT; /*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */; /*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */; /*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;

<filename>rust/rocket/mysql/init/1_init.sql CREATE DATABASE holiday_bot; CREATE USER 'rocket'@'%' IDENTIFIED BY 'password'; GRANT ALL PRIVILEGES ON holiday_bot.* TO rocket; -- FLUSH PRIVILEGES;

-- -------------------------------------------------------- -- -- Table structure for table `g5_auth` -- DROP TABLE IF EXISTS `g5_auth`; CREATE TABLE IF NOT EXISTS `g5_auth` ( `mb_id` varchar(20) NOT NULL default '', `au_menu` varchar(20) NOT NULL default '', `au_auth` set('r','w','d') NOT NULL default '', PRIMARY KEY (`mb_id`,`au_menu`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8; -- -------------------------------------------------------- -- -- Table structure for table `g5_board` -- DROP TABLE IF EXISTS `g5_board`; CREATE TABLE IF NOT EXISTS `g5_board` ( `bo_table` varchar(20) NOT NULL DEFAULT '', `gr_id` varchar(255) NOT NULL DEFAULT '', `bo_subject` varchar(255) NOT NULL DEFAULT '', `bo_mobile_subject` varchar(255) NOT NULL DEFAULT '', `bo_device` enum('both','pc','mobile') NOT NULL DEFAULT 'both', `bo_admin` varchar(255) NOT NULL DEFAULT '', `bo_list_level` tinyint(4) NOT NULL DEFAULT '0', `bo_read_level` tinyint(4) NOT NULL DEFAULT '0', `bo_write_level` tinyint(4) NOT NULL DEFAULT '0', `bo_reply_level` tinyint(4) NOT NULL DEFAULT '0', `bo_comment_level` tinyint(4) NOT NULL DEFAULT '0', `bo_upload_level` tinyint(4) NOT NULL DEFAULT '0', `bo_download_level` tinyint(4) NOT NULL DEFAULT '0', `bo_html_level` tinyint(4) NOT NULL DEFAULT '0', `bo_link_level` tinyint(4) NOT NULL DEFAULT '0', `bo_count_delete` tinyint(4) NOT NULL DEFAULT '0', `bo_count_modify` tinyint(4) NOT NULL DEFAULT '0', `bo_read_point` int(11) NOT NULL DEFAULT '0', `bo_write_point` int(11) NOT NULL DEFAULT '0', `bo_comment_point` int(11) NOT NULL DEFAULT '0', `bo_download_point` int(11) NOT NULL DEFAULT '0', `bo_use_category` tinyint(4) NOT NULL DEFAULT '0', `bo_category_list` text NOT NULL, `bo_use_sideview` tinyint(4) NOT NULL DEFAULT '0', `bo_use_file_content` tinyint(4) NOT NULL DEFAULT '0', `bo_use_secret` tinyint(4) NOT NULL DEFAULT '0', `bo_use_dhtml_editor` tinyint(4) NOT NULL DEFAULT '0', `bo_use_rss_view` tinyint(4) NOT NULL DEFAULT '0', `bo_use_good` tinyint(4) NOT NULL DEFAULT '0', `bo_use_nogood` tinyint(4) NOT NULL DEFAULT '0', `bo_use_name` tinyint(4) NOT NULL DEFAULT '0', `bo_use_signature` tinyint(4) NOT NULL DEFAULT '0', `bo_use_ip_view` tinyint(4) NOT NULL DEFAULT '0', `bo_use_list_view` tinyint(4) NOT NULL DEFAULT '0', `bo_use_list_file` tinyint(4) NOT NULL DEFAULT '0', `bo_use_list_content` tinyint(4) NOT NULL DEFAULT '0', `bo_table_width` int(11) NOT NULL DEFAULT '0', `bo_subject_len` int(11) NOT NULL DEFAULT '0', `bo_mobile_subject_len` int(11) NOT NULL DEFAULT '0', `bo_page_rows` int(11) NOT NULL DEFAULT '0', `bo_mobile_page_rows` int(11) NOT NULL DEFAULT '0', `bo_new` int(11) NOT NULL DEFAULT '0', `bo_hot` int(11) NOT NULL DEFAULT '0', `bo_image_width` int(11) NOT NULL DEFAULT '0', `bo_skin` varchar(255) NOT NULL DEFAULT '', `bo_mobile_skin` varchar(255) NOT NULL DEFAULT '', `bo_include_head` varchar(255) NOT NULL DEFAULT '', `bo_include_tail` varchar(255) NOT NULL DEFAULT '', `bo_content_head` text NOT NULL, `bo_mobile_content_head` text NOT NULL, `bo_content_tail` text NOT NULL, `bo_mobile_content_tail` text NOT NULL, `bo_insert_content` text NOT NULL, `bo_gallery_cols` int(11) NOT NULL DEFAULT '0', `bo_gallery_width` int(11) NOT NULL DEFAULT '0', `bo_gallery_height` int(11) NOT NULL DEFAULT '0', `bo_mobile_gallery_width` int(11) NOT NULL DEFAULT '0', `bo_mobile_gallery_height` int(11) NOT NULL DEFAULT '0', `bo_upload_size` int(11) NOT NULL DEFAULT '0', `bo_reply_order` tinyint(4) NOT NULL DEFAULT '0', `bo_use_search` tinyint(4) NOT NULL DEFAULT '0', `bo_order` int(11) NOT NULL DEFAULT '0', `bo_count_write` int(11) NOT NULL DEFAULT '0', `bo_count_comment` int(11) NOT NULL DEFAULT '0', `bo_write_min` int(11) NOT NULL DEFAULT '0', `bo_write_max` int(11) NOT NULL DEFAULT '0', `bo_comment_min` int(11) NOT NULL DEFAULT '0', `bo_comment_max` int(11) NOT NULL DEFAULT '0', `bo_notice` text NOT NULL, `bo_upload_count` tinyint(4) NOT NULL DEFAULT '0', `bo_use_email` tinyint(4) NOT NULL DEFAULT '0', `bo_use_cert` enum('','cert','adult','hp-cert','hp-adult') NOT NULL DEFAULT '', `bo_use_sns` tinyint(4) NOT NULL DEFAULT '0', `bo_sort_field` varchar(255) NOT NULL DEFAULT '', `bo_1_subj` varchar(255) NOT NULL DEFAULT '', `bo_2_subj` varchar(255) NOT NULL DEFAULT '', `bo_3_subj` varchar(255) NOT NULL DEFAULT '', `bo_4_subj` varchar(255) NOT NULL DEFAULT '', `bo_5_subj` varchar(255) NOT NULL DEFAULT '', `bo_6_subj` varchar(255) NOT NULL DEFAULT '', `bo_7_subj` varchar(255) NOT NULL DEFAULT '', `bo_8_subj` varchar(255) NOT NULL DEFAULT '', `bo_9_subj` varchar(255) NOT NULL DEFAULT '', `bo_10_subj` varchar(255) NOT NULL DEFAULT '', `bo_1` varchar(255) NOT NULL DEFAULT '', `bo_2` varchar(255) NOT NULL DEFAULT '', `bo_3` varchar(255) NOT NULL DEFAULT '', `bo_4` varchar(255) NOT NULL DEFAULT '', `bo_5` varchar(255) NOT NULL DEFAULT '', `bo_6` varchar(255) NOT NULL DEFAULT '', `bo_7` varchar(255) NOT NULL DEFAULT '', `bo_8` varchar(255) NOT NULL DEFAULT '', `bo_9` varchar(255) NOT NULL DEFAULT '', `bo_10` varchar(255) NOT NULL DEFAULT '', PRIMARY KEY (`bo_table`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8; -- -------------------------------------------------------- -- -- Table structure for table `g5_board_file` -- DROP TABLE IF EXISTS `g5_board_file`; CREATE TABLE IF NOT EXISTS `g5_board_file` ( `bo_table` varchar(20) NOT NULL default '', `wr_id` int(11) NOT NULL default '0', `bf_no` int(11) NOT NULL default '0', `bf_source` varchar(255) NOT NULL default '', `bf_file` varchar(255) NOT NULL default '', `bf_download` int(11) NOT NULL, `bf_content` text NOT NULL, `bf_filesize` int(11) NOT NULL default '0', `bf_width` int(11) NOT NULL default '0', `bf_height` smallint(6) NOT NULL default '0', `bf_type` tinyint(4) NOT NULL default '0', `bf_datetime` datetime NOT NULL default '0000-00-00 00:00:00', PRIMARY KEY (`bo_table`,`wr_id`,`bf_no`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8; -- -------------------------------------------------------- -- -- Table structure for table `g5_board_good` -- DROP TABLE IF EXISTS `g5_board_good`; CREATE TABLE IF NOT EXISTS `g5_board_good` ( `bg_id` int(11) NOT NULL auto_increment, `bo_table` varchar(20) NOT NULL default '', `wr_id` int(11) NOT NULL default '0', `mb_id` varchar(20) NOT NULL default '', `bg_flag` varchar(255) NOT NULL default '', `bg_datetime` datetime NOT NULL default '0000-00-00 00:00:00', PRIMARY KEY (`bg_id`), UNIQUE KEY `fkey1` (`bo_table`,`wr_id`,`mb_id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8; -- -------------------------------------------------------- -- -- Table structure for table `g5_board_new` -- DROP TABLE IF EXISTS `g5_board_new`; CREATE TABLE IF NOT EXISTS `g5_board_new` ( `bn_id` int(11) NOT NULL auto_increment, `bo_table` varchar(20) NOT NULL default '', `wr_id` int(11) NOT NULL default '0', `wr_parent` int(11) NOT NULL default '0', `bn_datetime` datetime NOT NULL default '0000-00-00 00:00:00', `mb_id` varchar(20) NOT NULL default '', PRIMARY KEY (`bn_id`), KEY `mb_id` (`mb_id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8; -- -------------------------------------------------------- -- -- Table structure for table `g5_config` -- DROP TABLE IF EXISTS `g5_config`; CREATE TABLE IF NOT EXISTS `g5_config` ( `cf_title` varchar(255) NOT NULL DEFAULT '', `cf_theme` varchar(255) NOT NULL DEFAULT '', `cf_admin` varchar(255) NOT NULL DEFAULT '', `cf_admin_email` varchar(255) NOT NULL DEFAULT '', `cf_admin_email_name` varchar(255) NOT NULL DEFAULT '', `cf_add_script` text NOT NULL, `cf_use_point` tinyint(4) NOT NULL DEFAULT '0', `cf_point_term` int(11) NOT NULL DEFAULT '0', `cf_use_copy_log` tinyint(4) NOT NULL DEFAULT '0', `cf_use_email_certify` tinyint(4) NOT NULL DEFAULT '0', `cf_login_point` int(11) NOT NULL DEFAULT '0', `cf_cut_name` tinyint(4) NOT NULL DEFAULT '0', `cf_nick_modify` int(11) NOT NULL DEFAULT '0', `cf_new_skin` varchar(255) NOT NULL DEFAULT '', `cf_new_rows` int(11) NOT NULL DEFAULT '0', `cf_search_skin` varchar(255) NOT NULL DEFAULT '', `cf_connect_skin` varchar(255) NOT NULL DEFAULT '', `cf_faq_skin` varchar(255) NOT NULL DEFAULT '', `cf_read_point` int(11) NOT NULL DEFAULT '0', `cf_write_point` int(11) NOT NULL DEFAULT '0', `cf_comment_point` int(11) NOT NULL DEFAULT '0', `cf_download_point` int(11) NOT NULL DEFAULT '0', `cf_write_pages` int(11) NOT NULL DEFAULT '0', `cf_mobile_pages` int(11) NOT NULL DEFAULT '0', `cf_link_target` varchar(255) NOT NULL DEFAULT '', `cf_delay_sec` int(11) NOT NULL DEFAULT '0', `cf_filter` text NOT NULL, `cf_possible_ip` text NOT NULL, `cf_intercept_ip` text NOT NULL, `cf_analytics` text NOT NULL, `cf_add_meta` text NOT NULL, `cf_member_skin` varchar(255) NOT NULL DEFAULT '', `cf_use_homepage` tinyint(4) NOT NULL DEFAULT '0', `cf_req_homepage` tinyint(4) NOT NULL DEFAULT '0', `cf_use_tel` tinyint(4) NOT NULL DEFAULT '0', `cf_req_tel` tinyint(4) NOT NULL DEFAULT '0', `cf_use_hp` tinyint(4) NOT NULL DEFAULT '0', `cf_req_hp` tinyint(4) NOT NULL DEFAULT '0', `cf_use_addr` tinyint(4) NOT NULL DEFAULT '0', `cf_req_addr` tinyint(4) NOT NULL DEFAULT '0', `cf_use_signature` tinyint(4) NOT NULL DEFAULT '0', `cf_req_signature` tinyint(4) NOT NULL DEFAULT '0', `cf_use_profile` tinyint(4) NOT NULL DEFAULT '0', `cf_req_profile` tinyint(4) NOT NULL DEFAULT '0', `cf_register_level` tinyint(4) NOT NULL DEFAULT '0', `cf_register_point` int(11) NOT NULL DEFAULT '0', `cf_icon_level` tinyint(4) NOT NULL DEFAULT '0', `cf_use_recommend` tinyint(4) NOT NULL DEFAULT '0', `cf_recommend_point` int(11) NOT NULL DEFAULT '0', `cf_leave_day` int(11) NOT NULL DEFAULT '0', `cf_search_part` int(11) NOT NULL DEFAULT '0', `cf_email_use` tinyint(4) NOT NULL DEFAULT '0', `cf_email_wr_super_admin` tinyint(4) NOT NULL DEFAULT '0', `cf_email_wr_group_admin` tinyint(4) NOT NULL DEFAULT '0', `cf_email_wr_board_admin` tinyint(4) NOT NULL DEFAULT '0', `cf_email_wr_write` tinyint(4) NOT NULL DEFAULT '0', `cf_email_wr_comment_all` tinyint(4) NOT NULL DEFAULT '0', `cf_email_mb_super_admin` tinyint(4) NOT NULL DEFAULT '0', `cf_email_mb_member` tinyint(4) NOT NULL DEFAULT '0', `cf_email_po_super_admin` tinyint(4) NOT NULL DEFAULT '0', `cf_prohibit_id` text NOT NULL, `cf_prohibit_email` text NOT NULL, `cf_new_del` int(11) NOT NULL DEFAULT '0', `cf_memo_del` int(11) NOT NULL DEFAULT '0', `cf_visit_del` int(11) NOT NULL DEFAULT '0', `cf_popular_del` int(11) NOT NULL DEFAULT '0', `cf_optimize_date` date NOT NULL default '0000-00-00', `cf_use_member_icon` tinyint(4) NOT NULL DEFAULT '0', `cf_member_icon_size` int(11) NOT NULL DEFAULT '0', `cf_member_icon_width` int(11) NOT NULL DEFAULT '0', `cf_member_icon_height` int(11) NOT NULL DEFAULT '0', `cf_login_minutes` int(11) NOT NULL DEFAULT '0', `cf_image_extension` varchar(255) NOT NULL DEFAULT '', `cf_flash_extension` varchar(255) NOT NULL DEFAULT '', `cf_movie_extension` varchar(255) NOT NULL DEFAULT '', `cf_formmail_is_member` tinyint(4) NOT NULL DEFAULT '0', `cf_page_rows` int(11) NOT NULL DEFAULT '0', `cf_mobile_page_rows` int(11) NOT NULL DEFAULT '0', `cf_visit` varchar(255) NOT NULL DEFAULT '', `cf_max_po_id` int(11) NOT NULL DEFAULT '0', `cf_stipulation` text NOT NULL, `cf_privacy` text NOT NULL, `cf_open_modify` int(11) NOT NULL DEFAULT '0', `cf_memo_send_point` int(11) NOT NULL DEFAULT '0', `cf_mobile_new_skin` varchar(255) NOT NULL DEFAULT '', `cf_mobile_search_skin` varchar(255) NOT NULL DEFAULT '', `cf_mobile_connect_skin` varchar(255) NOT NULL DEFAULT '', `cf_mobile_faq_skin` varchar(255) NOT NULL DEFAULT '', `cf_mobile_member_skin` varchar(255) NOT NULL DEFAULT '', `cf_captcha_mp3` varchar(255) NOT NULL DEFAULT '', `cf_editor` varchar(255) NOT NULL DEFAULT '', `cf_cert_use` tinyint(4) NOT NULL DEFAULT '0', `cf_cert_ipin` varchar(255) NOT NULL DEFAULT '', `cf_cert_hp` varchar(255) NOT NULL DEFAULT '', `cf_cert_kcb_cd` varchar(255) NOT NULL DEFAULT '', `cf_cert_kcp_cd` varchar(255) NOT NULL DEFAULT '', `cf_lg_mid` varchar(255) NOT NULL DEFAULT '', `cf_lg_mert_key` varchar(255) NOT NULL DEFAULT '', `cf_cert_limit` int(11) NOT NULL DEFAULT '0', `cf_cert_req` tinyint(4) NOT NULL DEFAULT '0', `cf_sms_use` varchar(255) NOT NULL DEFAULT '', `cf_sms_type` varchar(10) NOT NULL DEFAULT '', `cf_icode_id` varchar(255) NOT NULL DEFAULT '', `cf_icode_pw` varchar(255) NOT NULL DEFAULT '', `cf_icode_server_ip` varchar(255) NOT NULL DEFAULT '', `cf_icode_server_port` varchar(255) NOT NULL DEFAULT '', `cf_googl_shorturl_apikey` varchar(255) NOT NULL DEFAULT '', `cf_facebook_appid` varchar(255) NOT NULL, `cf_facebook_secret` varchar(255) NOT NULL, `cf_twitter_key` varchar(255) NOT NULL, `cf_twitter_secret` varchar(255) NOT NULL, `cf_kakao_js_apikey` varchar(255) NOT NULL, `cf_1_subj` varchar(255) NOT NULL DEFAULT '', `cf_2_subj` varchar(255) NOT NULL DEFAULT '', `cf_3_subj` varchar(255) NOT NULL DEFAULT '', `cf_4_subj` varchar(255) NOT NULL DEFAULT '', `cf_5_subj` varchar(255) NOT NULL DEFAULT '', `cf_6_subj` varchar(255) NOT NULL DEFAULT '', `cf_7_subj` varchar(255) NOT NULL DEFAULT '', `cf_8_subj` varchar(255) NOT NULL DEFAULT '', `cf_9_subj` varchar(255) NOT NULL DEFAULT '', `cf_10_subj` varchar(255) NOT NULL DEFAULT '', `cf_1` varchar(255) NOT NULL DEFAULT '', `cf_2` varchar(255) NOT NULL DEFAULT '', `cf_3` varchar(255) NOT NULL DEFAULT '', `cf_4` varchar(255) NOT NULL DEFAULT '', `cf_5` varchar(255) NOT NULL DEFAULT '', `cf_6` varchar(255) NOT NULL DEFAULT '', `cf_7` varchar(255) NOT NULL DEFAULT '', `cf_8` varchar(255) NOT NULL DEFAULT '', `cf_9` varchar(255) NOT NULL DEFAULT '', `cf_10` varchar(255) NOT NULL DEFAULT '' ) ENGINE=MyISAM DEFAULT CHARSET=utf8; -- -------------------------------------------------------- -- -- Table structure for table `g5_cert_history` -- DROP TABLE IF EXISTS `g5_cert_history`; CREATE TABLE IF NOT EXISTS `g5_cert_history` ( `cr_id` int(11) NOT NULL auto_increment, `mb_id` varchar(20) NOT NULL DEFAULT '', `cr_company` varchar(255) NOT NULL DEFAULT '', `cr_method` varchar(255) NOT NULL DEFAULT '', `cr_ip` varchar(255) NOT NULL DEFAULT '', `cr_date` date NOT NULL DEFAULT '0000-00-00', `cr_time` time NOT NULL DEFAULT '00:00:00', PRIMARY KEY (`cr_id`), KEY `mb_id` (`mb_id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8; -- -------------------------------------------------------- -- -- Table structure for table `g5_group` -- DROP TABLE IF EXISTS `g5_group`; CREATE TABLE IF NOT EXISTS `g5_group` ( `gr_id` varchar(10) NOT NULL default '', `gr_subject` varchar(255) NOT NULL default '', `gr_device` ENUM('both','pc','mobile') NOT NULL DEFAULT 'both', `gr_admin` varchar(255) NOT NULL default '', `gr_use_access` tinyint(4) NOT NULL default '0', `gr_order` int(11) NOT NULL default '0', `gr_1_subj` varchar(255) NOT NULL default '', `gr_2_subj` varchar(255) NOT NULL default '', `gr_3_subj` varchar(255) NOT NULL default '', `gr_4_subj` varchar(255) NOT NULL default '', `gr_5_subj` varchar(255) NOT NULL default '', `gr_6_subj` varchar(255) NOT NULL default '', `gr_7_subj` varchar(255) NOT NULL default '', `gr_8_subj` varchar(255) NOT NULL default '', `gr_9_subj` varchar(255) NOT NULL default '', `gr_10_subj` varchar(255) NOT NULL default '', `gr_1` varchar(255) NOT NULL default '', `gr_2` varchar(255) NOT NULL default '', `gr_3` varchar(255) NOT NULL default '', `gr_4` varchar(255) NOT NULL default '', `gr_5` varchar(255) NOT NULL default '', `gr_6` varchar(255) NOT NULL default '', `gr_7` varchar(255) NOT NULL default '', `gr_8` varchar(255) NOT NULL default '', `gr_9` varchar(255) NOT NULL default '', `gr_10` varchar(255) NOT NULL default '', PRIMARY KEY (`gr_id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8; -- -------------------------------------------------------- -- -- Table structure for table `g5_group_member` -- DROP TABLE IF EXISTS `g5_group_member`; CREATE TABLE IF NOT EXISTS `g5_group_member` ( `gm_id` int(11) NOT NULL auto_increment, `gr_id` varchar(255) NOT NULL default '', `mb_id` varchar(20) NOT NULL default '', `gm_datetime` datetime NOT NULL default '0000-00-00 00:00:00', PRIMARY KEY (`gm_id`), KEY `gr_id` (`gr_id`), KEY `mb_id` (`mb_id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8; -- -------------------------------------------------------- -- -- Table structure for table `g5_login` -- DROP TABLE IF EXISTS `g5_login`; CREATE TABLE IF NOT EXISTS `g5_login` ( `lo_ip` varchar(255) NOT NULL default '', `mb_id` varchar(20) NOT NULL default '', `lo_datetime` datetime NOT NULL default '0000-00-00 00:00:00', `lo_location` text NOT NULL, `lo_url` text NOT NULL, PRIMARY KEY (`lo_ip`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8; -- -------------------------------------------------------- -- -- Table structure for table `g5_mail` -- DROP TABLE IF EXISTS `g5_mail`; CREATE TABLE IF NOT EXISTS `g5_mail` ( `ma_id` int(11) NOT NULL auto_increment, `ma_subject` varchar(255) NOT NULL default '', `ma_content` mediumtext NOT NULL, `ma_time` datetime NOT NULL default '0000-00-00 00:00:00', `ma_ip` varchar(255) NOT NULL default '', `ma_last_option` text NOT NULL, PRIMARY KEY (`ma_id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8; -- -------------------------------------------------------- -- -- Table structure for table `g5_member` -- DROP TABLE IF EXISTS `g5_member`; CREATE TABLE IF NOT EXISTS `g5_member` ( `mb_no` int(11) NOT NULL auto_increment, `mb_id` varchar(20) NOT NULL default '', `mb_password` varchar(255) NOT NULL default '', `mb_name` varchar(255) NOT NULL default '', `mb_nick` varchar(255) NOT NULL default '', `mb_nick_date` date NOT NULL default '0000-00-00', `mb_email` varchar(255) NOT NULL default '', `mb_homepage` varchar(255) NOT NULL default '', `mb_level` tinyint(4) NOT NULL default '0', `mb_sex` char(1) NOT NULL default '', `mb_birth` varchar(255) NOT NULL default '', `mb_tel` varchar(255) NOT NULL default '', `mb_hp` varchar(255) NOT NULL default '', `mb_certify` varchar(20) NOT NULL default '', `mb_adult` tinyint(4) NOT NULL default '0', `mb_dupinfo` varchar(255) NOT NULL default '', `mb_zip1` char(3) NOT NULL default '', `mb_zip2` char(3) NOT NULL default '', `mb_addr1` varchar(255) NOT NULL default '', `mb_addr2` varchar(255) NOT NULL default '', `mb_addr3` varchar(255) NOT NULL default '', `mb_addr_jibeon` varchar(255) NOT NULL default '', `mb_signature` text NOT NULL, `mb_recommend` varchar(255) NOT NULL default '', `mb_point` int(11) NOT NULL default '0', `mb_today_login` datetime NOT NULL default '0000-00-00 00:00:00', `mb_login_ip` varchar(255) NOT NULL default '', `mb_datetime` datetime NOT NULL default '0000-00-00 00:00:00', `mb_ip` varchar(255) NOT NULL default '', `mb_leave_date` varchar(8) NOT NULL default '', `mb_intercept_date` varchar(8) NOT NULL default '', `mb_email_certify` datetime NOT NULL default '0000-00-00 00:00:00', `mb_email_certify2` varchar(255) NOT NULL default '', `mb_memo` text NOT NULL, `mb_lost_certify` varchar(255) NOT NULL, `mb_mailling` tinyint(4) NOT NULL default '0', `mb_sms` tinyint(4) NOT NULL default '0', `mb_open` tinyint(4) NOT NULL default '0', `mb_open_date` date NOT NULL default '0000-00-00', `mb_profile` text NOT NULL, `mb_memo_call` varchar(255) NOT NULL default '', `mb_1` varchar(255) NOT NULL default '', `mb_2` varchar(255) NOT NULL default '', `mb_3` varchar(255) NOT NULL default '', `mb_4` varchar(255) NOT NULL default '', `mb_5` varchar(255) NOT NULL default '', `mb_6` varchar(255) NOT NULL default '', `mb_7` varchar(255) NOT NULL default '', `mb_8` varchar(255) NOT NULL default '', `mb_9` varchar(255) NOT NULL default '', `mb_10` varchar(255) NOT NULL default '', PRIMARY KEY (`mb_no`), UNIQUE KEY `mb_id` (`mb_id`), KEY `mb_today_login` (`mb_today_login`), KEY `mb_datetime` (`mb_datetime`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8; -- -------------------------------------------------------- -- -- Table structure for table `g5_memo` -- DROP TABLE IF EXISTS `g5_memo`; CREATE TABLE IF NOT EXISTS `g5_memo` ( `me_id` int(11) NOT NULL default '0', `me_recv_mb_id` varchar(20) NOT NULL default '', `me_send_mb_id` varchar(20) NOT NULL default '', `me_send_datetime` datetime NOT NULL default '0000-00-00 00:00:00', `me_read_datetime` datetime NOT NULL default '0000-00-00 00:00:00', `me_memo` text NOT NULL, PRIMARY KEY (`me_id`), KEY `me_recv_mb_id` (`me_recv_mb_id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8; -- -------------------------------------------------------- -- -- Table structure for table `g5_point` -- DROP TABLE IF EXISTS `g5_point`; CREATE TABLE IF NOT EXISTS `g5_point` ( `po_id` int(11) NOT NULL auto_increment, `mb_id` varchar(20) NOT NULL default '', `po_datetime` datetime NOT NULL default '0000-00-00 00:00:00', `po_content` varchar(255) NOT NULL default '', `po_point` int(11) NOT NULL default '0', `po_use_point` int(11) NOT NULL default '0', `po_expired` tinyint(4) NOT NULL default '0', `po_expire_date` date NOT NULL default '0000-00-00', `po_mb_point` int(11) NOT NULL default '0', `po_rel_table` varchar(20) NOT NULL default '', `po_rel_id` varchar(20) NOT NULL default '', `po_rel_action` varchar(255) NOT NULL default '', PRIMARY KEY (`po_id`), KEY `index1` (`mb_id`,`po_rel_table`,`po_rel_id`,`po_rel_action`), KEY `index2` (`po_expire_date`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8; -- -------------------------------------------------------- -- -- Table structure for table `g5_poll` -- DROP TABLE IF EXISTS `g5_poll`; CREATE TABLE IF NOT EXISTS `g5_poll` ( `po_id` int(11) NOT NULL auto_increment, `po_subject` varchar(255) NOT NULL default '', `po_poll1` varchar(255) NOT NULL default '', `po_poll2` varchar(255) NOT NULL default '', `po_poll3` varchar(255) NOT NULL default '', `po_poll4` varchar(255) NOT NULL default '', `po_poll5` varchar(255) NOT NULL default '', `po_poll6` varchar(255) NOT NULL default '', `po_poll7` varchar(255) NOT NULL default '', `po_poll8` varchar(255) NOT NULL default '', `po_poll9` varchar(255) NOT NULL default '', `po_cnt1` int(11) NOT NULL default '0', `po_cnt2` int(11) NOT NULL default '0', `po_cnt3` int(11) NOT NULL default '0', `po_cnt4` int(11) NOT NULL default '0', `po_cnt5` int(11) NOT NULL default '0', `po_cnt6` int(11) NOT NULL default '0', `po_cnt7` int(11) NOT NULL default '0', `po_cnt8` int(11) NOT NULL default '0', `po_cnt9` int(11) NOT NULL default '0', `po_etc` varchar(255) NOT NULL default '', `po_level` tinyint(4) NOT NULL default '0', `po_point` int(11) NOT NULL default '0', `po_date` date NOT NULL default '0000-00-00', `po_ips` mediumtext NOT NULL, `mb_ids` text NOT NULL, PRIMARY KEY (`po_id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8; -- -------------------------------------------------------- -- -- Table structure for table `g5_poll_etc` -- DROP TABLE IF EXISTS `g5_poll_etc`; CREATE TABLE IF NOT EXISTS `g5_poll_etc` ( `pc_id` int(11) NOT NULL default '0', `po_id` int(11) NOT NULL default '0', `mb_id` varchar(20) NOT NULL default '', `pc_name` varchar(255) NOT NULL default '', `pc_idea` varchar(255) NOT NULL default '', `pc_datetime` datetime NOT NULL default '0000-00-00 00:00:00', PRIMARY KEY (`pc_id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8; -- -------------------------------------------------------- -- -- Table structure for table `g5_popular` -- DROP TABLE IF EXISTS `g5_popular`; CREATE TABLE IF NOT EXISTS `g5_popular` ( `pp_id` int(11) NOT NULL auto_increment, `pp_word` varchar(50) NOT NULL default '', `pp_date` date NOT NULL default '0000-00-00', `pp_ip` varchar(50) NOT NULL default '', PRIMARY KEY (`pp_id`), UNIQUE KEY `index1` (`pp_date`,`pp_word`,`pp_ip`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8; -- -------------------------------------------------------- -- -- Table structure for table `g5_scrap` -- DROP TABLE IF EXISTS `g5_scrap`; CREATE TABLE IF NOT EXISTS `g5_scrap` ( `ms_id` int(11) NOT NULL auto_increment, `mb_id` varchar(20) NOT NULL default '', `bo_table` varchar(20) NOT NULL default '', `wr_id` varchar(15) NOT NULL default '', `ms_datetime` datetime NOT NULL default '0000-00-00 00:00:00', PRIMARY KEY (`ms_id`), KEY `mb_id` (`mb_id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8; -- -------------------------------------------------------- -- -- Table structure for table `g5_visit` -- DROP TABLE IF EXISTS `g5_visit`; CREATE TABLE IF NOT EXISTS `g5_visit` ( `vi_id` int(11) NOT NULL default '0', `vi_ip` varchar(255) NOT NULL default '', `vi_date` date NOT NULL default '0000-00-00', `vi_time` time NOT NULL default '00:00:00', `vi_referer` text NOT NULL, `vi_agent` varchar(255) NOT NULL default '', PRIMARY KEY (`vi_id`), UNIQUE KEY `index1` (`vi_ip`,`vi_date`), KEY `index2` (`vi_date`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8; -- -------------------------------------------------------- -- -- Table structure for table `g5_visit_sum` -- DROP TABLE IF EXISTS `g5_visit_sum`; CREATE TABLE IF NOT EXISTS `g5_visit_sum` ( `vs_date` date NOT NULL default '0000-00-00', `vs_count` int(11) NOT NULL default '0', PRIMARY KEY (`vs_date`), KEY `index1` (`vs_count`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8; -- -------------------------------------------------------- -- -- Table structure for table `g5_unique` -- DROP TABLE IF EXISTS `g5_uniqid`; CREATE TABLE IF NOT EXISTS `g5_uniqid` ( `uq_id` bigint(20) unsigned NOT NULL, `uq_ip` varchar(255) NOT NULL, PRIMARY KEY (`uq_id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8; -- -------------------------------------------------------- -- -- Table structure for table `g5_autosave` -- DROP TABLE IF EXISTS `g5_autosave`; CREATE TABLE IF NOT EXISTS `g5_autosave` ( `as_id` int(11) NOT NULL AUTO_INCREMENT, `mb_id` varchar(20) NOT NULL, `as_uid` bigint(20) unsigned NOT NULL, `as_subject` varchar(255) NOT NULL, `as_content` text NOT NULL, `as_datetime` datetime NOT NULL, PRIMARY KEY (`as_id`), UNIQUE KEY `as_uid` (`as_uid`), KEY `mb_id` (`mb_id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8; -- -------------------------------------------------------- -- -- Table structure for table `g5_qa_config` -- DROP TABLE IF EXISTS `g5_qa_config`; CREATE TABLE IF NOT EXISTS `g5_qa_config` ( `qa_title` varchar(255) NOT NULL DEFAULT'', `qa_category` varchar(255) NOT NULL DEFAULT'', `qa_skin` varchar(255) NOT NULL DEFAULT '', `qa_mobile_skin` varchar(255) NOT NULL DEFAULT '', `qa_use_email` tinyint(4) NOT NULL DEFAULT '0', `qa_req_email` tinyint(4) NOT NULL DEFAULT '0', `qa_use_hp` tinyint(4) NOT NULL DEFAULT '0', `qa_req_hp` tinyint(4) NOT NULL DEFAULT '0', `qa_use_sms` tinyint(4) NOT NULL DEFAULT '0', `qa_send_number` varchar(255) NOT NULL DEFAULT '0', `qa_admin_hp` varchar(255) NOT NULL DEFAULT '', `qa_admin_email` varchar(255) NOT NULL DEFAULT '', `qa_use_editor` tinyint(4) NOT NULL DEFAULT '0', `qa_subject_len` int(11) NOT NULL DEFAULT '0', `qa_mobile_subject_len` int(11) NOT NULL DEFAULT '0', `qa_page_rows` int(11) NOT NULL DEFAULT '0', `qa_mobile_page_rows` int(11) NOT NULL DEFAULT '0', `qa_image_width` int(11) NOT NULL DEFAULT '0', `qa_upload_size` int(11) NOT NULL DEFAULT '0', `qa_insert_content` text NOT NULL, `qa_include_head` varchar(255) NOT NULL DEFAULT '', `qa_include_tail` varchar(255) NOT NULL DEFAULT '', `qa_content_head` text NOT NULL, `qa_content_tail` text NOT NULL, `qa_mobile_content_head` text NOT NULL, `qa_mobile_content_tail` text NOT NULL, `qa_1_subj` varchar(255) NOT NULL DEFAULT '', `qa_2_subj` varchar(255) NOT NULL DEFAULT '', `qa_3_subj` varchar(255) NOT NULL DEFAULT '', `qa_4_subj` varchar(255) NOT NULL DEFAULT '', `qa_5_subj` varchar(255) NOT NULL DEFAULT '', `qa_1` varchar(255) NOT NULL DEFAULT '', `qa_2` varchar(255) NOT NULL DEFAULT '', `qa_3` varchar(255) NOT NULL DEFAULT '', `qa_4` varchar(255) NOT NULL DEFAULT '', `qa_5` varchar(255) NOT NULL DEFAULT '' ) ENGINE=MyISAM DEFAULT CHARSET=utf8; -- -------------------------------------------------------- -- -- Table structure for table `g5_qa_content` -- DROP TABLE IF EXISTS `g5_qa_content`; CREATE TABLE IF NOT EXISTS `g5_qa_content` ( `qa_id` int(11) NOT NULL AUTO_INCREMENT, `qa_num` int(11) NOT NULL DEFAULT '0', `qa_parent` int(11) NOT NULL DEFAULT '0', `qa_related` int(11) NOT NULL DEFAULT '0', `mb_id` varchar(20) NOT NULL DEFAULT '', `qa_name` varchar(255) NOT NULL DEFAULT '', `qa_email` varchar(255) NOT NULL DEFAULT '', `qa_hp` varchar(255) NOT NULL DEFAULT '', `qa_type` tinyint(4) NOT NULL DEFAULT '0', `qa_category` varchar(255) NOT NULL DEFAULT '', `qa_email_recv` tinyint(4) NOT NULL DEFAULT '0', `qa_sms_recv` tinyint(4) NOT NULL DEFAULT '0', `qa_html` tinyint(4) NOT NULL DEFAULT '0', `qa_subject` varchar(255) NOT NULL DEFAULT '', `qa_content` text NOT NULL, `qa_status` tinyint(4) NOT NULL DEFAULT '0', `qa_file1` varchar(255) NOT NULL DEFAULT '', `qa_source1` varchar(255) NOT NULL DEFAULT '', `qa_file2` varchar(255) NOT NULL DEFAULT '', `qa_source2` varchar(255) NOT NULL DEFAULT '', `qa_ip` varchar(255) NOT NULL DEFAULT '', `qa_datetime` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `qa_1` varchar(255) NOT NULL DEFAULT '', `qa_2` varchar(255) NOT NULL DEFAULT '', `qa_3` varchar(255) NOT NULL DEFAULT '', `qa_4` varchar(255) NOT NULL DEFAULT '', `qa_5` varchar(255) NOT NULL DEFAULT '', PRIMARY KEY (`qa_id`), KEY `qa_num_parent` (`qa_num`,`qa_parent`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8; -- -------------------------------------------------------- -- -- Table structure for table `g5_content` -- DROP TABLE IF EXISTS `g5_content`; CREATE TABLE IF NOT EXISTS `g5_content` ( `co_id` varchar(20) NOT NULL DEFAULT '', `co_html` tinyint(4) NOT NULL DEFAULT '0', `co_subject` varchar(255) NOT NULL DEFAULT '', `co_content` longtext NOT NULL, `co_mobile_content` longtext NOT NULL, `co_skin` varchar(255) NOT NULL DEFAULT '', `co_mobile_skin` varchar(255) NOT NULL DEFAULT '', `co_tag_filter_use` tinyint(4) NOT NULL DEFAULT '0', `co_hit` int(11) NOT NULL DEFAULT '0', `co_include_head` varchar(255) NOT NULL, `co_include_tail` varchar(255) NOT NULL, PRIMARY KEY (`co_id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8; -- -------------------------------------------------------- -- -- Table structure for table `g5_faq` -- DROP TABLE IF EXISTS `g5_faq`; CREATE TABLE IF NOT EXISTS `g5_faq` ( `fa_id` int(11) NOT NULL AUTO_INCREMENT, `fm_id` int(11) NOT NULL DEFAULT '0', `fa_subject` text NOT NULL, `fa_content` text NOT NULL, `fa_order` int(11) NOT NULL DEFAULT '0', PRIMARY KEY (`fa_id`), KEY `fm_id` (`fm_id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8; -- -------------------------------------------------------- -- -- Table structure for table `g5_faq_master` -- DROP TABLE IF EXISTS `g5_faq_master`; CREATE TABLE IF NOT EXISTS `g5_faq_master` ( `fm_id` int(11) NOT NULL AUTO_INCREMENT, `fm_subject` varchar(255) NOT NULL DEFAULT '', `fm_head_html` text NOT NULL, `fm_tail_html` text NOT NULL, `fm_mobile_head_html` text NOT NULL, `fm_mobile_tail_html` text NOT NULL, `fm_order` int(11) NOT NULL DEFAULT '0', PRIMARY KEY (`fm_id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8; -- -------------------------------------------------------- -- -- Table structure for table `g5_new_win` -- DROP TABLE IF EXISTS `g5_new_win`; CREATE TABLE IF NOT EXISTS `g5_new_win` ( `nw_id` int(11) NOT NULL AUTO_INCREMENT, `nw_device` varchar(10) NOT NULL DEFAULT 'both', `nw_begin_time` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `nw_end_time` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `nw_disable_hours` int(11) NOT NULL DEFAULT '0', `nw_left` int(11) NOT NULL DEFAULT '0', `nw_top` int(11) NOT NULL DEFAULT '0', `nw_height` int(11) NOT NULL DEFAULT '0', `nw_width` int(11) NOT NULL DEFAULT '0', `nw_subject` text NOT NULL, `nw_content` text NOT NULL, `nw_content_html` tinyint(4) NOT NULL DEFAULT '0', PRIMARY KEY (`nw_id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8; -- -------------------------------------------------------- -- -- Table structure for table `g5_menu` -- DROP TABLE IF EXISTS `g5_menu`; CREATE TABLE IF NOT EXISTS `g5_menu` ( `me_id` int(11) NOT NULL AUTO_INCREMENT, `me_code` varchar(255) NOT NULL DEFAULT '', `me_name` varchar(255) NOT NULL DEFAULT '', `me_link` varchar(255) NOT NULL DEFAULT '', `me_target` varchar(255) NOT NULL DEFAULT '', `me_order` int(11) NOT NULL DEFAULT '0', `me_use` tinyint(4) NOT NULL DEFAULT '0', `me_mobile_use` tinyint(4) NOT NULL DEFAULT '0', PRIMARY KEY (`me_id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8;

-- phpMyAdmin SQL Dump -- version 4.6.6deb5 -- https://www.phpmyadmin.net/ -- -- Host: localhost:3306 -- Generation Time: 21 Mei 2018 pada 22.19 -- Versi Server: 5.7.22-0ubuntu18.04.1 -- PHP Version: 7.0.22-0ubuntu0.17.04.1 SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO"; SET time_zone = "+00:00"; /*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */; /*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */; /*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */; /*!40101 SET NAMES utf8mb4 */; -- -- Database: `jyweb` -- -- -------------------------------------------------------- -- -- Struktur dari tabel `article` -- CREATE TABLE `article` ( `id_article` int(5) NOT NULL, `title` text NOT NULL, `text` text NOT NULL, `images` text NOT NULL, `id_users` int(5) NOT NULL, `timestamp` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ) ENGINE=InnoDB DEFAULT CHARSET=latin1; -- -------------------------------------------------------- -- -- Struktur dari tabel `main_content` -- CREATE TABLE `main_content` ( `id_content` int(5) NOT NULL, `title` text NOT NULL, `text` text NOT NULL, `images` text NOT NULL, `timestamp` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ) ENGINE=InnoDB DEFAULT CHARSET=latin1; -- -- Dumping data untuk tabel `main_content` -- INSERT INTO `main_content` (`id_content`, `title`, `text`, `images`, `timestamp`) VALUES (1, 'Lorem Ipsun Solor Sit Amet', 'Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.', 'favicon.png', '2017-11-04 15:01:10'), (2, 'Lorem Ipsun Solor Sit Amet', 'Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.', 'favicon.png', '2017-11-04 15:01:10'), (3, 'Lorem Ipsun Solor Sit Amet', 'Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.', 'favicon.png', '2017-11-09 13:40:24'); -- -------------------------------------------------------- -- -- Struktur dari tabel `news` -- CREATE TABLE `news` ( `id_news` int(5) NOT NULL, `title` text, `text` text, `image` text, `id_users` int(5) DEFAULT NULL, `slug` text, `created_at` datetime DEFAULT CURRENT_TIMESTAMP, `updated_at` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ) ENGINE=InnoDB DEFAULT CHARSET=latin1; -- -- Dumping data untuk tabel `news` -- INSERT INTO `news` (`id_news`, `title`, `text`, `image`, `id_users`, `slug`, `created_at`, `updated_at`) VALUES (39, 'News', '<p>Description</p>\r\n', 'image_1511623074.png', 1, 'news', '2017-11-25 22:17:54', '2017-11-25 15:19:38'), (40, 'Codeigniter', '<p>This is<em><strong> CodeIgniter.</strong></em></p>\r\n\r\n<p>Features:</p>\r\n\r\n<ul>\r\n <li>Framework with small footprint</li>\r\n <li>TBA</li>\r\n</ul>\r\n\r\n<table border=\"1\" cellpadding=\"1\" cellspacing=\"1\" style=\"width:500px\">\r\n <tbody>\r\n <tr>\r\n <td><strong>ID</strong></td>\r\n <td><strong>USER</strong></td>\r\n </tr>\r\n <tr>\r\n <td>1.</td>\r\n <td>Jayconda</td>\r\n </tr>\r\n <tr>\r\n <td>2.</td>\r\n <td>Jaresh</td>\r\n </tr>\r\n </tbody>\r\n</table>\r\n\r\n<p>&nbsp;</p>\r\n', 'image_1511625030.png', 1, 'codeigniter', '2017-11-25 22:50:30', '2017-11-25 15:50:30'); -- -------------------------------------------------------- -- -- Struktur dari tabel `service` -- CREATE TABLE `service` ( `id_service` int(5) NOT NULL, `service_name` varchar(128) NOT NULL, `service_details` text NOT NULL, `service_image` text NOT NULL, `category` int(5) NOT NULL, `id_user` int(11) NOT NULL, `created_at` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP, `updated_at` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ) ENGINE=InnoDB DEFAULT CHARSET=latin1; -- -------------------------------------------------------- -- -- Struktur dari tabel `users` -- CREATE TABLE `users` ( `id_users` int(5) NOT NULL, `username` varchar(15) NOT NULL, `password` text NOT NULL, `role` int(1) NOT NULL DEFAULT '0', `avatar` varchar(250) DEFAULT NULL, `status` tinyint(1) NOT NULL DEFAULT '1', `created_at` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ) ENGINE=InnoDB DEFAULT CHARSET=latin1; -- -- Dumping data untuk tabel `users` -- INSERT INTO `users` (`id_users`, `username`, `password`, `role`, `avatar`, `status`, `created_at`) VALUES (1, 'admin', '<PASSWORD>', 3, NULL, 0, '2018-02-12 17:42:22'); -- -- Indexes for dumped tables -- -- -- Indexes for table `article` -- ALTER TABLE `article` ADD PRIMARY KEY (`id_article`), ADD KEY `id_users` (`id_users`); -- -- Indexes for table `main_content` -- ALTER TABLE `main_content` ADD PRIMARY KEY (`id_content`); -- -- Indexes for table `news` -- ALTER TABLE `news` ADD PRIMARY KEY (`id_news`), ADD KEY `id_users` (`id_users`); -- -- Indexes for table `service` -- ALTER TABLE `service` ADD PRIMARY KEY (`id_service`); -- -- Indexes for table `users` -- ALTER TABLE `users` ADD PRIMARY KEY (`id_users`); -- -- AUTO_INCREMENT for dumped tables -- -- -- AUTO_INCREMENT for table `article` -- ALTER TABLE `article` MODIFY `id_article` int(5) NOT NULL AUTO_INCREMENT; -- -- AUTO_INCREMENT for table `main_content` -- ALTER TABLE `main_content` MODIFY `id_content` int(5) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=4; -- -- AUTO_INCREMENT for table `news` -- ALTER TABLE `news` MODIFY `id_news` int(5) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=41; -- -- AUTO_INCREMENT for table `service` -- ALTER TABLE `service` MODIFY `id_service` int(5) NOT NULL AUTO_INCREMENT; -- -- AUTO_INCREMENT for table `users` -- ALTER TABLE `users` MODIFY `id_users` int(5) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2; -- -- Ketidakleluasaan untuk tabel pelimpahan (Dumped Tables) -- -- -- Ketidakleluasaan untuk tabel `article` -- ALTER TABLE `article` ADD CONSTRAINT `article_ibfk_1` FOREIGN KEY (`id_users`) REFERENCES `users` (`id_users`); -- -- Ketidakleluasaan untuk tabel `news` -- ALTER TABLE `news` ADD CONSTRAINT `news_ibfk_1` FOREIGN KEY (`id_users`) REFERENCES `users` (`id_users`); /*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */; /*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */; /*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;

<filename>conf/evolutions/default/2.sql # --- !Ups CREATE TABLE `packs` ( `id` INT UNSIGNED NOT NULL AUTO_INCREMENT, `name` VARCHAR(255) NOT NULL, PRIMARY KEY (`id`), UNIQUE INDEX `pack_id_UNIQUE` (`id` ASC), UNIQUE INDEX `pack_name_UNIQUE` (`name` ASC) ); # --- !Downs DROP TABLE `packs`;

<reponame>JR-Stark/iter-quizz<filename>data/create_table.sql -- ----------------------------------------------------- -- Schema oquiz -- ----------------------------------------------------- -- Par convention on va nommer toutes les tables au singulier, en minuscule et en anglais. -- Chaque table contiendra un champs created_at contenant la date de création d'un enregistrement -- Et un champ updated_at contenant la date de mise à jour de cet enregistrement -- Création d'une transaction, c'est un groupe d' instruction SQL -- qui rends celles-ci dépéndantes les unes des autres. -- Si au moins une des instructions génère une erreur, -- alors toutes les commandes sont invalidés BEGIN; -- Comme c'est un script de création de tables ont s'assure que celles-ci -- Soit supprimées avant de les créées. -- On peut supprimer plusieurs tables en même temps DROP TABLE IF EXISTS "level", "answer", "user", "quiz", "question", "tag", "quiz_has_tag"; -- ----------------------------------------------------- -- Table "level" -- ----------------------------------------------------- CREATE TABLE IF NOT EXISTS "level" ( -- une clé primaire est automatiquement NOT NULL. Pas besoin de le préciser. -- -- afin d'utiliser la génération automatique d'un identifiant on utilise une colonne de type serial (Attention désormais on utilisera plutôt GENERATED ALWAYS AS IDENTITY) -- https://wiki.postgresql.org/wiki/Don't_Do_This#Don.27t_use_serial -- Mais dans notre projet on utilise serial car sequelize utilise encore serial… -- -- serial est un pseudo-type c'est a dire qu'en fait lorsque l'on met "serial" -- cela corresponspond en fait à : -- integer NOT NULL DEFAULT nextval('"level_id_seq"'::regclass) -- faisant référence à la sequence nommé level_id_seq, mais tout cela est automatique à la création. -- "id" serial PRIMARY KEY, "name" text NOT NULL ); -- ----------------------------------------------------- -- Table "answer" -- ----------------------------------------------------- -- On ne peut pas référencé le champ id de la table question ici, car la table n'existe pas encore. On fera une modification à la fin du script pour ajouter la référence. CREATE TABLE IF NOT EXISTS "answer" ( "id" serial PRIMARY KEY, "description" text NOT NULL, "question_id" integer NOT NULL ); -- ----------------------------------------------------- -- Table "app_user" -- ----------------------------------------------------- CREATE TABLE IF NOT EXISTS "user" ( "id" serial PRIMARY KEY, "email" text NOT NULL, "password" text NOT NULL, "firstname" text NULL, "lastname" text NULL ); -- ----------------------------------------------------- -- Table "quiz" -- ----------------------------------------------------- CREATE TABLE IF NOT EXISTS "quiz" ( "id" serial PRIMARY KEY, "title" text NOT NULL, "description" text NULL, "user_id" integer NOT NULL REFERENCES "user" ("id") ); -- ----------------------------------------------------- -- Table "question" -- ----------------------------------------------------- CREATE TABLE IF NOT EXISTS "question" ( "id" serial PRIMARY KEY, "question" text NOT NULL, "anecdote" text NULL, "wiki" text NULL, "level_id" integer NOT NULL REFERENCES "level" ("id"), -- 'Good answer', "answer_id" integer NOT NULL REFERENCES "answer" ("id"), "quiz_id" integer NOT NULL REFERENCES "quiz" ("id") ); -- ----------------------------------------------------- -- Table "tag" CREATE TABLE IF NOT EXISTS "tag" ( "id" serial PRIMARY KEY, "name" text NOT NULL ); -- ----------------------------------------------------- -- Table "quiz_has_tag" -- ----------------------------------------------------- CREATE TABLE IF NOT EXISTS "quiz_has_tag" ( "quiz_id" integer REFERENCES "quiz"("id"), "tag_id" integer REFERENCES "tag" ("id"), PRIMARY KEY ("quiz_id", "tag_id") ); -- Maintenant on peut créer la référence vers la table question pour le champ "question_id" dans la table "answer" afin de réprésenter notre clé étrangère. -- On remarquera ici la présence de l'instruction FOREIGN KEY qui dit explicitement que ceette colonne sert de clé étrangère faisaint référence à la colonne question de la table question -- Lors de la création d'une table ce détail est implicite ALTER TABLE "answer" ADD FOREIGN KEY ("question_id") REFERENCES "question" ("id"); -- Pour mettre fin à au bloc de transaction et l'exécuter COMMIT;

IF OBJECT_ID ('dbo.Activity') IS NOT NULL DROP TABLE dbo.Activity GO CREATE TABLE Activity ( ActivityID INT IDENTITY NOT NULL, Title NVARCHAR(500) NOT NULL, Description NVARCHAR(MAX) NULL, StartTime DATETIME NULL, EndTime DATETIME NULL, PriorityID INT NOT NULL,-- DEFAULT (2) ImportanceID INT NOT NULL,-- DEFAULT (2) MaximumAttendees INT NOT NULL, --0 Mains not limited. Place NVARCHAR(500) NOT NULL, OrganizerID INT NOT NULL, PresenterID INT NULL, AllowQueue INT NOT NULL, --DEFAULT (1), 1 mains yes CONSTRAINT PK_Activity PRIMARY KEY (ActivityID ASC), CONSTRAINT FK_Activity_User_Organizer FOREIGN KEY (OrganizerID) REFERENCES [User](UserID), CONSTRAINT FK_Activity_User_Presenter FOREIGN KEY (PresenterID) REFERENCES [User](UserID) ) GO; go; Go; gO; GO go Go gO

<reponame>AldoMyrtaj/duckdb SELECT sum(ws_ext_discount_amt) AS "Excess Discount Amount" FROM web_sales, item, date_dim WHERE i_manufact_id = 350 AND i_item_sk = ws_item_sk AND d_date BETWEEN '2000-01-27' AND cast('2000-04-26' AS date) AND d_date_sk = ws_sold_date_sk AND ws_ext_discount_amt > (SELECT 1.3 * avg(ws_ext_discount_amt) FROM web_sales, date_dim WHERE ws_item_sk = i_item_sk AND d_date BETWEEN '2000-01-27' AND cast('2000-04-26' AS date) AND d_date_sk = ws_sold_date_sk ) ORDER BY sum(ws_ext_discount_amt) LIMIT 100;

<gh_stars>10-100 INSERT INTO houses VALUES (1, 150000, tstzrange('2015-01-01', '2016-01-01')), (1, 200000, tstzrange('2016-01-01', '2017-01-01')), (2, 300000, tstzrange('2015-01-01', '2016-01-01')), (3, 100000, tstzrange('2014-01-01', '2015-01-01')), (3, 200000, tstzrange('2015-01-01', null)), (4, 200000, tstzrange(null, '2014-01-01')) ; SELECT create_temporal_foreign_key('room_has_a_house', 'rooms', 'house_id', 'valid_at', 'houses', 'id', 'valid_at'); -- You can update an fk id to NULL INSERT INTO rooms VALUES (1, 1, tstzrange('2015-01-01', '2015-06-01')); UPDATE rooms SET house_id = NULL; DELETE FROM rooms; -- You can update the range when the fk is NULL INSERT INTO rooms VALUES (1, NULL, tstzrange('2015-01-01', '2015-06-01')); UPDATE rooms SET valid_at = tstzrange('1999-01-01', '2000-01-01'); DELETE FROM rooms; -- You can update a finite fk exactly covered by one row INSERT INTO rooms VALUES (1, 1, tstzrange('2015-01-01', '2015-02-01')); UPDATE rooms SET valid_at = tstzrange('2015-01-01', '2016-01-01'); DELETE FROM rooms; -- You can update a finite fk more than covered by one row INSERT INTO rooms VALUES (1, 1, tstzrange('2015-01-01', '2015-02-01')); UPDATE rooms SET valid_at = tstzrange('2015-01-01', '2015-06-01'); DELETE FROM rooms; -- You can update a finite fk exactly covered by two rows INSERT INTO rooms VALUES (1, 1, tstzrange('2015-01-01', '2015-02-01')); UPDATE rooms SET valid_at = tstzrange('2015-01-01', '2017-01-01'); DELETE FROM rooms; -- You can update a finite fk more than covered by two rows INSERT INTO rooms VALUES (1, 1, tstzrange('2015-01-01', '2015-02-01')); UPDATE rooms SET valid_at = tstzrange('2015-01-01', '2016-06-01'); DELETE FROM rooms; -- You can't update a finite fk id not covered by any row INSERT INTO rooms VALUES (1, 1, tstzrange('2015-01-01', '2015-02-01')); UPDATE rooms SET house_id = 7; DELETE FROM rooms; -- You can't update a finite fk range not covered by any row INSERT INTO rooms VALUES (1, 1, tstzrange('2015-01-01', '2015-02-01')); UPDATE rooms SET valid_at = tstzrange('1999-01-01', '2000-01-01'); DELETE FROM rooms; -- You can't update a finite fk partially covered by one row INSERT INTO rooms VALUES (1, 1, tstzrange('2015-01-01', '2015-02-01')); UPDATE rooms SET valid_at = tstzrange('2014-01-01', '2015-06-01'); DELETE FROM rooms; -- You can't update a finite fk partially covered by two rows INSERT INTO rooms VALUES (1, 1, tstzrange('2015-01-01', '2015-02-01')); UPDATE rooms SET valid_at = tstzrange('2014-01-01', '2016-06-01'); DELETE FROM rooms; -- You can update an infinite fk exactly covered by one row INSERT INTO rooms VALUES (1, 3, tstzrange('2015-01-01', '2015-02-01')); UPDATE rooms SET valid_at = tstzrange('2015-01-01', null); DELETE FROM rooms; -- You can update an infinite fk more than covered by one row INSERT INTO rooms VALUES (1, 3, tstzrange('2015-01-01', '2015-02-01')); UPDATE rooms SET valid_at = tstzrange('2016-01-01', null); DELETE FROM rooms; -- You can update an infinite fk exactly covered by two rows INSERT INTO rooms VALUES (1, 3, tstzrange('2015-01-01', '2015-02-01')); UPDATE rooms SET valid_at = tstzrange('2014-01-01', null); DELETE FROM rooms; -- You can update an infinite fk more than covered by two rows INSERT INTO rooms VALUES (1, 3, tstzrange('2015-01-01', '2015-02-01')); UPDATE rooms SET valid_at = tstzrange('2014-06-01', null); DELETE FROM rooms; -- You can't update an infinite fk id not covered by any row INSERT INTO rooms VALUES (1, 3, tstzrange('2015-01-01', '2015-02-01')); UPDATE rooms SET house_id = 7; DELETE FROM rooms; -- You can't update an infinite fk range not covered by any row INSERT INTO rooms VALUES (1, 1, tstzrange('2015-01-01', '2015-02-01')); UPDATE rooms SET valid_at = tstzrange('2020-01-01', null); DELETE FROM rooms; -- You can't update an infinite fk partially covered by one row INSERT INTO rooms VALUES (1, 4, tstzrange(null, '2012-01-01')); UPDATE rooms SET valid_at = tstzrange(null, '2020-01-01'); DELETE FROM rooms; -- You can't update an infinite fk partially covered by two rows INSERT INTO rooms VALUES (1, 3, tstzrange('2015-01-01', '2015-02-01')); UPDATE rooms SET valid_at = tstzrange('1990-01-01', null); DELETE FROM rooms; DELETE FROM rooms; DELETE FROM houses; SELECT drop_temporal_foreign_key('room_has_a_house', 'rooms', 'houses');

<gh_stars>10-100 INSERT INTO book (id, publishingdate, title, isbn, version) VALUES (1, '2017-04-04', 'Hibernate Tips', '123-4567890123', 0); INSERT INTO review (id, comment, fkBook) VALUES (1, 'This is a review', 1); INSERT INTO review (id, comment, fkBook) VALUES (2, 'This is another review', 1);

<filename>server/create_tables/lte_tbmrodata.sql<gh_stars>0 CREATE TABLE `tbmrodata` ( `start_time` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci DEFAULT NULL, `serving_sector` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci DEFAULT NULL, `interfering_sector` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci DEFAULT NULL, `lte_sc_rsrp` float DEFAULT NULL, `lte_nc_rsrp` float DEFAULT NULL, `lte_nc_earfcn` float DEFAULT NULL, `lte_nc_pci` float DEFAULT NULL, KEY `tbmrodata_serving_sector_index` (`serving_sector`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci

SELECT min(t.title), min(t.production_year), min(chn.name) FROM cast_info ci, title t, char_name chn WHERE ci.movie_id = t.id AND chn.id = ci.person_role_id AND t.kind_id = 1 AND ci.role_id = 2;

<reponame>rchicangana/pica -------------------------------------------------------- -- Archivo creado - domingo-septiembre-02-2018 -------------------------------------------------------- -------------------------------------------------------- -- DDL for Table ESTADO_USER -------------------------------------------------------- CREATE TABLE "ESTADO_USER" ( "ID_ESTADO_USER" NUMBER(10,0), "ESTADO" VARCHAR2(100) ); -------------------------------------------------------- -- DDL for Table USUARIO -------------------------------------------------------- CREATE TABLE "USUARIO" ( "ID_USUARIO" NUMBER(10) NOT NULL, "NOMBRE" VARCHAR2(100) NOT NULL, "EMAIL" VARCHAR2(100) NOT NULL, "ID_ESTADO_USER" NUMBER(10,0) NOT NULL, "LOGIN" VARCHAR2(50) NOT NULL ); -------------------------------------------------------- -- DDL for Table USUARIO_ROLE -------------------------------------------------------- CREATE TABLE "USUARIO_ROLE" ( "ID" NUMBER(18,0), "ID_USUARIO" NUMBER(10), "ID_ROLE" NUMBER(10,0) ); -------------------------------------------------------- -- DDL for Table ROLE -------------------------------------------------------- CREATE TABLE "ROLE" ( "ID_ROLE" NUMBER(10,0), "ROLE" VARCHAR2(100) ); -------------------------------------------------------- -- DDL for Table MENU_ROLE -------------------------------------------------------- CREATE TABLE "MENU_ROLE" ( "ID_ROLE" NUMBER(10,0), "ID_MENU" NUMBER(10,0) ); -------------------------------------------------------- -- DDL for Table MENU -------------------------------------------------------- CREATE TABLE "MENU" ( "ID_MENU" NUMBER(10,0), "NOMBRE" VARCHAR2(50), "URL" VARCHAR2(210), "ID_MENU_PADRE" NUMBER(10,0), "ULTIMO_NIVEL" VARCHAR2(1), "ESTADO" NUMBER(10,0) ); REM INSERTING into ESTADO_USER SET DEFINE OFF; REM INSERTING into USUARIO SET DEFINE OFF; REM INSERTING into USUARIO_ROLE SET DEFINE OFF; REM INSERTING into ROLE SET DEFINE OFF; REM INSERTING into MENU_ROLE SET DEFINE OFF; REM INSERTING into MENU SET DEFINE OFF; -------------------------------------------------------- -- DDL for Index MENU_ROLE_PK -------------------------------------------------------- CREATE UNIQUE INDEX "MENU_ROLE_PK" ON "MENU_ROLE" ("ID_ROLE", "ID_MENU"); -------------------------------------------------------- -- DDL for Index SYS_C007723 -------------------------------------------------------- CREATE UNIQUE INDEX "SYS_C007723" ON "ESTADO_USER" ("ID_ESTADO_USER"); -------------------------------------------------------- -- DDL for Index SYS_C007728 -------------------------------------------------------- CREATE UNIQUE INDEX "SYS_C007728" ON "USUARIO" ("ID_USUARIO"); -------------------------------------------------------- -- DDL for Index SYS_C007736 -------------------------------------------------------- CREATE UNIQUE INDEX "SYS_C007736" ON "USUARIO_ROLE" ("ID"); -------------------------------------------------------- -- DDL for Index SYS_C007732 -------------------------------------------------------- CREATE UNIQUE INDEX "SYS_C007732" ON "ROLE" ("ID_ROLE"); -------------------------------------------------------- -- DDL for Index SYS_C007741 -------------------------------------------------------- CREATE UNIQUE INDEX "SYS_C007741" ON "MENU" ("ID_MENU"); -------------------------------------------------------- -- Constraints for Table ESTADO_USER -------------------------------------------------------- ALTER TABLE "ESTADO_USER" MODIFY ("ID_ESTADO_USER" NOT NULL ENABLE); ALTER TABLE "ESTADO_USER" MODIFY ("ESTADO" NOT NULL ENABLE); ALTER TABLE "ESTADO_USER" ADD PRIMARY KEY ("ID_ESTADO_USER") USING INDEX ENABLE; -------------------------------------------------------- -- Constraints for Table USUARIO -------------------------------------------------------- ALTER TABLE "USUARIO" MODIFY ("ID_USUARIO" NOT NULL ENABLE); ALTER TABLE "USUARIO" MODIFY ("NOMBRE" NOT NULL ENABLE); ALTER TABLE "USUARIO" MODIFY ("EMAIL" NOT NULL ENABLE); ALTER TABLE "USUARIO" MODIFY ("ID_ESTADO_USER" NOT NULL ENABLE); ALTER TABLE "USUARIO" ADD PRIMARY KEY ("ID_USUARIO") USING INDEX ENABLE; -------------------------------------------------------- -- Constraints for Table USUARIO_ROLE -------------------------------------------------------- ALTER TABLE "USUARIO_ROLE" MODIFY ("ID" NOT NULL ENABLE); ALTER TABLE "USUARIO_ROLE" MODIFY ("ID_USUARIO" NOT NULL ENABLE); ALTER TABLE "USUARIO_ROLE" MODIFY ("ID_ROLE" NOT NULL ENABLE); ALTER TABLE "USUARIO_ROLE" ADD PRIMARY KEY ("ID") USING INDEX ENABLE; -------------------------------------------------------- -- Constraints for Table ROLE -------------------------------------------------------- ALTER TABLE "ROLE" MODIFY ("ID_ROLE" NOT NULL ENABLE); ALTER TABLE "ROLE" MODIFY ("ROLE" NOT NULL ENABLE); ALTER TABLE "ROLE" ADD PRIMARY KEY ("ID_ROLE") USING INDEX ENABLE; -------------------------------------------------------- -- Constraints for Table MENU_ROLE -------------------------------------------------------- ALTER TABLE "MENU_ROLE" MODIFY ("ID_ROLE" NOT NULL ENABLE); ALTER TABLE "MENU_ROLE" MODIFY ("ID_MENU" NOT NULL ENABLE); ALTER TABLE "MENU_ROLE" ADD CONSTRAINT "MENU_ROLE_PK" PRIMARY KEY ("ID_ROLE", "ID_MENU") USING INDEX ENABLE; -------------------------------------------------------- -- Constraints for Table MENU -------------------------------------------------------- ALTER TABLE "MENU" MODIFY ("ID_MENU" NOT NULL ENABLE); ALTER TABLE "MENU" MODIFY ("NOMBRE" NOT NULL ENABLE); ALTER TABLE "MENU" MODIFY ("URL" NOT NULL ENABLE); ALTER TABLE "MENU" ADD PRIMARY KEY ("ID_MENU") USING INDEX ENABLE; -------------------------------------------------------- -- Ref Constraints for Table USUARIO -------------------------------------------------------- ALTER TABLE "USUARIO" ADD CONSTRAINT "ID_ESTADO_USER_FK_USUARIO" FOREIGN KEY ("ID_ESTADO_USER") REFERENCES "ESTADO_USER" ("ID_ESTADO_USER") ENABLE; -------------------------------------------------------- -- Ref Constraints for Table USUARIO_ROLE -------------------------------------------------------- ALTER TABLE "USUARIO_ROLE" ADD CONSTRAINT "ID_USUARIO_FK_USUARIO_ROLE" FOREIGN KEY ("ID_USUARIO") REFERENCES "USUARIO" ("ID_USUARIO") ENABLE; -------------------------------------------------------- -- Ref Constraints for Table MENU_ROLE -------------------------------------------------------- ALTER TABLE "MENU_ROLE" ADD CONSTRAINT "ID_ROLE_FK_MENU_ROLE" FOREIGN KEY ("ID_ROLE") REFERENCES "ROLE" ("ID_ROLE") ENABLE; ALTER TABLE "MENU_ROLE" ADD CONSTRAINT "ID_MENU_FK_MENU_ROLE" FOREIGN KEY ("ID_MENU") REFERENCES "MENU" ("ID_MENU") ENABLE;

/*==============================================================*/ /* Database name: Residency */ /* DBMS name: MySQL 5.0 */ /* Created on: 12/4/2016 5:40:12 PM */ /*==============================================================*/ drop database if exists Residency; /*==============================================================*/ /* Database: Residency */ /*==============================================================*/ create database Residency; use Residency; /*==============================================================*/ /* Table: CLAIMING_RESIDENCY */ /*==============================================================*/ create table CLAIMING_RESIDENCY ( CLAIMING_RESIDENCY_SEQ int not null auto_increment, SUPPORTING_DOCUMENTS_SEQ int, DEMONSTRATE_RESIDENCY_SEQ int, PERSON_NAME varchar(200), CLAIMANT_RELATIONSHIP varchar(100), ADDRESS varchar(200), PHONE_NUMBER varchar(50), RESIDENCY_DATE datetime, USER_SEQ_ENT_BY numeric(10,0), DT_ENT datetime, USER_SEQ_CHG_BY numeric(10,0), DT_CHG datetime, primary key (CLAIMING_RESIDENCY_SEQ) ); /*==============================================================*/ /* Table: DEMONSTRATE_RESIDENCY */ /*==============================================================*/ create table DEMONSTRATE_RESIDENCY ( DEMONSTRATE_RESIDENCY_SEQ int not null auto_increment, CODE varchar(20), DESCRIPTION varchar(200), USER_SEQ_ENT_BY numeric(10,0), DT_ENT datetime, USER_SEQ_CHG_BY numeric(10,0), DT_CHG datetime, primary key (DEMONSTRATE_RESIDENCY_SEQ) ); /*==============================================================*/ /* Table: EVIDENCE_OF_RESIDENCY */ /*==============================================================*/ create table EVIDENCE_OF_RESIDENCY ( EVIDENCE_OF_RESIDENCY_SEQ int not null auto_increment, CODE varchar(20), DESCRIPTION varchar(200), USER_SEQ_ENT_BY numeric(10,0), DT_ENT datetime, USER_SEQ_CHG_BY numeric(10,0), DT_CHG datetime, primary key (EVIDENCE_OF_RESIDENCY_SEQ) ); /*==============================================================*/ /* Table: NON_CITIZEN */ /*==============================================================*/ create table NON_CITIZEN ( NON_CITIZEN_SEQ int not null auto_increment, ALIEN_REGISTRATION_NUMBER numeric(10,0) not null, ISSUE_DATE datetime, VISA_CATEGORY varchar(20), USER_SEQ_ENT_BY numeric(10,0), DT_ENT datetime, USER_SEQ_CHG_BY numeric(10,0), DT_CHG datetime, primary key (NON_CITIZEN_SEQ) ); /*==============================================================*/ /* Table: NON_RESIDENT */ /*==============================================================*/ create table NON_RESIDENT ( NON_RESIDENT_SEQ int not null auto_increment, SIGNATURE varchar(200) not null, DATE datetime not null, USER_SEQ_ENT_BY numeric(10,0), DT_ENT datetime, USER_SEQ_CHG_BY numeric(10,0), DT_CHG datetime, primary key (NON_RESIDENT_SEQ) ); /*==============================================================*/ /* Table: QUALIFICATION */ /*==============================================================*/ create table QUALIFICATION ( QUALIFICATION_SEQ int not null auto_increment, CODE varchar(20), DESCRIPTION varchar(200), USER_SEQ_ENT_BY numeric(10,0), DT_ENT datetime, USER_SEQ_CHG_BY numeric(10,0), DT_CHG datetime, primary key (QUALIFICATION_SEQ) ); /*==============================================================*/ /* Table: QUALIFICATION_EXCEPTION */ /*==============================================================*/ create table QUALIFICATION_EXCEPTION ( QUALIFICATION_SEQ int, USER_SEQ_ENT_BY numeric(10,0), DT_ENT datetime, USER_SEQ_CHG_BY numeric(10,0), DT_CHG datetime ); /*==============================================================*/ /* Table: RESIDENCY_DECLARATION */ /*==============================================================*/ create table RESIDENCY_DECLARATION ( RESIDENCY_DECLARATION_SEQ int not null auto_increment, STUDENT_NAME varchar(200), CLAIMANT_NAME varchar(200), SIGNATURE varchar(200) not null, DATE datetime not null, USER_SEQ_ENT_BY numeric(10,0), DT_ENT datetime, USER_SEQ_CHG_BY numeric(10,0), DT_CHG datetime, primary key (RESIDENCY_DECLARATION_SEQ) ); /*==============================================================*/ /* Table: STATUS */ /*==============================================================*/ create table STATUS ( STATUS_SEQ int not null auto_increment, CODE varchar(15), DESCRIPTION varchar(200), primary key (STATUS_SEQ) ); /*==============================================================*/ /* Table: STUDENT */ /*==============================================================*/ create table STUDENT ( STUDENT_SEQ int not null auto_increment, STUDENT_TYPE_SEQ int, NON_CITIZEN_SEQ int, NON_RESIDENT_SEQ int, STUDENT_NAME varchar(40), Z_NUMBER numeric(8,0), BIRTHDAY datetime, USER_SEQ_ENT_BY numeric(10,0), DT_ENT datetime, USER_SEQ_CHG_BY numeric(10,0), DT_CHG datetime, primary key (STUDENT_SEQ) ); /*==============================================================*/ /* Table: STUDENT_RESIDENCY */ /*==============================================================*/ create table STUDENT_RESIDENCY ( STUDENT_RESIDENCY_SEQ int not null auto_increment, CLAIMING_RESIDENCY_SEQ int, STUDENT_SEQ int, USER_SEQ int, RESIDENCY_DECLARATION_SEQ int, STATUS_SEQ int, EVIDENCE_OF_RESIDENCY_SEQ int, YEAR smallint, USER_SEQ_ENT_BY numeric(10,0), DT_ENT datetime, USER_SEQ_CHG_BY numeric(10,0), DT_CHG datetime, primary key (STUDENT_RESIDENCY_SEQ) ); /*==============================================================*/ /* Table: STUDENT_TYPE */ /*==============================================================*/ create table STUDENT_TYPE ( STUDENT_TYPE_SEQ int not null auto_increment, CODE varchar(20), DESCRIPTION varchar(200), USER_SEQ_ENT_BY numeric(10,0), DT_ENT datetime, USER_SEQ_CHG_BY numeric(10,0), DT_CHG datetime, primary key (STUDENT_TYPE_SEQ) ); /*==============================================================*/ /* Table: SUPPORTING_DOCUMENTS */ /*==============================================================*/ create table SUPPORTING_DOCUMENTS ( SUPPORTING_DOCUMENTS_SEQ int not null auto_increment, VOTER_REGISTRATION varchar(50), VOTER_ISSUE_DATE datetime, DRIVERS_LICENSE varchar(50), DRIVERS_ISSUE_DATE datetime, DRIVERS_CURRENT_DATE datetime, STATE_ID varchar(50), STATE_ISSUE_DATE datetime, STATE_CURRENT_DATE datetime, VEHICLE_REGISTRATION varchar(50), VEHICLE_ISSUE_DATE datetime, VEHICLE_CURRENT_DATE datetime, PERMANENT_HOME smallint, HOMESTEAD_EXEMPTION smallint, HIGHSCHOOL_OFFICIAL_TRANSCRIPT smallint, HIGHSCHOOL_DATES_ATTENDED varchar(50), HIGHSCHOOL_GRADUATION datetime, FULLTIME_EMPLOYMENT smallint, USER_SEQ_ENT_BY numeric(10,0), DT_ENT datetime, USER_SEQ_CHG_BY numeric(10,0), DT_CHG datetime, primary key (SUPPORTING_DOCUMENTS_SEQ) ); /*==============================================================*/ /* Table: UPLOADED_DOCUMENTS */ /*==============================================================*/ create table UPLOADED_DOCUMENTS ( UPLOADED_DOCUMENTS_SEQ numeric(10,0) not null, FILE_PATH char(10), primary key (UPLOADED_DOCUMENTS_SEQ) ); /*==============================================================*/ /* Table: USER */ /*==============================================================*/ create table USER ( USER_SEQ int not null auto_increment, USER_ROLE_SEQ int, FIRST_NAME varchar(50), LAST_NAME varchar(50), Z_NUMBER numeric(8,0), EMAIL_ADDRESS varchar(50), PHONE_NUMBER varchar(25), ADDRESS varchar(200), USER_SEQ_ENT_BY numeric(10,0), DT_ENT datetime, USER_SEQ_CHG_BY numeric(10,0), DT_CHG datetime, primary key (USER_SEQ) ); /*==============================================================*/ /* Table: USER_ROLE */ /*==============================================================*/ create table USER_ROLE ( USER_ROLE_SEQ int not null auto_increment, USER_ROLE_CODE varchar(20), USER_ROLE_DESCRIPTION varchar(150), USER_SEQ_ENT_BY numeric(10,0), DT_ENT datetime, USER_SEQ_CHG_BY numeric(10,0), DT_CHG datetime, primary key (USER_ROLE_SEQ) ); alter table CLAIMING_RESIDENCY add constraint FK_REFERENCE_7 foreign key (SUPPORTING_DOCUMENTS_SEQ) references SUPPORTING_DOCUMENTS (SUPPORTING_DOCUMENTS_SEQ) on delete restrict on update restrict; alter table CLAIMING_RESIDENCY add constraint FK_REFERENCE_8 foreign key (DEMONSTRATE_RESIDENCY_SEQ) references DEMONSTRATE_RESIDENCY (DEMONSTRATE_RESIDENCY_SEQ) on delete restrict on update restrict; alter table QUALIFICATION_EXCEPTION add constraint FK_REFERENCE_16 foreign key (QUALIFICATION_SEQ) references QUALIFICATION (QUALIFICATION_SEQ) on delete restrict on update restrict; alter table STUDENT add constraint FK_REFERENCE_4 foreign key (STUDENT_TYPE_SEQ) references STUDENT_TYPE (STUDENT_TYPE_SEQ) on delete restrict on update restrict; alter table STUDENT add constraint FK_REFERENCE_5 foreign key (NON_CITIZEN_SEQ) references NON_CITIZEN (NON_CITIZEN_SEQ) on delete restrict on update restrict; alter table STUDENT add constraint FK_REFERENCE_6 foreign key (NON_RESIDENT_SEQ) references NON_RESIDENT (NON_RESIDENT_SEQ) on delete restrict on update restrict; alter table STUDENT_RESIDENCY add constraint FK_REFERENCE_11 foreign key (STUDENT_SEQ) references STUDENT (STUDENT_SEQ) on delete restrict on update restrict; alter table STUDENT_RESIDENCY add constraint FK_REFERENCE_13 foreign key (USER_SEQ) references USER (USER_SEQ) on delete restrict on update restrict; alter table STUDENT_RESIDENCY add constraint FK_REFERENCE_14 foreign key (RESIDENCY_DECLARATION_SEQ) references RESIDENCY_DECLARATION (RESIDENCY_DECLARATION_SEQ) on delete restrict on update restrict; alter table STUDENT_RESIDENCY add constraint FK_REFERENCE_15 foreign key (STATUS_SEQ) references STATUS (STATUS_SEQ) on delete restrict on update restrict; alter table STUDENT_RESIDENCY add constraint FK_REFERENCE_17 foreign key (EVIDENCE_OF_RESIDENCY_SEQ) references EVIDENCE_OF_RESIDENCY (EVIDENCE_OF_RESIDENCY_SEQ) on delete restrict on update restrict; alter table STUDENT_RESIDENCY add constraint FK_REFERENCE_9 foreign key (CLAIMING_RESIDENCY_SEQ) references CLAIMING_RESIDENCY (CLAIMING_RESIDENCY_SEQ) on delete cascade on update restrict; alter table USER add constraint FK_REFERENCE_12 foreign key (USER_ROLE_SEQ) references USER_ROLE (USER_ROLE_SEQ) on delete restrict on update restrict;

set client_min_messages to warning; create extension if not exists pgtap; reset client_min_messages; begin; select plan(3); select has_function( 'ggircs_portal', 'fuel_is_carbon_taxed', array['ggircs_portal.fuel'], 'Function ggircs_portal.fuel_is_carbon_taxed should exist' ); -- test data insert into swrs.fuel_carbon_tax_details(normalized_fuel_type, carbon_tax_act_fuel_type_id) values ('Non carbon taxed test fuel - normalized', null), ('Carbon taxed test fuel - normalized', 1); -- Aviation fuel insert into swrs.fuel_mapping(fuel_type, fuel_carbon_tax_details_id) values ('Non carbon taxed test fuel', (select id from swrs.fuel_carbon_tax_details where normalized_fuel_type='Non carbon taxed test fuel - normalized')), ('Carbon taxed test fuel', (select id from swrs.fuel_carbon_tax_details where normalized_fuel_type='Carbon taxed test fuel - normalized')); insert into ggircs_portal.fuel(name, swrs_fuel_mapping_id) values ('Non carbon taxed test fuel', (select id from swrs.fuel_mapping where fuel_type='Non carbon taxed test fuel')), ('Carbon taxed test fuel', (select id from swrs.fuel_mapping where fuel_type='Carbon taxed test fuel')); select is( ( with tested_fuel as ( select row(fuel.*)::ggircs_portal.fuel from ggircs_portal.fuel where name='Carbon taxed test fuel' ) select ggircs_portal.fuel_is_carbon_taxed((select * from tested_fuel)) ), true, 'Function returns true if the fuel has a carbon tax act fuel type id' ); select is( ( with tested_fuel as ( select row(fuel.*)::ggircs_portal.fuel from ggircs_portal.fuel where name='Non carbon taxed test fuel' ) select ggircs_portal.fuel_is_carbon_taxed((select * from tested_fuel)) ), false, 'Function returns false if the fuel has a carbon tax act fuel type id' ); select finish(); rollback;

<reponame>opengauss-mirror/Yat -- @testpoint: opengauss关键字exists(非保留)，作为游标名，部分测试点合理报错 --前置条件 drop table if exists exists_test cascade; create table exists_test(cid int,fid int); --关键字不带引号-成功 start transaction; cursor exists for select * from exists_test order by 1; close exists; end; --关键字带双引号-成功 start transaction; cursor "exists" for select * from exists_test order by 1; close "exists"; end; --关键字带单引号-合理报错 start transaction; cursor 'exists' for select * from exists_test order by 1; close 'exists'; end; --关键字带反引号-合理报错 start transaction; cursor `exists` for select * from exists_test order by 1; close `exists`; end; drop table if exists exists_test cascade;

--Oracle SELECT TS.tenpo_id, TS.tenpo_mei, TS.shohin_id, S.shohin_mei FROM TenpoShohin TS CROSS JOIN Shohin S;

CREATE TABLE IF NOT EXISTS tasks ( task_id INT AUTO_INCREMENT, title VARCHAR(255) NOT NULL, start_date DATE, due_date DATE, priority TINYINT NOT NULL DEFAULT 3, description TEXT, PRIMARY KEY (task_id) ); INSERT INTO tasks(title, priority) VALUES ('My first task', 1), ('It is the second task',2), ('This is the third task of the week',3);

-- phpMyAdmin SQL Dump -- version 4.8.3 -- https://www.phpmyadmin.net/ -- -- Host: 127.0.0.1 -- Generation Time: Dec 01, 2018 at 10:11 PM -- Server version: 10.1.36-MariaDB -- PHP Version: 7.2.11 SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO"; SET AUTOCOMMIT = 0; START TRANSACTION; SET time_zone = "+00:00"; /*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */; /*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */; /*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */; /*!40101 SET NAMES utf8mb4 */; -- Database: `test` -- CREATE DATABASE IF NOT EXISTS `test` DEFAULT CHARACTER SET latin1 COLLATE latin1_swedish_ci; USE `test`; -- -------------------------------------------------------- -- -- Table structure for table `categories` -- CREATE TABLE `categories` ( `cat_id` int(8) NOT NULL, `cat_name` varchar(255) NOT NULL, `cat_description` varchar(255) NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=latin1; -- -------------------------------------------------------- -- -- Table structure for table `posts` -- CREATE TABLE `posts` ( `post_id` int(8) NOT NULL, `post_content` text NOT NULL, `post_date` datetime NOT NULL, `post_topic` int(8) NOT NULL, `post_by` int(8) NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=latin1; -- -------------------------------------------------------- -- -- Table structure for table `topics` -- CREATE TABLE `topics` ( `topic_id` int(8) NOT NULL, `topic_subject` varchar(255) NOT NULL, `topic_date` datetime NOT NULL, `topic_cat` int(8) NOT NULL, `topic_by` int(8) NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=latin1; -- -------------------------------------------------------- -- -- Table structure for table `users` -- CREATE TABLE `users` ( `user_id` int(8) NOT NULL, `user_name` varchar(30) NOT NULL, `user_pass` varchar(255) NOT NULL, `user_email` varchar(255) NOT NULL, `user_date` datetime NOT NULL, `user_level` int(8) NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=latin1; -- -- Dumping data for table `users` -- INSERT INTO `users` (`user_id`, `user_name`, `user_pass`, `user_email`, `user_date`, `user_level`) VALUES (1, 'AniketMan', '<PASSWORD>', '<EMAIL>', '2018-11-04 18:33:06', 0), (2, 'test', '<PASSWORD>', '<EMAIL>', '2018-11-06 18:43:35', 0), (3, 'bob', '<PASSWORD>', '<EMAIL>', '2018-11-07 12:51:35', 0); -- -- Indexes for dumped tables -- -- -- Indexes for table `categories` -- ALTER TABLE `categories` ADD PRIMARY KEY (`cat_id`), ADD UNIQUE KEY `cat_name_unique` (`cat_name`); -- -- Indexes for table `posts` -- ALTER TABLE `posts` ADD PRIMARY KEY (`post_id`); -- -- Indexes for table `topics` -- ALTER TABLE `topics` ADD PRIMARY KEY (`topic_id`), ADD KEY `topic_cat` (`topic_cat`), ADD KEY `topic_by` (`topic_by`); -- -- Indexes for table `users` -- ALTER TABLE `users` ADD PRIMARY KEY (`user_id`), ADD UNIQUE KEY `user_name_unique` (`user_name`); -- -- AUTO_INCREMENT for dumped tables -- -- -- AUTO_INCREMENT for table `categories` -- ALTER TABLE `categories` MODIFY `cat_id` int(8) NOT NULL AUTO_INCREMENT; -- -- AUTO_INCREMENT for table `posts` -- ALTER TABLE `posts` MODIFY `post_id` int(8) NOT NULL AUTO_INCREMENT; -- -- AUTO_INCREMENT for table `topics` -- ALTER TABLE `topics` MODIFY `topic_id` int(8) NOT NULL AUTO_INCREMENT; -- -- AUTO_INCREMENT for table `users` -- ALTER TABLE `users` MODIFY `user_id` int(8) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=4; -- -- Constraints for dumped tables -- -- -- Constraints for table `topics` -- ALTER TABLE `topics` ADD CONSTRAINT `topics_ibfk_1` FOREIGN KEY (`topic_cat`) REFERENCES `categories` (`cat_id`) ON DELETE CASCADE ON UPDATE CASCADE, ADD CONSTRAINT `topics_ibfk_2` FOREIGN KEY (`topic_by`) REFERENCES `users` (`user_id`) ON UPDATE CASCADE; COMMIT; /*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */; /*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */; /*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */; CREATE USER 'forum'@'localhost' IDENTIFIED BY 'changeme'; GRANT ALL PRIVILEGES ON test.* TO 'forum'@'localhost';

<filename>sql/se.sql -- phpMyAdmin SQL Dump -- version 4.5.2 -- http://www.phpmyadmin.net -- -- Host: 127.0.0.1 -- Generation Time: Dec 31, 2015 at 01:44 PM -- Server version: 5.6.17 -- PHP Version: 5.5.12 SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO"; SET time_zone = "+00:00"; /*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */; /*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */; /*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */; /*!40101 SET NAMES utf8mb4 */; -- -- Database: `se` -- -- -------------------------------------------------------- -- -- Table structure for table `sellpost` -- CREATE TABLE `sellpost` ( `number` int(11) NOT NULL, `tipe` varchar(20) NOT NULL, `judul` varchar(160) NOT NULL, `tanggal` datetime NOT NULL, `harga` double NOT NULL, `alamat` varchar(100) NOT NULL, `deskripsi` varchar(500) NOT NULL, `gambar` varchar(60) NOT NULL, `status` varchar(10) NOT NULL, `user` varchar(12) NOT NULL, `keterangan` varchar(160) NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=latin1; -- -- Dumping data for table `sellpost` -- INSERT INTO `sellpost` (`number`, `tipe`, `judul`, `tanggal`, `harga`, `alamat`, `deskripsi`, `gambar`, `status`, `user`, `keterangan`) VALUES (4, 'Perjalanan', 'Bon Jovi live Jakarta', '2015-09-10 00:00:00', 140000, 'Jakarta', 'Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Aenean commodo ligula eget dolor. Aenean massa. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Donec quam felis, ultricies nec, pellentesque eu, pretium quis, sem. Nulla consequat massa quis enim. Donec pede justo, fringilla vel, aliquet nec, vulputate eget, arcu. In enim justo, rhoncus ut, imperdiet a, venenatis vitae, justo.', 'ticket3.jpg', 'sold', 'Lambang', ''), (5, 'Perjalanan', 'Bromo', '2015-09-12 10:30:00', 140000, 'Malang', 'Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Aenean commodo ligula eget dolor. Aenean massa. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Donec quam felis, ultricies nec, pellentesque eu, pretium quis, sem. Nulla consequat massa quis enim. Donec pede justo, fringilla vel, aliquet nec, vulputate eget, arcu. In enim justo, rhoncus ut, imperdiet a, venenatis vitae, justo.', 'ticket2.jpg', 'reserved', 'brolin', 'lambang'), (6, 'Pariwisata', 'ticket bromo', '2015-10-04 07:35:00', 200000, 'Semarang', 'Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Aenean commodo ligula eget dolor. Aenean massa. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Donec quam felis, ultricies nec, pellentesque eu, pretium quis, sem. Nulla consequat massa quis enim. Donec pede justo, fringilla vel, aliquet nec, vulputate eget, arcu. In enim justo, rhoncus ut, imperdiet a, venenatis vitae, justo.', 'ticket1.jpg', 'deactived', 'brolin', 'post ini melanggar peraturan kami'), (7, 'Perjalanan', 'Tiket ke Dieg', '2016-03-10 05:25:00', 300000, 'Jakarte', 'Jual ticket ke dieg magelang harga murah. Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Aenean commodo ligula eget dolor. Aenean massa. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Donec quam felis, ultricies nec, pellentesque eu, pretium quis, sem.', 'ticket4.jpg', 'reserved', 'brolin', 'lambang'), (8, 'Perjalanan', 'Tiket ke Bromo', '2016-05-04 07:35:00', 200000, 'Semarang', 'Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Aenean commodo ligula eget dolor. Aenean massa. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Donec quam felis, ultricies nec, pellentesque eu, pretium quis, sem. Nulla consequat massa quis enim. Donec pede justo, fringilla vel, aliquet nec, vulputate eget, arcu. In enim justo, rhoncus ut, imperdiet a, venenatis vitae, justo.', 'ticket2.jpg', 'active', 'Lambang', ''), (9, 'Perjalanan', 'Tiket ke Dufan Murah', '2016-02-04 07:35:00', 200000, 'Semarang', 'Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Aenean commodo ligula eget dolor. Aenean massa. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Donec quam felis, ultricies nec, pellentesque eu, pretium quis, sem. Nulla consequat massa quis enim. Donec pede justo, fringilla vel, aliquet nec, vulputate eget, arcu. In enim justo, rhoncus ut, imperdiet a, venenatis vitae, justo.', 'ticket2.jpg', 'sold', 'Brolin', ''), (10, 'Pariwisata', 'Tiket Pariwisata ke Dieg', '2016-01-15 06:07:13', 320000, 'Magelang', 'Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Aenean commodo ligula eget dolor. Aenean massa. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Donec quam felis, ultricies nec, pellentesque eu, pretium quis, sem', 'ticket3.jpg', 'sold', 'lambang', 'brolin'); -- -------------------------------------------------------- -- -- Table structure for table `users` -- CREATE TABLE `users` ( `username` varchar(10) NOT NULL, `password` varchar(32) NOT NULL, `email` varchar(50) NOT NULL, `hp` varchar(50) NOT NULL, `kota` varchar(32) NOT NULL, `regdate` year(4) NOT NULL, `gambar` varchar(20) NOT NULL DEFAULT 'default.jpg' ) ENGINE=InnoDB DEFAULT CHARSET=latin1; -- -- Dumping data for table `users` -- INSERT INTO `users` (`username`, `password`, `email`, `hp`, `kota`, `regdate`, `gambar`) VALUES ('brolin', '<PASSWORD>', '<EMAIL>', '084679987493', 'Bandung', 2013, 'user1.jpg'), ('Kikiy', '123', '<EMAIL>', '086787309812', 'Semarang', 2010, ''), ('lambang', '<PASSWORD>', '<EMAIL>', '083245672135', 'Semarang', 2015, 'user.jpg'), ('Rolies', '827ccb0eea8a706c4c34a16891f84e7b', '<EMAIL>', '082384625996', 'Pekanbaru', 2015, 'default.jpg'), ('Youngky', '827ccb0eea8a706c4c34a16891f84e7b', '<EMAIL>', '082357808721', 'Jakarta', 2015, ''); -- -- Indexes for dumped tables -- -- -- Indexes for table `sellpost` -- ALTER TABLE `sellpost` ADD PRIMARY KEY (`number`); -- -- Indexes for table `users` -- ALTER TABLE `users` ADD PRIMARY KEY (`username`); -- -- AUTO_INCREMENT for dumped tables -- -- -- AUTO_INCREMENT for table `sellpost` -- ALTER TABLE `sellpost` MODIFY `number` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=11; /*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */; /*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */; /*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;

-- phpMyAdmin SQL Dump -- version 5.0.2 -- https://www.phpmyadmin.net/ -- -- Host: 127.0.0.1 -- Waktu pembuatan: 30 Des 2020 pada 18.30 -- Versi server: 10.4.11-MariaDB -- Versi PHP: 7.4.6 SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO"; START TRANSACTION; SET time_zone = "+00:00"; /*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */; /*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */; /*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */; /*!40101 SET NAMES utf8mb4 */; -- -- Database: `db_arsip` -- -- -------------------------------------------------------- -- -- Struktur dari tabel `auth_activation_attempts` -- CREATE TABLE `auth_activation_attempts` ( `id` int(11) UNSIGNED NOT NULL, `ip_address` varchar(255) NOT NULL, `user_agent` varchar(255) NOT NULL, `token` varchar(255) DEFAULT NULL, `created_at` datetime NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8; -- -------------------------------------------------------- -- -- Struktur dari tabel `auth_groups` -- CREATE TABLE `auth_groups` ( `id` int(11) UNSIGNED NOT NULL, `name` varchar(255) NOT NULL, `description` varchar(255) NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8; -- -------------------------------------------------------- -- -- Struktur dari tabel `auth_groups_permissions` -- CREATE TABLE `auth_groups_permissions` ( `group_id` int(11) UNSIGNED NOT NULL DEFAULT 0, `permission_id` int(11) UNSIGNED NOT NULL DEFAULT 0 ) ENGINE=InnoDB DEFAULT CHARSET=utf8; -- -------------------------------------------------------- -- -- Struktur dari tabel `auth_groups_users` -- CREATE TABLE `auth_groups_users` ( `group_id` int(11) UNSIGNED NOT NULL DEFAULT 0, `user_id` int(11) UNSIGNED NOT NULL DEFAULT 0 ) ENGINE=InnoDB DEFAULT CHARSET=utf8; -- -------------------------------------------------------- -- -- Struktur dari tabel `auth_logins` -- CREATE TABLE `auth_logins` ( `id` int(11) UNSIGNED NOT NULL, `ip_address` varchar(255) DEFAULT NULL, `email` varchar(255) DEFAULT NULL, `user_id` int(11) UNSIGNED DEFAULT NULL, `date` datetime NOT NULL, `success` tinyint(1) NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8; -- -- Dumping data untuk tabel `auth_logins` -- INSERT INTO `auth_logins` (`id`, `ip_address`, `email`, `user_id`, `date`, `success`) VALUES (1, '::1', '<EMAIL>', 1, '2020-12-10 13:51:30', 1), (2, '::1', 'habib', NULL, '2020-12-18 07:08:46', 0), (3, '::1', 'habib', NULL, '2020-12-18 07:09:57', 0), (4, '::1', 'habib', NULL, '2020-12-18 07:12:31', 0), (5, '::1', '<EMAIL>', 2, '2020-12-18 07:14:39', 1), (6, '::1', '<EMAIL>', 2, '2020-12-18 08:03:26', 1), (7, '::1', 'admin', NULL, '2020-12-18 09:19:08', 0), (8, '::1', '<EMAIL>@admin.<EMAIL>', 2, '2020-12-18 09:19:24', 1), (9, '::1', '<EMAIL>', 2, '2020-12-18 20:40:35', 1), (10, '::1', '<EMAIL>', 2, '2020-12-19 03:01:12', 1), (11, '::1', '<EMAIL>', 2, '2020-12-19 08:55:44', 1), (12, '::1', '<EMAIL>', 2, '2020-12-21 09:13:22', 1), (13, '::1', '<EMAIL>', 2, '2020-12-21 11:00:59', 1), (14, '::1', '<EMAIL>', 2, '2020-12-22 09:05:08', 1), (15, '::1', '<EMAIL>', 2, '2020-12-24 09:06:02', 1), (16, '::1', '<EMAIL>', 2, '2020-12-25 07:36:43', 1), (17, '::1', '<EMAIL>', 2, '2020-12-25 23:27:41', 1), (18, '::1', '<EMAIL>', 2, '2020-12-26 21:08:06', 1), (19, '::1', '<EMAIL>', 2, '2020-12-26 21:24:33', 1), (20, '::1', '<EMAIL>', 2, '2020-12-27 00:25:25', 1), (21, '::1', '<EMAIL>', 2, '2020-12-27 04:26:27', 1), (22, '::1', 'admin', NULL, '2020-12-27 07:14:48', 0), (23, '::1', '<EMAIL>', 2, '2020-12-27 07:17:22', 1), (24, '::1', '<EMAIL>', 2, '2020-12-27 19:49:26', 1), (25, '::1', '<EMAIL>', 2, '2020-12-28 06:16:10', 1), (26, '::1', '<EMAIL>', 2, '2020-12-29 07:04:35', 1), (27, '::1', '<EMAIL>', 2, '2020-12-29 18:57:34', 1), (28, '::1', '<EMAIL>', 2, '2020-12-30 05:10:01', 1); -- -------------------------------------------------------- -- -- Struktur dari tabel `auth_permissions` -- CREATE TABLE `auth_permissions` ( `id` int(11) UNSIGNED NOT NULL, `name` varchar(255) NOT NULL, `description` varchar(255) NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8; -- -------------------------------------------------------- -- -- Struktur dari tabel `auth_reset_attempts` -- CREATE TABLE `auth_reset_attempts` ( `id` int(11) UNSIGNED NOT NULL, `email` varchar(255) NOT NULL, `ip_address` varchar(255) NOT NULL, `user_agent` varchar(255) NOT NULL, `token` varchar(255) DEFAULT NULL, `created_at` datetime NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8; -- -------------------------------------------------------- -- -- Struktur dari tabel `auth_tokens` -- CREATE TABLE `auth_tokens` ( `id` int(11) UNSIGNED NOT NULL, `selector` varchar(255) NOT NULL, `hashedValidator` varchar(255) NOT NULL, `user_id` int(11) UNSIGNED NOT NULL, `expires` datetime NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8; -- -------------------------------------------------------- -- -- Struktur dari tabel `auth_users_permissions` -- CREATE TABLE `auth_users_permissions` ( `user_id` int(11) UNSIGNED NOT NULL DEFAULT 0, `permission_id` int(11) UNSIGNED NOT NULL DEFAULT 0 ) ENGINE=InnoDB DEFAULT CHARSET=utf8; -- -------------------------------------------------------- -- -- Struktur dari tabel `dokumen` -- CREATE TABLE `dokumen` ( `id` int(11) NOT NULL, `no_surat` varchar(255) NOT NULL, `perihal` varchar(255) NOT NULL, `slug` varchar(255) NOT NULL, `jenis` varchar(255) NOT NULL, `tgl_pembuatan` date NOT NULL, `no_filling_kabinet` varchar(50) NOT NULL, `nama_folder` varchar(50) NOT NULL, `file_surat` varchar(255) NOT NULL, `created_at` datetime DEFAULT NULL, `updated_at` datetime DEFAULT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4; -- -- Dumping data untuk tabel `dokumen` -- INSERT INTO `dokumen` (`id`, `no_surat`, `perihal`, `slug`, `jenis`, `tgl_pembuatan`, `no_filling_kabinet`, `nama_folder`, `file_surat`, `created_at`, `updated_at`) VALUES (26, '003', 'Surat Keputusan Presiden', 'surat-keputusan-presiden', 'Surat Keterangan', '0000-00-00', '', '', '644-Article Text-2278-1-10-20171125.pdf', '2020-12-21 11:21:20', '2020-12-23 01:34:26'), (27, '003', 'Surat AB', 'surat-ab', 'Daftar Pegawai ', '0000-00-00', '12P', '3F', 'document(1).pdf', '2020-12-21 11:26:57', '2020-12-29 22:14:05'), (28, '0011', 'Surat Luar', 'surat-luar', 'Surat Izin', '0000-00-00', '', '', 'Eemeren-Houtlosser2006_Article_StrategicManeuveringASynthetic.pdf', '2020-12-21 11:30:20', '2020-12-22 00:32:37'), (30, '0011', 'Surat Y', 'surat-y', 'Haha', '2020-02-12', '12E', '8A', '09E01004_1.pdf', '2020-12-22 12:22:39', '2020-12-23 01:45:05'), (32, '900', 'Surat Z', 'surat-z', 'Daftar Pegawai ', '0000-00-00', '199B', '', '09E01004_unlocked.pdf', '2020-12-22 12:25:11', '2020-12-23 01:44:15'), (33, '0988123', 'Surat Pemberitahuan', 'surat-pemberitahuan', '', '2020-12-17', '34', '9P', 'Workshop Pemrograman_2.pdf', '2020-12-27 21:40:23', '2020-12-28 11:05:54'); -- -------------------------------------------------------- -- -- Struktur dari tabel `migrations` -- CREATE TABLE `migrations` ( `id` bigint(20) UNSIGNED NOT NULL, `version` varchar(255) NOT NULL, `class` text NOT NULL, `group` varchar(255) NOT NULL, `namespace` varchar(255) NOT NULL, `time` int(11) NOT NULL, `batch` int(11) UNSIGNED NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8; -- -- Dumping data untuk tabel `migrations` -- INSERT INTO `migrations` (`id`, `version`, `class`, `group`, `namespace`, `time`, `batch`) VALUES (1, '2017-11-20-223112', 'Myth\\Auth\\Database\\Migrations\\CreateAuthTables', 'default', 'Myth\\Auth', 1607628437, 1); -- -------------------------------------------------------- -- -- Struktur dari tabel `riwayat` -- CREATE TABLE `riwayat` ( `id` int(11) NOT NULL, `id_user` int(11) NOT NULL, `id_dokumen` int(11) NOT NULL, `no_surat` varchar(255) NOT NULL, `perihal` varchar(255) NOT NULL, `keterangan` varchar(255) NOT NULL, `waktu` datetime NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4; -- -- Dumping data untuk tabel `riwayat` -- INSERT INTO `riwayat` (`id`, `id_user`, `id_dokumen`, `no_surat`, `perihal`, `keterangan`, `waktu`) VALUES (14, 2, 26, '001', 'Surat Keputusan Presiden', 'Ditambahkan', '2020-12-22 00:21:20'), (15, 2, 27, '003', 'Surat AB', 'Ditambahkan', '2020-12-22 00:26:57'), (16, 2, 30, '0011', 'Surat Y', 'Ditambahkan', '2020-12-22 00:30:20'), (17, 2, 30, '0011', 'Surat Y', 'Diubah (Perihal)', '2020-12-22 00:32:37'), (18, 2, 27, '003', 'Surat AB', 'Berkas Fisik Diambil', '2020-12-22 00:32:46'), (19, 2, 0, '0023', 'Surat LK', 'Ditambahkan', '2020-12-22 00:33:22'), (20, 2, 0, '0023', 'Surat LK', 'Dihapus', '2020-12-22 00:33:45'), (21, 2, 30, '0011', 'Surat Y', 'Ditambahkan', '2020-12-23 01:22:40'), (22, 2, 32, '900', 'Surat Z', 'Ditambahkan', '2020-12-23 01:23:24'), (23, 2, 32, '900', 'Surat Z', 'Dihapus', '2020-12-23 01:24:34'), (24, 2, 32, '900', 'Surat Z', 'Ditambahkan', '2020-12-23 01:25:11'), (25, 2, 26, '001', 'Surat Keputusan Presiden', 'Diubah (No Surat)', '2020-12-23 01:33:32'), (26, 2, 26, '003', 'Surat Keputusan Presiden', 'Diubah (File Surat)', '2020-12-23 01:33:57'), (27, 2, 26, '003', 'Surat Keputusan Presiden', 'Diubah (File Surat)', '2020-12-23 01:34:26'), (28, 2, 32, '900', 'Surat Z', 'Diubah (Nomor Filling Kabinet)', '2020-12-23 01:44:15'), (29, 2, 30, '0011', 'Surat Y', 'Diubah (Nomor Filling Kabinet)', '2020-12-23 01:45:05'), (30, 2, 30, '0011', 'Surat Y', 'File keluar (Download)', '2020-12-23 02:06:26'), (31, 2, 32, '900', 'Surat Z', 'File keluar (Download)', '2020-12-23 02:07:13'), (32, 2, 26, '003', 'Surat Keputusan Presiden', 'File keluar (Download)', '2020-12-24 23:07:47'), (33, 2, 27, '003', 'Surat AB', 'Diubah (Nomor Filling Kabinet, Nama Folder, Tanggal Pembuatan)', '2020-12-28 10:20:55'), (34, 2, 27, '003', 'Surat AB', 'Diubah (Nomor Filling Kabinet, Nama Folder, Tanggal Pembuatan)', '2020-12-28 10:33:54'), (35, 2, 33, '0988123', 'Surat Pemberitahuan', 'Ditambahkan', '2020-12-28 10:40:23'), (36, 2, 33, '0988123', 'Surat Pemberitahuan', 'Diubah (Nomor Filling Kabinet, Nama Folder, Tanggal Pembuatan)', '2020-12-28 10:42:06'), (37, 2, 33, '0988123', 'Surat Pemberitahuan', 'Diubah (Nomor Filling Kabinet, Nama Folder, Tanggal Pembuatan)', '2020-12-28 10:43:47'), (38, 2, 33, '0988123', 'Surat Pemberitahuan', 'Diubah (Nomor Filling Kabinet, Nama Folder, Tanggal Pembuatan)', '2020-12-28 10:46:09'), (39, 2, 33, '0988123', 'Surat Pemberitahuan', 'Diubah (Nomor Filling Kabinet, Nama Folder, Tanggal Pembuatan)', '2020-12-28 10:46:29'), (40, 2, 33, '0988123', 'Surat Pemberitahuan', 'Diubah (Perihal, Nomor Filling Kabinet, Nama Folder, Tanggal Pembuatan)', '2020-12-28 10:48:21'), (41, 2, 33, '0988123', 'Surat Pemberitahuan', 'Diubah (Perihal, Nomor Filling Kabinet, Nama Folder, Tanggal Pembuatan)', '2020-12-28 10:49:41'), (42, 2, 33, '0988123', 'Surat Pemberitahuan', 'Diubah (Nama Folder, Tanggal Pembuatan)', '2020-12-28 10:50:49'), (43, 2, 30, '0011', 'Surat Y', 'Diubah (Tanggal Pembuatan)', '2020-12-28 10:52:36'), (44, 2, 33, '0988123', 'Surat Pemberitahuan', 'Diubah (Nama Folder, Tanggal Pembuatan)', '2020-12-28 10:54:12'), (45, 2, 33, '0988123', 'Surat Pemberitahuan', 'Diubah (Tanggal Pembuatan)', '2020-12-28 10:54:38'), (46, 2, 33, '0988123', 'Surat Pemberitahuan', 'Diubah (Nama Folder, Tanggal Pembuatan)', '2020-12-28 10:55:05'), (47, 2, 33, '0988123', 'Surat Pemberitahuan', 'Diubah (Tanggal Pembuatan)', '2020-12-28 10:56:12'), (48, 2, 33, '0988123', 'Surat Pemberitahuan', 'Diubah (Tanggal Pembuatan)', '2020-12-28 10:57:51'), (49, 2, 33, '0988123', 'Surat Pemberitahuan', 'Diubah (Tanggal Pembuatan)', '2020-12-28 10:58:51'), (50, 2, 33, '0988123', 'Surat Pemberitahuan', 'Diubah (Tanggal Pembuatan)', '2020-12-28 11:02:21'), (51, 2, 33, '0988123', 'Surat Pemberitahuan', 'Diubah (Tanggal Pembuatan)', '2020-12-28 11:05:22'), (52, 2, 33, '0988123', 'Surat Pemberitahuan', 'Diubah (Nama Folder)', '2020-12-28 11:05:54'), (53, 2, 27, '003', 'Surat AB', 'Berkas Fisik Diambil (Kantor Sebelah)', '2020-12-28 20:48:22'), (54, 2, 27, '003', 'Surat AB', 'Berkas Fisik Dikembalikan (Kabinet 122)', '2020-12-29 21:59:14'), (55, 2, 27, '003', 'Surat AB', 'Berkas Fisik Diambil (Kantor Sebelah)', '2020-12-29 21:59:35'), (56, 2, 27, '003', 'Surat AB', 'Berkas Fisik Dikembalikan (Kabinet 98)', '2020-12-29 21:59:54'), (57, 2, 27, '003', 'Surat AB', 'Berkas Fisik Diambil (Kantor A)', '2020-12-29 22:12:56'), (58, 2, 27, '003', 'Surat AB', 'Berkas Fisik Dikembalikan (Folder 12B)', '2020-12-29 22:13:14'), (59, 2, 27, '003', 'Surat AB', 'Berkas Fisik Diambil (Kantor P)', '2020-12-29 22:13:31'), (60, 2, 27, '003', 'Surat AB', 'Berkas Fisik Dikembalikan (Kabinet 12P/Folder 3F)', '2020-12-29 22:14:05'); -- -------------------------------------------------------- -- -- Struktur dari tabel `users` -- CREATE TABLE `users` ( `id` int(11) UNSIGNED NOT NULL, `email` varchar(255) NOT NULL, `username` varchar(30) DEFAULT NULL, `password_hash` varchar(255) NOT NULL, `reset_hash` varchar(255) DEFAULT NULL, `reset_at` datetime DEFAULT NULL, `reset_expires` datetime DEFAULT NULL, `activate_hash` varchar(255) DEFAULT NULL, `status` varchar(255) DEFAULT NULL, `status_message` varchar(255) DEFAULT NULL, `active` tinyint(1) NOT NULL DEFAULT 0, `force_pass_reset` tinyint(1) NOT NULL DEFAULT 0, `created_at` datetime DEFAULT NULL, `updated_at` datetime DEFAULT NULL, `deleted_at` datetime DEFAULT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8; -- -- Dumping data untuk tabel `users` -- INSERT INTO `users` (`id`, `email`, `username`, `password_hash`, `reset_hash`, `reset_at`, `reset_expires`, `activate_hash`, `status`, `status_message`, `active`, `force_pass_reset`, `created_at`, `updated_at`, `deleted_at`) VALUES (1, '<EMAIL>', '<PASSWORD>', <PASSWORD>', NULL, NULL, NULL, NULL, NULL, NULL, 1, 0, '2020-12-10 13:51:19', '2020-12-10 13:51:19', NULL), (2, '<EMAIL>', 'admin', <PASSWORD>', NULL, NULL, NULL, NULL, NULL, NULL, 1, 0, '2020-12-18 07:14:32', '2020-12-18 07:14:32', NULL); -- -- Indexes for dumped tables -- -- -- Indeks untuk tabel `auth_activation_attempts` -- ALTER TABLE `auth_activation_attempts` ADD PRIMARY KEY (`id`); -- -- Indeks untuk tabel `auth_groups` -- ALTER TABLE `auth_groups` ADD PRIMARY KEY (`id`); -- -- Indeks untuk tabel `auth_groups_permissions` -- ALTER TABLE `auth_groups_permissions` ADD KEY `auth_groups_permissions_permission_id_foreign` (`permission_id`), ADD KEY `group_id_permission_id` (`group_id`,`permission_id`); -- -- Indeks untuk tabel `auth_groups_users` -- ALTER TABLE `auth_groups_users` ADD KEY `auth_groups_users_user_id_foreign` (`user_id`), ADD KEY `group_id_user_id` (`group_id`,`user_id`); -- -- Indeks untuk tabel `auth_logins` -- ALTER TABLE `auth_logins` ADD PRIMARY KEY (`id`), ADD KEY `email` (`email`), ADD KEY `user_id` (`user_id`); -- -- Indeks untuk tabel `auth_permissions` -- ALTER TABLE `auth_permissions` ADD PRIMARY KEY (`id`); -- -- Indeks untuk tabel `auth_reset_attempts` -- ALTER TABLE `auth_reset_attempts` ADD PRIMARY KEY (`id`); -- -- Indeks untuk tabel `auth_tokens` -- ALTER TABLE `auth_tokens` ADD PRIMARY KEY (`id`), ADD KEY `auth_tokens_user_id_foreign` (`user_id`), ADD KEY `selector` (`selector`); -- -- Indeks untuk tabel `auth_users_permissions` -- ALTER TABLE `auth_users_permissions` ADD KEY `auth_users_permissions_permission_id_foreign` (`permission_id`), ADD KEY `user_id_permission_id` (`user_id`,`permission_id`); -- -- Indeks untuk tabel `dokumen` -- ALTER TABLE `dokumen` ADD PRIMARY KEY (`id`); -- -- Indeks untuk tabel `migrations` -- ALTER TABLE `migrations` ADD PRIMARY KEY (`id`); -- -- Indeks untuk tabel `riwayat` -- ALTER TABLE `riwayat` ADD PRIMARY KEY (`id`); -- -- Indeks untuk tabel `users` -- ALTER TABLE `users` ADD PRIMARY KEY (`id`), ADD UNIQUE KEY `email` (`email`), ADD UNIQUE KEY `username` (`username`); -- -- AUTO_INCREMENT untuk tabel yang dibuang -- -- -- AUTO_INCREMENT untuk tabel `auth_activation_attempts` -- ALTER TABLE `auth_activation_attempts` MODIFY `id` int(11) UNSIGNED NOT NULL AUTO_INCREMENT; -- -- AUTO_INCREMENT untuk tabel `auth_groups` -- ALTER TABLE `auth_groups` MODIFY `id` int(11) UNSIGNED NOT NULL AUTO_INCREMENT; -- -- AUTO_INCREMENT untuk tabel `auth_logins` -- ALTER TABLE `auth_logins` MODIFY `id` int(11) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=29; -- -- AUTO_INCREMENT untuk tabel `auth_permissions` -- ALTER TABLE `auth_permissions` MODIFY `id` int(11) UNSIGNED NOT NULL AUTO_INCREMENT; -- -- AUTO_INCREMENT untuk tabel `auth_reset_attempts` -- ALTER TABLE `auth_reset_attempts` MODIFY `id` int(11) UNSIGNED NOT NULL AUTO_INCREMENT; -- -- AUTO_INCREMENT untuk tabel `auth_tokens` -- ALTER TABLE `auth_tokens` MODIFY `id` int(11) UNSIGNED NOT NULL AUTO_INCREMENT; -- -- AUTO_INCREMENT untuk tabel `dokumen` -- ALTER TABLE `dokumen` MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=34; -- -- AUTO_INCREMENT untuk tabel `migrations` -- ALTER TABLE `migrations` MODIFY `id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2; -- -- AUTO_INCREMENT untuk tabel `riwayat` -- ALTER TABLE `riwayat` MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=61; -- -- AUTO_INCREMENT untuk tabel `users` -- ALTER TABLE `users` MODIFY `id` int(11) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=3; -- -- Ketidakleluasaan untuk tabel pelimpahan (Dumped Tables) -- -- -- Ketidakleluasaan untuk tabel `auth_groups_permissions` -- ALTER TABLE `auth_groups_permissions` ADD CONSTRAINT `auth_groups_permissions_group_id_foreign` FOREIGN KEY (`group_id`) REFERENCES `auth_groups` (`id`) ON DELETE CASCADE, ADD CONSTRAINT `auth_groups_permissions_permission_id_foreign` FOREIGN KEY (`permission_id`) REFERENCES `auth_permissions` (`id`) ON DELETE CASCADE; -- -- Ketidakleluasaan untuk tabel `auth_groups_users` -- ALTER TABLE `auth_groups_users` ADD CONSTRAINT `auth_groups_users_group_id_foreign` FOREIGN KEY (`group_id`) REFERENCES `auth_groups` (`id`) ON DELETE CASCADE, ADD CONSTRAINT `auth_groups_users_user_id_foreign` FOREIGN KEY (`user_id`) REFERENCES `users` (`id`) ON DELETE CASCADE; -- -- Ketidakleluasaan untuk tabel `auth_tokens` -- ALTER TABLE `auth_tokens` ADD CONSTRAINT `auth_tokens_user_id_foreign` FOREIGN KEY (`user_id`) REFERENCES `users` (`id`) ON DELETE CASCADE; -- -- Ketidakleluasaan untuk tabel `auth_users_permissions` -- ALTER TABLE `auth_users_permissions` ADD CONSTRAINT `auth_users_permissions_permission_id_foreign` FOREIGN KEY (`permission_id`) REFERENCES `auth_permissions` (`id`) ON DELETE CASCADE, ADD CONSTRAINT `auth_users_permissions_user_id_foreign` FOREIGN KEY (`user_id`) REFERENCES `users` (`id`) ON DELETE CASCADE; COMMIT; /*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */; /*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */; /*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;

<filename>examples/schema.sql<gh_stars>0 CREATE TABLE members ( id uuid, email varchar(128), hashed_password varchar(128), name varchar(128), PRIMARY KEY (id) ); CREATE TABLE products ( id uuid, name varchar(128), ean varchar(128), price decimal, category_id uuid, PRIMARY KEY (id) ); CREATE TABLE orders ( id uuid, member_id uuid, amount decimal, PRIMARY KEY (id), ); CREATE TABLE order_items ( id uuid, order_id uuid, product_id uuid, quantity int, amount int, PRIMARY KEY (id), CONSTRAINT order_id FOREIGN KEY (order_id) REFERENCES orders (id), ); CREATE TABLE categories ( id uuid, name varchar(128), parent_id uuid, PRIMARY KEY (id) ); -- Example queries SELECT * FROM orders WHERE orders.id = '...'; -- Query plan for Matriarch -- 1. parse sql statement FROM clause to detect the table involved in the statement -- 1.1. get its vindexes -- 2. parse sql statement WHERE clause to see if it matches any of the columns used in -- vindexes of the table involved (starting with the primary vindex) -- 2.1 WHERE column matches the primary vindex column 'id' -- 3 Matriarch hashes the id and routes the query to the appropriate shard -- 4 Matriarch proxies the response back to the client SELECT * FROM orders INNER JOIN order_items ON order_items.order_id = orders.id WHERE orders.id = '...'; -- Query plan for Matriarch -- 1. parse sql statement FROM clause to detect tables involved in the statement -- and the join condition -- 1.1. for each table get the vindexes -- 2. parse sql statement WHERE clause to see if it matches any of the -- vindexes of the tables involved (starting with the primary vindex) -- 2.1 WHERE column matches the primary vindex column of table ecommerce.orders -- 2.2 Matriarch hashes the order id and identifies the appropriate shard for ecommerce.orders -- 2.3 By parsing the JOIN condition, Matriarch understands that the column used in the -- WHERE clause is also used to match data in table order_items. -- 3 Matriarch routes the whole query to the appropriate shard -- 4 Matriarch proxies the response back to the client

<gh_stars>0 create table if not exists user( user_id varchar(20), user_pw varchar(255) not null, mail varchar(40) not null, gender varchar(10) not null, class varchar(10) not null, f_name varchar(10) not null, l_name varchar(10) not null, PRIMARY KEY (user_id) ); create table if not exists phone( phone_num varchar(20), user_id varchar(20) not null, PRIMARY KEY (phone_num), FOREIGN KEY (user_id) REFERENCES user (user_id) ); create table if not exists cardinfo( id int, user_id varchar(20) not null, company varchar(20) not null, card1 int(4), card2 int(4), card3 int(4), card4 varchar(255), PRIMARY KEY (id), FOREIGN KEY (user_id) REFERENCES user(user_id) );