Re: Thinking through object/text fields: Findings summarized, advice solicited

2017-07-18 Thread David Adams via 4D_Tech
Thanks for the people that answered "what has Postgres have to do with 4D" so well. Also, thanks for the advice on tools. My quick findings for desktop tools (I didn't look at Web tools) Valentina Studio Surprisingly good and complete for a free tool. Design, admin, and data browsing. The 'pro' v

Re: Thinking through object/text fields: Findings summarized, advice solicited

2017-07-18 Thread John DeSoi via 4D_Tech
Hi Kirk, Navicat is just a GUI tool to view and manipulate PostgreSQL data. It is really that PostgreSQL helps me with 4D. 4D is great, but PostgreSQL is better suited for many tasks. I use it for websites (with Drupal) and sync the necessary data with 4D. I also use it a lot for preprocessing

Re: Thinking through object/text fields: Findings summarized, advice solicited

2017-07-17 Thread David Adams via 4D_Tech
Hey Lee, thanks for the suggestions, that should save me some time for sure. On Tue, Jul 18, 2017 at 3:26 AM, Lee Hinde via 4D_Tech <4d_tech@lists.4d.com > wrote: > On Mon, Jul 17, 2017 at 5:40 AM, David Adams via 4D_Tech < > 4d_tech@lists.4d.com> wrote: > > > > > My biggest problem with PostgreS

Re: Thinking through object/text fields: Findings summarized, advice solicited

2017-07-17 Thread David Adams via 4D_Tech
On Tue, Jul 18, 2017 at 2:08 AM, Kirk Brooks via 4D_Tech < 4d_tech@lists.4d.com> wrote: > Hi John, > I haven't done very much communicating from 4D to a SQL database so this is > a very naive question - but could you talk about how a tool like Navicat > helps you with 4D? It doesn't. But if you'

Re: Thinking through object/text fields: Findings summarized, advice solicited

2017-07-17 Thread Lee Hinde via 4D_Tech
On Mon, Jul 17, 2017 at 5:40 AM, David Adams via 4D_Tech < 4d_tech@lists.4d.com> wrote: > > My biggest problem with PostgreSQL is the relative lack of nice front-end > tools. My beloved SequelPro for MySQL has long hinted at a PostgreSQL > version, but it doesn't seem to be there yet. For MySQL th

Re: Thinking through object/text fields: Findings summarized, advice solicited

2017-07-17 Thread Kirk Brooks via 4D_Tech
Hi John, I haven't done very much communicating from 4D to a SQL database so this is a very naive question - but could you talk about how a tool like Navicat helps you with 4D? On Mon, Jul 17, 2017 at 8:39 AM, John DeSoi via 4D_Tech < 4d_tech@lists.4d.com> wrote: > I bought Navicat 11 a few month

Re: Thinking through object/text fields: Findings summarized, advice solicited

2017-07-17 Thread John DeSoi via 4D_Tech
I bought Navicat 11 a few months ago after they made some nice improvements in the SQL editor. I thought it was the most Mac friendly of any PostgreSQL tools. Shortly thereafter Navicat 12 was released. I'm pretty sure it is not Java, but I think they switched to some other GUI library to make t

Re: Thinking through object/text fields: Findings summarized, advice solicited

2017-07-17 Thread David Adams via 4D_Tech
Better and better, thanks John. That's great, I'd seen mention of TOAST but wasn't sure how it fit in. Now after 1 hour total, I'm feeling like a PostgreSQL smartie ;-) Since we're on this (not 4D) subject, I'll just mention a key detail about jsonb queries in PostgreSQL: They cannot take adva

Re: Thinking through object/text fields: Findings summarized, advice solicited

2017-07-17 Thread John DeSoi via 4D_Tech
Note: PostgreSQL automatically and transparently compresses large variable length column values. https://www.postgresql.org/docs/9.6/static/storage-toast.html John DeSoi, Ph.D. > On Jul 17, 2017, at 12:10 AM, David Adams via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > The jsonb type restruct

Re: Thinking through object/text fields: Findings summarized, advice solicited

2017-07-16 Thread David Adams via 4D_Tech
> On Mon, Jul 17, 2017 at 6:50 AM, Julio Carneiro via 4D_Tech < 4d_tech@lists.4d.com> wrote: > Correct, David, you got the gist of my comment. > Jim Hays gave a great example where I can see object fields excel. If your app > requires user defined fields, then an object field is just perfect for t

Re: Thinking through object/text fields: Findings summarized, advice solicited

2017-07-16 Thread Julio Carneiro via 4D_Tech
Correct, David, you got the gist of my comment. Jim Hays gave a great example where I can see object fields excel. If your app requires user defined fields, then an object field is just perfect for that. I’ve had similar situations in the past and used tab-separated text fields first, and then

Re: Thinking through object/text fields: Findings summarized, advice solicited

2017-07-15 Thread Cannon Smith via 4D_Tech
Although I use object extensively in code, I don’t use them in very many fields. I do have several “settings” fields and find object type fields very useful here. Being able to add settings in the future without changing the structure is great and it seems like less work to have an extensive, bu

Re: Thinking through object/text fields: Findings summarized, advice solicited

2017-07-14 Thread David Adams via 4D_Tech
On Sat, Jul 15, 2017 at 7:36 AM, Kirk Brooks via 4D_Tech < 4d_tech@lists.4d.com> wrote: > > Perhaps this is what you are saying and I'm just reading too narrowly (it's > been that sort of week). > I'm not sure, but I was reading Julio's comment as something akin to "David, don't do what you were

Re: Thinking through object/text fields: Findings summarized, advice solicited

2017-07-14 Thread David Adams via 4D_Tech
Right, good point about the SQL goof. I have a little test window for SQL statements I use regularly for data exploration. Handy! Double-click a table name and automatically get a pre-built SELECT, etc. I had to update it to scan the list of fields for object field types and exclude them. Pity. T

Re: Thinking through object/text fields: Findings summarized, advice solicited

2017-07-14 Thread Kirk Brooks via 4D_Tech
Julio, I don't think 'variable structure' is necessarily the defining element. It's certainly good for that but now that we can search on these fields they're also good for situations where you want to allow each record to have some large number of fields most of which won't ever be used but need t

Re: Thinking through object/text fields: Findings summarized, advice solicited

2017-07-14 Thread Jim Hays via 4D_Tech
> * Unless you need the object field index & search, there is exactly *no > reason* to use an object field instead of a text field. We have a need for customers to create their own fields - dates, numbers, texts, possibly pictures. Haven't actually done it yet, but we expect that Object fields will

Re: Thinking through object/text fields: Findings summarized, advice solicited

2017-07-14 Thread Charles Miller via 4D_Tech
I think just one more thing and that is a caveat. You can NOT access object fields with SQL. You would have to write a sql fn call that would return the data to you. I for one will not be using object fields until they become available through sql. As much as I like the idea, I move to much data b

Re: Thinking through object/text fields: Findings summarized, advice solicited

2017-07-14 Thread Walt Nelson via 4D_Tech
David, Given that 4D and Wakanda use the same data engine (from my limited understanding of Wakanda, I believe they do), have you spoken to anyone on the Wakanda team about your concerns/questions? Just thought I would throw that into the mix. Thanks, Walt Nelson (Seattle) New stuff coming! ww

Re: Thinking through object/text fields: Findings summarized, advice solicited

2017-07-14 Thread David Adams via 4D_Tech
John, Good point thanks. That could be a meaningful help in a situation where 4D is being used to generate JSON blocks to pump out to another system. That's exactly what I'm thinking about. 4D doesn't have built in data analysis or visualization tools (well, there is sort of graph feature, but it'

Re: Thinking through object/text fields: Findings summarized, advice solicited

2017-07-14 Thread John DeSoi via 4D_Tech
If storage space is a primary constraint and object indexing is not needed, you can use a blob to store as UTF-8 text. VARIABLE TO BLOB with object uses UTF-8 text (tested 15.4, not 16). In your example where you basically wanted to store an object array directly, you could stringify the array

Re: Thinking through object/text fields: Findings summarized, advice solicited

2017-07-14 Thread Jim Dorrance via 4D_Tech
I agree... If the structure is fixed and the values need to be visualised,I: Store in specific arrays. Arrays to blob. Blob to field (or Document). To visualise: Blob from Document or field Blob to arrays Arrays to Listbox and my QuerySort component to search etc On Fri, Jul 14, 2017 at 10:49 AM

Re: Thinking through object/text fields: Findings summarized, advice solicited

2017-07-14 Thread David Adams via 4D_Tech
Julio, Thanks for the excellent points you added to the first post. ** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/option

Re: Thinking through object/text fields: Findings summarized, advice solicited

2017-07-14 Thread Julio Carneiro via 4D_Tech
On Jul 14, 2017, at 4:21 AM, David Adams via 4D_Tech <4d_tech@lists.4d.com> wrote: > > Does that all sound about right? Am I missing reasons why I would want to > use object fields. vs. text fields? Any other technical details that people > have learned or figured out? I’d add that using an obje

Thinking through object/text fields: Findings summarized, advice solicited

2017-07-13 Thread David Adams via 4D_Tech
Having just started looking at object fields and learned a few things, I have a few thoughts. For background, I've been using 4D's C_OBJECT and ARRAY OBJECT for some time, and now I'm looking at object fields. I think that I've gotten a grip on some of the details through experimentation, help from