<     May 2017     >
Su Mo Tu We Th Fr Sa  
    1  2  3  4  5  6  
 7  8  9 10 11 12 13  
14 15 16 17 18 19 20  
21 22 23 24 25 26 27  
28 29 30 31
03:13 GitHub191 joined
03:13 <GitHub191> [13sequel] 15StevePotter opened issue #1365: Looking for guidance on appending a literal field to each SELECT query 02https://git.io/vHmvy
03:13 GitHub191 left
05:08 tercenya joined
05:45 GitHub114 joined
05:45 <GitHub114> [13sequel] 15jeremyevans commented on issue #1365: For this type of thing, I would recommend using the sql_comments extension that ships with Sequel. But you could also override `select_columns_sql` for the dataset to append additional columns.... 02https://git.io/vHmtr
05:45 GitHub114 left
05:45 GitHub111 joined
05:45 <GitHub111> [13sequel] 15jeremyevans closed issue #1365: Looking for guidance on appending a literal field to each SELECT query 02https://git.io/vHmvy
05:45 GitHub111 left
07:14 aidalgol joined
08:22 tercenya joined
10:25 lopex joined
12:20 GitHub41 joined
12:20 <GitHub41> [13sequel] 15StevePotter commented on issue #1365: @jeremyevans sorry for posting to the wrong forum and thank you so much for your help! 02https://git.io/vHmSY
12:20 GitHub41 left
12:40 riddley joined
13:07 adamdrew joined
13:11 <adamdrew> I'm using Sequel::Model with sqlite, and set_schema and create_table to setup my database. How can I add columns later? I tried adding the new columns to set_schema block, but that didn't work. I tried added a migration block but that didn't work either
13:11 <adamdrew> I couldn't find any example of how to extend a model in the docs
13:45 evanmorton joined
13:49 <evanmorton> This is a followup to yesterday's question. I'm accessing SQL Server, and have had some success in writing to it. However, when I read from it using the below code, everything comes back nil. The row count is right, and the column names are right, but the data isn't getting to me. Any ideas?inTable = $database.from(Sequel.lit(inTableName)) inTable.all{|row| p row} Thanks.
14:17 <jeremyevans> adamdrew: The schema plugin is being deprecated, you should use migrations to make modifications to database schema
14:18 <jeremyevans> evanmorton: What does inTable.first return?
14:23 <adamdrew> thanks jeremyevans - I haven't used migrations before so I want to make sure I understand them. I wont write any code in my model class the way I do with schema. rather, I create a separate script using the migration dsl and execute that outside of my app?
14:24 <adamdrew> and I can get started by dumping the schema from my existing databases using sequel -d ?
14:34 <jeremyevans> adamdrew: that's correct
16:19 Rennex joined
17:09 <evanmorton> jeremyevans:It returns the following, which I've sanitized by changing column names "{:rownumber=>nil, :foo=>nil, :bar=>nil, :wombat=>nil}"
17:11 <jeremyevans> evanmorton: Odd. Can you try using the underlying driver directly to see if the behavior is different? Which adapter are you using, and what is the underlying driver and driver version?
17:41 <evanmorton> jeremyevans: I'm using :adapter=>'ado'. How do I find out the driver and driver version? How do I use it directly? Thanks.
17:42 <jeremyevans> evanmorton: ado uses ruby's built in win32ole driver
17:43 <jeremyevans> evanmorton: Can you try using the tinytds adapter and see if you can reproduce the problem with that adapter?
17:43 <jeremyevans> evanmorton: tinytds is the recommended adapter for accessing Microsoft SQL Server
17:59 tercenya joined
18:05 <evanmorton> That works. Thanks!
18:06 <evanmorton> The reason I was using ado rather than tiny_tds is that in a related application I tried many adapters, including tiny_tds, and had various problems. If I have problems with tiny_tds again is it possible to have both adapters open? That is, can I have two different adapters within the same process connecting to the same database at once?
18:11 <jeremyevans> evanmorton: yes, that is certainly possible
18:22 <evanmorton> Good. Thanks for all the help.
20:12 tercenya joined
20:23 pdrakeweb joined
21:56 brybeecher joined
23:24 brybeecher joined