Node name limitation?

[Kasbolat Kumakhov]

I have a list of products in my Android app which looks like this:

productList

  |-- productName_1

      |-- parameter_1

      |-- parameter_2

      |-- parameter_3

  |-- productName_2

      |-- parameter_1

      |-- parameter_2

      |-- parameter_3

  |-- productName_3

      |-- parameter_1

      |-- parameter_2

      |-- parameter_3

The product names are user generated. I thougth it's a good way to store data, but it appears that there is a name limitation in Firebase (perhaps i missed it in the docs).

When user types "." (dot) i get an exception like this:

com.google.firebase.database.DatabaseException: Invalid Firebase Database path: productList/CoolProduct.. Firebase Database paths must not contain '.', '#', '$', '[', or ']'

Ok. Pretty understandable.

But how to handle this in code and not limit users in product names? Something like escaping sequences or something?

Or perhaps i need to change the scheme and store products under push IDs?

[Kato Richardson]

Hi Kasbolat,

The restricted characters are covered here. You'll either need to escape those characters (URl encoding almost works, except that you still need to convert periods) or use a more unique/safe identifier.

Using unrestricted names as the keys may also result in duplicates or prevent two entries with the same name. Push ids are, of course, ideal for distributed data, but not always as readable if you're going to be putting them into the URLs. So slugifying the names may be preferable.

☼, Kato

--
You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebase-talk+unsubscribe@googlegroups.com.
To post to this group, send email to fireba...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/3d1fb713-bcb0-4bf9-a68c-237e111bf540%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Kato Richardson |

Developer Programs Eng |

kato...@google.com |

775-235-8398

[Kasbolat Kumakhov]

I see. Thanks for the link. As i mentioned - missed it.

Well duplication is not a problem in my case.

Actually I thought of using base64 encoding. What do you think about it?

The point is to encode and decode the strings back. Not just one way.

четверг, 25 августа 2016 г., 23:29:54 UTC+3 пользователь Kato Richardson написал:

To unsubscribe from this group and stop receiving emails from it, send an email to firebase-tal...@googlegroups.com.

To post to this group, send email to fireba...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/3d1fb713-bcb0-4bf9-a68c-237e111bf540%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Kato Richardson]

If they don't need to be human readable in the database, push ids would be simplest and most useful (they're unique to the billions, chronologically ordered, already available in the SDK). If they need to be readable in URLs, et al, then probably slugifying or escaping control chars.

☼, Kato

To unsubscribe from this group and stop receiving emails from it, send an email to firebase-talk+unsubscribe@googlegroups.com.

To post to this group, send email to fireba...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/e32aad74-cf6b-4af7-a651-bdc9566820cf%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Joe White]

Use a PushID .. and with a property of name underneath ... may need an alternat node with the names and the associated UIDs to lookup.

[Kasbolat Kumakhov]

Thanks both of you, but in my case push IDs are not convenient because they add another level of hierarchy which i wanted to avoid.

I'll think about it, though. Thanks again!

четверг, 25 августа 2016 г., 22:54:39 UTC+3 пользователь Kasbolat Kumakhov написал: