{"author_name":"Truck","cat":"LD #22","comments":[],"epoch":1324329480,"likes":1,"metadata":{"p_key":"60267","p_author":"Truck","p_authorkey":"8368","p_urlkey":"96020","p_title":"tools","p_cat":"LD #22","p_event":"LD22","p_time":"1324329480","p_likes":"1","p_comments":"0","p_status":"UPD5","us_key":"8368","us_name":"Truck","us_username":"truck","event_start":"1323993600","event_key":"8","event_name":"LD22"},"text":"<p>So originally I said &#8220;I will not use a object-relational mapper.&#8221;\u00a0 My reasons were:<\/p>\n <ul>\n <li>Overhead<\/li>\n <li>I don&#8217;t mind designing by hand, in fact, I&#8217;m fairly good at it<\/li>\n <li>I don&#8217;t have experience with any aside from django&#8217;s mapper<\/li>\n <li>I am not using django (waay too much overhead and wrong toolkit for this.)<\/li>\n <\/ul>\n <p>I&#8217;d looked at the Canonical thing, I think it&#8217;s called storm, and it looked decent but in my attempted use of it a month or so ago, I hit upon lack of documentation beyond the tutorial which did not explain some basic things, like &#8220;how to get your db design to map.&#8221;\u00a0 Sort of, you know, what a mapper&#8230; should do.<\/p>\n <p>I do not feel that sqlalchemy is a good choice because it&#8217;s just plain too much overhead.\u00a0 I don&#8217;t really need an ORM.\u00a0 I need connectivity, and I&#8217;ll handle keeping the database in line. I&#8217;ve dealt far too many times with software that assumes that if you use a mapper, the database will never get corrupted. Like, you know, 100% of all java db stuff I&#8217;ve ever dealt with. In production. Costing me months of time. I hate java; too many &#8220;developers&#8221; who _can&#8217;t._\u00a0 Those who _can_ develop in java never end up working anywhere near me.<\/p>\n <p>Anyway so with all that background, I said &#8220;no&#8221; and was busy setting up the db by hand, and &#8211; darn it, I went and changed tools. I used to draw stuff up and build the whole design first, then publish; but no I went and was doing it bit by bit using Sequel Pro. No. Bad. It doesn&#8217;t &#8230; it works but it is NOT a design tool. It is &#8230; usable for some stuff I&#8217;ve been dealing with at work. With crap db&#8217;s designed by people who have no clue. _should have known_ but didn&#8217;t think it would be THIS bad.<\/p>\n <p>MySql Workbench worked well but lately it&#8217;s just been PANTS. Meaning &#8220;Hi, I will crash now!&#8221; and such. Also they don&#8217;t do ppc. And&#8230; yeah.<\/p>\n <p>So in short: I will need to probably write my own ORM type thing after this is over. What I need is a way to define the db directly, quickly, and without having breakage upon a change. And very little overhead.\u00a0 I want data, put into an object, and I&#8217;ll do the push\/pull when I need to.<\/p>\n <p>Oh that&#8217;s right, another issue with storm was it did not explain in any way, shape, or form how to avoid the problem of persistent connections that needed to be re-attached. Like, if you went to sleep, and they timed out, how to reconnect them the next morning when you were looking at it.<\/p>\n <p>Anyway not publishing this til after. Just saying, this is one of the things that went awry.<\/p>","time":"December 19th, 2011 4:18 pm","title":"tools"}