Ralf Vitasek
Ralf Vitasek
Definitely not the composite keys gem, i kicked that for good. But in your examples that work and would here too i assume you don't have the problematic trailing backslash...
This is really weird. ```sql INSERT INTO [testings] ([data]) OUTPUT INSERTED.[id] VALUES (N'--- :folder: c:\data\foo\ :file: example.yml ') ``` I'm seeing exactly the same problem when executing this sample in...
I guess i've found the root of this problem. This is a special thing that SQL Server is doing. A backslash at an end of a line is treated as...
sounds like the same to me: https://spin.atomicobject.com/2008/03/18/trailing-backslash-problem-and-fix-for-rails-and-sqlserver-2005/
Eh? No it actually has nothing to do with YAML. It‘s an adapter thing and so far the only solution i can rhink of is to Regex parse any strings...
Again: this has nothing to do with YAML. Any textarea can suffer from thus. Just enter a text with a lne that ends with a backslash and a following linebreak...
In any text to persist losing that backslash and the linebreak sure is just 2 bytes lost. In YAML you will notice quick because that breaks all following data.
just a plain FLOAT(8) that came from a migration what was simply created by `t.float :some_float` i googled a bit and it seems that while other DBs support NaN, INF...
and my adapter version is the current 5.1.6
That should just work with `has_many :articles` in the serializer. The serializer doesn't need to care where the ORM stores the association.