Changes between Version 2 and Version 3 of django_gheat

Timestamp:

Apr 13, 2011, 8:21:52 PM (14 years ago)

Author:

dennisw

Comment:

--

django_gheat

@@ -45 +45 @@
 Once you've entered the correct settings, you will be able to start Django.
 {{{
-$ cd django_gheat/samples/persisted
+# 'cd' to project root
+# The following command will add some standard Django tables and the tables defined in django_gheat/gheat/models.py to the database
+$ ./manage.py syncdb
 
-# The following command will add some standard Django tables and the tables defined in django_gheat/gheat/models.py to the database
-$ python manage.py syncdb
-
-$ python manage.py runserver
+# if using sample page, first 'cd samples/persisted', will get fixed soon
+$ ./manage.py runserver
 }}}
 Something like this should return:
@@ -75 +75 @@
 CREATE TABLE `gheat_gebruiker` (
     `id` integer AUTO_INCREMENT NOT NULL PRIMARY KEY,
-    `gebruiker` varchar(64) NOT NULL,
-    `apparatuur` varchar(64) NOT NULL
+    `naam` varchar(64) NOT NULL,
+    `email` varchar(64) NOT NULL
 )
 ;
+CREATE TABLE `gheat_apparatuur` (
+    `id` integer AUTO_INCREMENT NOT NULL PRIMARY KEY,
+    `antenne` varchar(64) NOT NULL,
+    `kaart` varchar(64) NOT NULL
+)
+;
+CREATE TABLE `gheat_meetrondje` (
+    `id` integer AUTO_INCREMENT NOT NULL PRIMARY KEY,
+    `datum` datetime NOT NULL,
+    `naam` varchar(60) NOT NULL,
+    `gebruiker_id` integer NOT NULL,
+    `apparatuur_id` integer NOT NULL
+)
+;
+ALTER TABLE `gheat_meetrondje` ADD CONSTRAINT `apparatuur_id_refs_id_5e2d317` FOREIGN KEY (`apparatuur_id`) REFERENCES `gheat_apparatuur` (`id`);
+ALTER TABLE `gheat_meetrondje` ADD CONSTRAINT `gebruiker_id_refs_id_3b558609` FOREIGN KEY (`gebruiker_id`) REFERENCES `gheat_gebruiker` (`id`);
 CREATE TABLE `gheat_meting` (
     `id` integer AUTO_INCREMENT NOT NULL PRIMARY KEY,
+    `meetrondje_id` integer NOT NULL,
     `accespoint_id` integer NOT NULL,
-    `gebruiker_id` integer NOT NULL,
     `lat` double precision NOT NULL,
     `lng` double precision NOT NULL,
-    `signaal` integer NOT NULL,
-    `datum` datetime NOT NULL
+    `signaal` integer NOT NULL
 )
 ;
-ALTER TABLE `gheat_meting` ADD CONSTRAINT `gebruiker_id_refs_id_56605efc` FOREIGN KEY (`gebruiker_id`) REFERENCES `gheat_gebruiker` (`id`);
 ALTER TABLE `gheat_meting` ADD CONSTRAINT `accespoint_id_refs_id_49f1ad5c` FOREIGN KEY (`accespoint_id`) REFERENCES `gheat_accespoint` (`id`);
+ALTER TABLE `gheat_meting` ADD CONSTRAINT `meetrondje_id_refs_id_6c4042fe` FOREIGN KEY (`meetrondje_id`) REFERENCES `gheat_meetrondje` (`id`);
 COMMIT;
+
 }}}
 Note that on this moment only the gheat_meting(lat, lng, signaal) are used for generating heatmaps, so make sure you atleast put some data in those columns.
@@ -98 +114 @@
 You can prerender a heatmap with the following command:
 {{{
-$ cd django_gheat/samples/persisted
-$ python manage.py gen_tiles
+# 'cd' to project root
+$ ./manage.py gen_tiles
 }}}
 This will prerender a heatmap with the default boundingbox specified in django_gheat/gheat/management/commands/gen_tiles.py
@@ -109 +125 @@
 # -b = view used for creating tiles, default should be fine
 
-$ python manage.py gen_tiles -s 60,6 -e 66,8 -c firetrans -b serve_tile
+$ ./manage.py gen_tiles -s 60,6 -e 66,8 -c firetrans -b serve_tile
 }}}