01:01.53 |
*** join/#brlcad kintel
(~kintel@unaffiliated/kintel) |
02:17.04 |
*** join/#brlcad kintel
(~kintel@unaffiliated/kintel) |
04:00.02 |
*** join/#brlcad ankesh11
(uid8015@gateway/web/irccloud.com/x-pugmazhdofrfjbcp) |
04:00.18 |
*** join/#brlcad ankesh11_
(uid8015@gateway/web/irccloud.com/x-lqojndbiragpyjen) |
04:05.23 |
*** join/#brlcad kanzure
(~kanzure@unaffiliated/kanzure) |
06:52.37 |
*** join/#brlcad merzo
(~merzo@user-94-45-58-141.skif.com.ua) |
07:42.20 |
*** join/#brlcad luca79
(~luca@host150-111-dynamic.4-87-r.retail.telecomitalia.it) |
09:00.17 |
*** join/#brlcad luca79
(~luca@host150-111-dynamic.4-87-r.retail.telecomitalia.it) |
09:03.11 |
*** join/#brlcad teepee--
(bc5c2133@gateway/web/freenode/ip.188.92.33.51) |
09:32.39 |
*** join/#brlcad dracarys983
(dracarys98@nat/iiit/x-bhcveqhixgggpaca) |
09:54.28 |
*** join/#brlcad andrei_il
(~andrei@109.100.128.78) |
10:32.34 |
*** join/#brlcad dracarys983
(dracarys98@nat/iiit/x-nhjawwfoxrfwcbya) |
12:50.22 |
*** join/#brlcad Izakey
(~Izakey@41.205.22.42) |
13:06.10 |
Notify |
03BRL-CAD:starseeker * 64689
brlcad/trunk/include/raytrace.h: Stub in first thoughts on
rt_pattern parameters container. |
13:07.08 |
Notify |
03BRL-CAD:starseeker * 64690
brlcad/trunk/sh/cmp.sh: It's now gqa, not g_qa |
13:32.47 |
*** join/#brlcad dracarys983
(dracarys98@nat/iiit/x-pueoyzmjykesbqzv) |
13:36.52 |
Notify |
03BRL-CAD:starseeker * 64692
(brlcad/trunk/src/libged/CMakeLists.txt
brlcad/trunk/src/libged/gdiff.c): gdiff ged command will need an
option for raytrace based testing. |
13:39.19 |
Izakey |
Hi starseeker Which command(s) tests mirror
support of a primitive ? |
14:20.06 |
*** join/#brlcad kintel
(~kintel@unaffiliated/kintel) |
14:36.07 |
Notify |
03BRL-CAD:starseeker * 64691
brlcad/trunk/include/raytrace.h: oops - finish struct |
14:39.02 |
*** join/#brlcad arno
(~luca@host157-19-dynamic.4-87-r.retail.telecomitalia.it) |
14:49.13 |
*** join/#brlcad kintel
(~kintel@unaffiliated/kintel) |
15:00.11 |
*** join/#brlcad kintel
(~kintel@unaffiliated/kintel) |
15:35.12 |
*** join/#brlcad Izakey
(~Izakey@41.205.22.51) |
15:46.38 |
*** join/#brlcad kintel
(~kintel@unaffiliated/kintel) |
16:42.18 |
*** join/#brlcad FreezingCold
(~FreezingC@135.0.41.14) |
16:45.37 |
*** join/#brlcad kintel
(~kintel@unaffiliated/kintel) |
16:58.31 |
*** join/#brlcad pujani
(~pujani@117.234.106.53) |
17:41.59 |
*** join/#brlcad kintel
(~kintel@unaffiliated/kintel) |
18:33.51 |
*** join/#brlcad pujani
(~pujani@117.234.106.53) |
19:10.29 |
*** join/#brlcad kintel
(~kintel@unaffiliated/kintel) |
19:15.24 |
*** join/#brlcad konrado
(~konro@41.244.240.211) |
19:25.28 |
*** join/#brlcad albertcoder
(~albertcod@1.39.32.31) |
19:26.07 |
*** join/#brlcad LordOfBikes
(~armin@dslb-088-066-212-148.088.066.pools.vodafone-ip.de) |
19:29.22 |
*** join/#brlcad LordOfBikes
(~armin@dslb-088-066-212-148.088.066.pools.vodafone-ip.de) |
19:31.22 |
albertcoder |
Hi brlcad I had a question in mind, regarding
the dynamic creation of tables. I have used a hook to create the
tables required for mdb extension. But when some user adds a new
trait, a new table is created (using unrecommended way
dbw->query(" "); also a MediaWiki developer advised update
database schema (create tables etc.) only once during the
installation of the script. |
19:31.24 |
*** join/#brlcad LordOfBikes
(~armin@dslb-088-066-212-148.088.066.pools.vodafone-ip.de) |
19:31.35 |
albertcoder |
How should this be tackled? |
20:36.41 |
brlcad |
awesome! http://www.mpi-sws.org/~rossberg/1ml/ |
20:37.29 |
brlcad |
albertcoder: not sure I follow .. any database
creation script should ideally only create the tables once
:) |
20:42.51 |
albertcoder |
Oh no, then I feel there has been some
miscommunication regarding the database design that we got approved
last time. brlcad It was decided that each new trait added must
create a new table for itself. |
20:46.10 |
*** join/#brlcad sofat
(~androirc@1.39.32.31) |
20:55.31 |
albertcoder |
I discussed this controversial database design
before and it was approved. Even someone from MediaWiki expressed
security concerns for handing over the power to create tables to
users. |
20:56.17 |
albertcoder |
brlcad, I asked this in the ML long ago and
you answered "This is database normalization. There are upsides
and downsides." |
20:57.49 |
albertcoder |
Did I get mistaken somewhere in
understanding? |
21:29.57 |
brlcad |
albertcoder: no, I mean that if there's a
script and tables are changing that the script should change too so
that the tables only get created one time |
21:30.03 |
brlcad |
not that it's a finite set of tables |
21:31.28 |
brlcad |
I remember that message, but I'm not sure I
remember realizing that nuance |
21:32.08 |
brlcad |
it's not a show stopper for us either way, but
I have to imagine there's another way to achieve full normalization
without having dynamic tables too |
21:32.24 |
brlcad |
(a table describing tables, unique
keys) |
21:44.21 |
albertcoder |
brlcad I am a little confused here. Like you
said, suppose we change the script (automated) which creates tables
upon the addition of trait by the user. Even then the script has to
be run manually to update the database schema. |
21:45.44 |
albertcoder |
like `php maintenance/update.php` in base
MediaWiki dir. |
21:52.43 |
albertcoder |
Anyway brlcad please leave your replies here,
it's 3:30 am here gotta leave. I will read them in the logs in the
morning. |
21:52.48 |
albertcoder |
gn |
21:56.36 |
*** join/#brlcad albertcoder
(~coderalbe@1.39.32.31) |
21:56.42 |
*** join/#brlcad Alleycoder
(~coderalbe@1.39.32.31) |
23:56.43 |
*** join/#brlcad ignacio
(~ignacio@unaffiliated/ignaciouy) |